<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Email Best Practice #5</title>
	<atom:link href="http://webcoherence.org/best-practices/email-best-practices/email-best-practice-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://webcoherence.org/best-practices/email-best-practices/email-best-practice-5/</link>
	<description>Experiments with Coherence on the Web</description>
	<lastBuildDate>Thu, 01 Dec 2011 22:25:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Antione Fuhriman</title>
		<link>http://webcoherence.org/best-practices/email-best-practices/email-best-practice-5/comment-page-1/#comment-620</link>
		<dc:creator>Antione Fuhriman</dc:creator>
		<pubDate>Fri, 15 Jul 2011 13:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://webcoherence.org/?p=473#comment-620</guid>
		<description>I think this is one of the most important information for me. And i am glad reading your article. But should remark on few general things, The site style is wonderful, the articles is really great : D. Good job, cheers</description>
		<content:encoded><![CDATA[<p>I think this is one of the most important information for me. And i am glad reading your article. But should remark on few general things, The site style is wonderful, the articles is really great : D. Good job, cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: G.Chomic</title>
		<link>http://webcoherence.org/best-practices/email-best-practices/email-best-practice-5/comment-page-1/#comment-28</link>
		<dc:creator>G.Chomic</dc:creator>
		<pubDate>Fri, 10 Apr 2009 02:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://webcoherence.org/?p=473#comment-28</guid>
		<description>@keyur

There is actually a bit danger to that method, especially with doc files but also with txt files.  Typing a password in a non-secure storage space - be it a txt file, or a doc file, or anywhere but an input box - leads to the storage of that file in various areas in the memory.  Nominally, that&#039;s &quot;fine&quot; - it potentially puts passwords in non-priviledged non-permament storage.  However, two caveats:

a)  Many applications make temp files in case you perform an &#039;oops&#039;.  Word does, if you&#039;ve saved it at one point.  One of my two preferred text editors, gVim, does even if you haven&#039;t, IIRC.  You close it ungracefully, and *poof* your password is on your hard drive forever.

b)  User patterns.  You use the method just described, and invariably you will open that txt file and leave it there for awhile.  If you&#039;re like most users, you will then do this often.  You might even make it permanent - a big security no-no.  Let&#039;s say you&#039;re more intelligent than that - but you do hibernate your laptop from time to time.  Now the entire contents of your memory are on your hard drive, including your password.  For quite some time.

Generally, though, I feel the big risk is anything that leads users to storing passwords in a desktop client or file.  Users will take that practice too far.

Instead, use a program like KeePass or KeePassX (Linux version.)  Stores encrypted, doubleclick the password to copy to your clipboard, paste it and your clipboard clears in 10 seconds automagically.</description>
		<content:encoded><![CDATA[<p>@keyur</p>
<p>There is actually a bit danger to that method, especially with doc files but also with txt files.  Typing a password in a non-secure storage space &#8211; be it a txt file, or a doc file, or anywhere but an input box &#8211; leads to the storage of that file in various areas in the memory.  Nominally, that&#8217;s &#8220;fine&#8221; &#8211; it potentially puts passwords in non-priviledged non-permament storage.  However, two caveats:</p>
<p>a)  Many applications make temp files in case you perform an &#8216;oops&#8217;.  Word does, if you&#8217;ve saved it at one point.  One of my two preferred text editors, gVim, does even if you haven&#8217;t, IIRC.  You close it ungracefully, and *poof* your password is on your hard drive forever.</p>
<p>b)  User patterns.  You use the method just described, and invariably you will open that txt file and leave it there for awhile.  If you&#8217;re like most users, you will then do this often.  You might even make it permanent &#8211; a big security no-no.  Let&#8217;s say you&#8217;re more intelligent than that &#8211; but you do hibernate your laptop from time to time.  Now the entire contents of your memory are on your hard drive, including your password.  For quite some time.</p>
<p>Generally, though, I feel the big risk is anything that leads users to storing passwords in a desktop client or file.  Users will take that practice too far.</p>
<p>Instead, use a program like KeePass or KeePassX (Linux version.)  Stores encrypted, doubleclick the password to copy to your clipboard, paste it and your clipboard clears in 10 seconds automagically.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nirav Ajmeri</title>
		<link>http://webcoherence.org/best-practices/email-best-practices/email-best-practice-5/comment-page-1/#comment-26</link>
		<dc:creator>Nirav Ajmeri</dc:creator>
		<pubDate>Tue, 07 Apr 2009 15:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://webcoherence.org/?p=473#comment-26</guid>
		<description>The reason of doing some twists is certain keyloggers also store the handles of window where the password was typed. So its always safe to key-in certain characters via keyboard and then use mouse to change the cursor location and key-in the other characters.</description>
		<content:encoded><![CDATA[<p>The reason of doing some twists is certain keyloggers also store the handles of window where the password was typed. So its always safe to key-in certain characters via keyboard and then use mouse to change the cursor location and key-in the other characters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: H</title>
		<link>http://webcoherence.org/best-practices/email-best-practices/email-best-practice-5/comment-page-1/#comment-25</link>
		<dc:creator>H</dc:creator>
		<pubDate>Tue, 07 Apr 2009 09:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://webcoherence.org/?p=473#comment-25</guid>
		<description>I think thats also an option, but given the fact that the keylogger would ideally also capture applications that you open and the keys you press - like ctrl-c and ctrl-v it would be easy for someone to make out that you typed your password and pasted it. However, if you type a lot of garbled text along with the password, and then select the password within lines of text, and paste it, it would be much more safe.</description>
		<content:encoded><![CDATA[<p>I think thats also an option, but given the fact that the keylogger would ideally also capture applications that you open and the keys you press &#8211; like ctrl-c and ctrl-v it would be easy for someone to make out that you typed your password and pasted it. However, if you type a lot of garbled text along with the password, and then select the password within lines of text, and paste it, it would be much more safe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keyur</title>
		<link>http://webcoherence.org/best-practices/email-best-practices/email-best-practice-5/comment-page-1/#comment-24</link>
		<dc:creator>keyur</dc:creator>
		<pubDate>Tue, 07 Apr 2009 09:07:19 +0000</pubDate>
		<guid isPermaLink="false">http://webcoherence.org/?p=473#comment-24</guid>
		<description>you can do also this thing
- type your password in other file like .txt or .doc, etc...
- then copy that password and paste into paste password field...

i think there is no problem in this method...</description>
		<content:encoded><![CDATA[<p>you can do also this thing<br />
- type your password in other file like .txt or .doc, etc&#8230;<br />
- then copy that password and paste into paste password field&#8230;</p>
<p>i think there is no problem in this method&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

