<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: On online security and password policies</title>
	<atom:link href="http://aralbalkan.com/1392/feed" rel="self" type="application/rss+xml" />
	<link>http://aralbalkan.com/1392</link>
	<description>Passionate geekisms.</description>
	<lastBuildDate>Sun, 12 Feb 2012 17:52:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Aral</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-163036</link>
		<dc:creator>Aral</dc:creator>
		<pubDate>Fri, 04 Jul 2008 08:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-163036</guid>
		<description>Hi Daniel,

I was actually thinking of devoting a blog post to just that. I think most people would be much safer if they chose one password for their email and used another for everything else (of course, they could choose different ones for every service -- but again, we get into the issue of memorizing them and writing them down.) 

Thanks for bringing it up!</description>
		<content:encoded><![CDATA[<p>Hi Daniel,</p>
<p>I was actually thinking of devoting a blog post to just that. I think most people would be much safer if they chose one password for their email and used another for everything else (of course, they could choose different ones for every service &#8212; but again, we get into the issue of memorizing them and writing them down.) </p>
<p>Thanks for bringing it up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: daniel larsen</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-162920</link>
		<dc:creator>daniel larsen</dc:creator>
		<pubDate>Thu, 03 Jul 2008 23:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-162920</guid>
		<description>The biggest gotcha with using the same password in multiple places: Using your email password on a site where your login name is your email address.  Hello! You just handed them your email address with its associated password.  I am amazed how many people in my family have done this. (ok, I admit it...I did it a few years ago too before it dawned on me how stupid that was)</description>
		<content:encoded><![CDATA[<p>The biggest gotcha with using the same password in multiple places: Using your email password on a site where your login name is your email address.  Hello! You just handed them your email address with its associated password.  I am amazed how many people in my family have done this. (ok, I admit it&#8230;I did it a few years ago too before it dawned on me how stupid that was)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louise</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-161585</link>
		<dc:creator>Louise</dc:creator>
		<pubDate>Mon, 30 Jun 2008 13:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-161585</guid>
		<description>This type of discussion can lead to so many places and I was wondering what your thoughts on password managers were. 

Louise 

(*disclaimer - I write for a password manager)</description>
		<content:encoded><![CDATA[<p>This type of discussion can lead to so many places and I was wondering what your thoughts on password managers were. </p>
<p>Louise </p>
<p>(*disclaimer &#8211; I write for a password manager)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Arno</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-161501</link>
		<dc:creator>David Arno</dc:creator>
		<pubDate>Mon, 30 Jun 2008 08:20:09 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-161501</guid>
		<description>I too have seen passwords written on post-it notes stuck to monitors. To use this as an argument against secure web passwords is just plain ridiculous though. A weak password on a website can be easily cracked by a hacker anywhere in the world. Try as he might though, that hacker will not be able to gain access to a password on a post-it note without gaining physical access to the room containing the monitor.

My personal bugbear over passwords is with idiot sysadmins that enforce constantly changing passwords. At one place I worked a few years back, passwords had to be changed every month and it remembered - and refused to let you reuse - the previous ten passwords. The solution I came up with was to use passwords such as:

december2002, january2003, February2003...

Completely insecure and solely due to a ridiculously overzealous password policy.</description>
		<content:encoded><![CDATA[<p>I too have seen passwords written on post-it notes stuck to monitors. To use this as an argument against secure web passwords is just plain ridiculous though. A weak password on a website can be easily cracked by a hacker anywhere in the world. Try as he might though, that hacker will not be able to gain access to a password on a post-it note without gaining physical access to the room containing the monitor.</p>
<p>My personal bugbear over passwords is with idiot sysadmins that enforce constantly changing passwords. At one place I worked a few years back, passwords had to be changed every month and it remembered &#8211; and refused to let you reuse &#8211; the previous ten passwords. The solution I came up with was to use passwords such as:</p>
<p>december2002, january2003, February2003&#8230;</p>
<p>Completely insecure and solely due to a ridiculously overzealous password policy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Farran</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-161158</link>
		<dc:creator>Alex Farran</dc:creator>
		<pubDate>Sun, 29 Jun 2008 10:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-161158</guid>
		<description>I don&#039;t think services like twitter and facebook, which don&#039;t handle very sensitive data, are particularly concerned with security.  It&#039;s not about whether the account gets hacked, but who&#039;s responsible if it is.  A strong password requirement protects them from dictionary attacks, and after that it&#039;s your responsibility to keep the account secure.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think services like twitter and facebook, which don&#8217;t handle very sensitive data, are particularly concerned with security.  It&#8217;s not about whether the account gets hacked, but who&#8217;s responsible if it is.  A strong password requirement protects them from dictionary attacks, and after that it&#8217;s your responsibility to keep the account secure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aral</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-161157</link>
		<dc:creator>Aral</dc:creator>
		<pubDate>Sun, 29 Jun 2008 10:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-161157</guid>
		<description>Hey Mario,

That&#039;s always a concern I share too.

There&#039;s nothing worse than to be forced to use a strong password only to have it stored in plain text and (here&#039;s the best bit) have it emailed to you after signing up!

@robs: Your comment doesn&#039;t make any sense. 

&lt;blockquote&gt;&lt;p&gt;’strong passwords are bad.. because a user is not able to type it fast. that means everybody can copy the password. you should force the user to choose a password which he can write in less than 0.5s.’&lt;/p&gt;&lt;p&gt;sounds good, right?&lt;/p&gt;&lt;/blockquote&gt;

You do know that password fields don&#039;t show you the password you&#039;re typing, right? So, no, it doesn&#039;t sound good at all; sounds quite daft, actually.

&lt;blockquote&gt;&lt;p&gt;how about reading some security papers before preaching bad practices?&lt;/p&gt;&lt;/blockquote&gt;

How about rationally addressing the issues that I raise and engaging in intelligent debate to further our collective understanding of the topic? Your comment is sarcastic but doesn&#039;t make a rational argument.</description>
		<content:encoded><![CDATA[<p>Hey Mario,</p>
<p>That&#8217;s always a concern I share too.</p>
<p>There&#8217;s nothing worse than to be forced to use a strong password only to have it stored in plain text and (here&#8217;s the best bit) have it emailed to you after signing up!</p>
<p>@robs: Your comment doesn&#8217;t make any sense. </p>
<blockquote><p>’strong passwords are bad.. because a user is not able to type it fast. that means everybody can copy the password. you should force the user to choose a password which he can write in less than 0.5s.’</p>
<p>sounds good, right?</p>
</blockquote>
<p>You do know that password fields don&#8217;t show you the password you&#8217;re typing, right? So, no, it doesn&#8217;t sound good at all; sounds quite daft, actually.</p>
<blockquote><p>how about reading some security papers before preaching bad practices?</p>
</blockquote>
<p>How about rationally addressing the issues that I raise and engaging in intelligent debate to further our collective understanding of the topic? Your comment is sarcastic but doesn&#8217;t make a rational argument.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Farid Abdulhadi</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-160813</link>
		<dc:creator>Farid Abdulhadi</dc:creator>
		<pubDate>Sat, 28 Jun 2008 13:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-160813</guid>
		<description>From a usability point of view, I think all websites and applications should encourage their users to choose a strong password even if it’s not required. Just have an indicator showing the strength of the password and then let the user decide. If it is a weak password you could always give the users tips on what a stronger password would be like.
As Aral is saying, at times it could be wrong to force the user to go for a password that probably will be forgotten by the end of the day. In some cases it’s just better that the user has a weak password that nobody knows about as opposed to getting a stronger one but writing it down somewhere.

Mario brings up a good point in his comment. I have actually seen passwords being stored as plain text! This is just wrong and no website should do this. Always encrypt the user’s password before storing it. Another irritating thing is when some websites send you an email with your password. It’s ok to send a randomly generated password if the user has forgotten it and requested it but don’t send an email with the users password.

Thanks for the article Aral, makes one think.</description>
		<content:encoded><![CDATA[<p>From a usability point of view, I think all websites and applications should encourage their users to choose a strong password even if it’s not required. Just have an indicator showing the strength of the password and then let the user decide. If it is a weak password you could always give the users tips on what a stronger password would be like.<br />
As Aral is saying, at times it could be wrong to force the user to go for a password that probably will be forgotten by the end of the day. In some cases it’s just better that the user has a weak password that nobody knows about as opposed to getting a stronger one but writing it down somewhere.</p>
<p>Mario brings up a good point in his comment. I have actually seen passwords being stored as plain text! This is just wrong and no website should do this. Always encrypt the user’s password before storing it. Another irritating thing is when some websites send you an email with your password. It’s ok to send a randomly generated password if the user has forgotten it and requested it but don’t send an email with the users password.</p>
<p>Thanks for the article Aral, makes one think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cody</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-160556</link>
		<dc:creator>Cody</dc:creator>
		<pubDate>Fri, 27 Jun 2008 17:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-160556</guid>
		<description>Hey Aral,

I agree with you, sites like a social networking application shouldn&#039;t require super strong passwords. I generally have a light password I use for these types of sites, and a stronger one that I use (with variations) for more secure things like my banking. Its incredibly frustrating when you can&#039;t use something you typically use elsewhere because your missing a capitol letter or something. I&#039;m just talking from a usability standpoint, not from a security standpoint. 

The one thing I&#039;d like to point out is that sites that have added stronger password requirements don&#039;t typically do this retroactively. For example I still keep a hotmail account that I opened in 1998. At that time I could have an all letter 5 character password. I can still log in today with that same password. I&#039;d expect if making a stronger password was that important that I would have gotten a message at some point at least encouraging me to change it, it not requiring me to do so when I logged into the account. 

I&#039;d say its fine that a site requires stronger passwords, but they need to let you know that in a clear and usable way up front (pownce does a great job with this). Thanks for the post!</description>
		<content:encoded><![CDATA[<p>Hey Aral,</p>
<p>I agree with you, sites like a social networking application shouldn&#8217;t require super strong passwords. I generally have a light password I use for these types of sites, and a stronger one that I use (with variations) for more secure things like my banking. Its incredibly frustrating when you can&#8217;t use something you typically use elsewhere because your missing a capitol letter or something. I&#8217;m just talking from a usability standpoint, not from a security standpoint. </p>
<p>The one thing I&#8217;d like to point out is that sites that have added stronger password requirements don&#8217;t typically do this retroactively. For example I still keep a hotmail account that I opened in 1998. At that time I could have an all letter 5 character password. I can still log in today with that same password. I&#8217;d expect if making a stronger password was that important that I would have gotten a message at some point at least encouraging me to change it, it not requiring me to do so when I logged into the account. </p>
<p>I&#8217;d say its fine that a site requires stronger passwords, but they need to let you know that in a clear and usable way up front (pownce does a great job with this). Thanks for the post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: robs</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-160524</link>
		<dc:creator>robs</dc:creator>
		<pubDate>Fri, 27 Jun 2008 15:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-160524</guid>
		<description>talking about security is extremely delicate and difficult. i&#039;m always amazed how many ppl give &quot;advice&quot; on such topics.

i wouldn&#039;t care less if they just use their bad practice on their own. but no! they have to preach it to the whole world.

@jason
&quot;Victor is completely wrong…&quot;

.. let&#039;s hope you&#039;re not completely wrong:

&#039;wanu3ved3xoby&#039;

&quot;what a great password!&quot; some security nubs might claim. or is it?
well it must be! it looks really good!

execpt for my boss&#039; password is &#039;wanu3ved3xobx&#039; but i&#039;m sure it&#039;s secure anyway, because it looks complicated!


@aral
why do you write such things? you could also write:

&#039;strong passwords are bad.. because a user is not able to type it fast. that means everybody can copy the password. you should force the user to choose a password which he can write in less than 0.5s.&#039;

sounds good, right?


@all
how about reading some security papers before preaching bad practices?

don&#039;t take it personally.. such things just make me angry :)

cheers robs</description>
		<content:encoded><![CDATA[<p>talking about security is extremely delicate and difficult. i&#8217;m always amazed how many ppl give &#8220;advice&#8221; on such topics.</p>
<p>i wouldn&#8217;t care less if they just use their bad practice on their own. but no! they have to preach it to the whole world.</p>
<p>@jason<br />
&#8220;Victor is completely wrong…&#8221;</p>
<p>.. let&#8217;s hope you&#8217;re not completely wrong:</p>
<p>&#8216;wanu3ved3xoby&#8217;</p>
<p>&#8220;what a great password!&#8221; some security nubs might claim. or is it?<br />
well it must be! it looks really good!</p>
<p>execpt for my boss&#8217; password is &#8216;wanu3ved3xobx&#8217; but i&#8217;m sure it&#8217;s secure anyway, because it looks complicated!</p>
<p>@aral<br />
why do you write such things? you could also write:</p>
<p>&#8216;strong passwords are bad.. because a user is not able to type it fast. that means everybody can copy the password. you should force the user to choose a password which he can write in less than 0.5s.&#8217;</p>
<p>sounds good, right?</p>
<p>@all<br />
how about reading some security papers before preaching bad practices?</p>
<p>don&#8217;t take it personally.. such things just make me angry :)</p>
<p>cheers robs</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason The Saj</title>
		<link>http://aralbalkan.com/1392/comment-page-1#comment-160491</link>
		<dc:creator>Jason The Saj</dc:creator>
		<pubDate>Fri, 27 Jun 2008 13:20:49 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1392#comment-160491</guid>
		<description>Victor is completely wrong...

Because L33t does not always guarantee you will remember your password. For example:

x site has a 8 character minimum.
y site has a restriction on non-alpha numerics
z site refuses spaces
q site wants a 4-digit pin

The problem is every site is different. So it&#039;s impossible to make a password you can use everywhere.  I like to have &quot;password levels&quot;. I have one for public internet, a different form for financial sites, etc.</description>
		<content:encoded><![CDATA[<p>Victor is completely wrong&#8230;</p>
<p>Because L33t does not always guarantee you will remember your password. For example:</p>
<p>x site has a 8 character minimum.<br />
y site has a restriction on non-alpha numerics<br />
z site refuses spaces<br />
q site wants a 4-digit pin</p>
<p>The problem is every site is different. So it&#8217;s impossible to make a password you can use everywhere.  I like to have &#8220;password levels&#8221;. I have one for public internet, a different form for financial sites, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

