<?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: Password Masking</title>
	<atom:link href="http://www.mcgrewsecurity.com/2009/06/26/password-masking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mcgrewsecurity.com/2009/06/26/password-masking/</link>
	<description></description>
	<lastBuildDate>Sat, 13 Mar 2010 16:07:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: LonerVamp</title>
		<link>http://www.mcgrewsecurity.com/2009/06/26/password-masking/comment-page-1/#comment-37236</link>
		<dc:creator>LonerVamp</dc:creator>
		<pubDate>Mon, 29 Jun 2009 13:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=462#comment-37236</guid>
		<description>I forgot to add that this is one of those grumpy-sounding posts by Schneier. A &quot;get off my lawn!&quot; sort of moment.

If we really want to get this ornery, then we should see a companion case against regular password changing/expiring because that degrades a customer experience when they forget they changed it yesterday and have to increase support calls to work the issue out.

All in all, a useful discussion, but some things just don&#039;t need to be changed, really. :) The risk savings is low if not actually in the red...and the real risk of elaborate setups like reflections is admittedly exceedingly low for most. :)</description>
		<content:encoded><![CDATA[<p>I forgot to add that this is one of those grumpy-sounding posts by Schneier. A &#8220;get off my lawn!&#8221; sort of moment.</p>
<p>If we really want to get this ornery, then we should see a companion case against regular password changing/expiring because that degrades a customer experience when they forget they changed it yesterday and have to increase support calls to work the issue out.</p>
<p>All in all, a useful discussion, but some things just don&#8217;t need to be changed, really. :) The risk savings is low if not actually in the red&#8230;and the real risk of elaborate setups like reflections is admittedly exceedingly low for most. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LonerVamp</title>
		<link>http://www.mcgrewsecurity.com/2009/06/26/password-masking/comment-page-1/#comment-37235</link>
		<dc:creator>LonerVamp</dc:creator>
		<pubDate>Mon, 29 Jun 2009 13:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=462#comment-37235</guid>
		<description>Barnes &amp; Noble AT&amp;T Wifi access pages feature a non-masked password entry. I admit every time I type that in I feel like I&#039;m pulling down my pants, standing up, and waddling around while the login processes. I hate it.

I saw thsi fly through the pauldotcom mailing list last week, and I&#039;d restate one of my points about an unmasked password, depending on the circumstances: We lose the ability to effectively know no one else saw the password.

It&#039;s tough to watch someone type a password and be able to reproduce it. But it is not tough to get the briefest of glimpses of a password and be able to reproduce it. Especially when so many passwords are, at their base, a word or easy phrase with a few char subs and/or numbers/non-alphas behind them. 

I also am in regular position to see and be seen typing in my passwords.</description>
		<content:encoded><![CDATA[<p>Barnes &amp; Noble AT&amp;T Wifi access pages feature a non-masked password entry. I admit every time I type that in I feel like I&#8217;m pulling down my pants, standing up, and waddling around while the login processes. I hate it.</p>
<p>I saw thsi fly through the pauldotcom mailing list last week, and I&#8217;d restate one of my points about an unmasked password, depending on the circumstances: We lose the ability to effectively know no one else saw the password.</p>
<p>It&#8217;s tough to watch someone type a password and be able to reproduce it. But it is not tough to get the briefest of glimpses of a password and be able to reproduce it. Especially when so many passwords are, at their base, a word or easy phrase with a few char subs and/or numbers/non-alphas behind them. </p>
<p>I also am in regular position to see and be seen typing in my passwords.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wesley McGrew</title>
		<link>http://www.mcgrewsecurity.com/2009/06/26/password-masking/comment-page-1/#comment-37220</link>
		<dc:creator>Wesley McGrew</dc:creator>
		<pubDate>Mon, 29 Jun 2009 01:51:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=462#comment-37220</guid>
		<description>The iPhone OS that runs on my iPod Touch and my wife&#039;s iPhone does that, and I really think it&#039;s great for a device where you&#039;re likely to make typing errors, and small enough to easily move around and shield from prying eyes.

When implemented on a larger, stationary scree, though, I&#039;m not sure if it&#039;s much more secure than just showing the password unmasked.  Anyone watching over-the-shoulder or with some camera rig as described above could catch the password easily, without the user having the recourse of being able to move or shield the display.</description>
		<content:encoded><![CDATA[<p>The iPhone OS that runs on my iPod Touch and my wife&#8217;s iPhone does that, and I really think it&#8217;s great for a device where you&#8217;re likely to make typing errors, and small enough to easily move around and shield from prying eyes.</p>
<p>When implemented on a larger, stationary scree, though, I&#8217;m not sure if it&#8217;s much more secure than just showing the password unmasked.  Anyone watching over-the-shoulder or with some camera rig as described above could catch the password easily, without the user having the recourse of being able to move or shield the display.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marc</title>
		<link>http://www.mcgrewsecurity.com/2009/06/26/password-masking/comment-page-1/#comment-37207</link>
		<dc:creator>marc</dc:creator>
		<pubDate>Sun, 28 Jun 2009 22:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=462#comment-37207</guid>
		<description>Don&#039;t be so quick to throw this to the wayside. Perhaps we should employee the G1&#039;s technique, and mask characters after a second of them being visible. Once you begin typing a subsequent character, it is masked. This allows people to see that they may have mistyped a character. It may further aide HCI without dramatically reducing security.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t be so quick to throw this to the wayside. Perhaps we should employee the G1&#8217;s technique, and mask characters after a second of them being visible. Once you begin typing a subsequent character, it is masked. This allows people to see that they may have mistyped a character. It may further aide HCI without dramatically reducing security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.mcgrewsecurity.com/2009/06/26/password-masking/comment-page-1/#comment-37107</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 26 Jun 2009 16:08:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=462#comment-37107</guid>
		<description>I agree.  Also, if I see a website or application with an unmasked password, then I also assume that the people that created it have a lower level of security awareness.  If it&#039;s unmasked to the user, then it&#039;s probably plaintext in a database somewhere too.  I would probably end up using a less secure password and use the same one for every website/application.  Same goes for websites/apps that email passwords in plaintext.</description>
		<content:encoded><![CDATA[<p>I agree.  Also, if I see a website or application with an unmasked password, then I also assume that the people that created it have a lower level of security awareness.  If it&#8217;s unmasked to the user, then it&#8217;s probably plaintext in a database somewhere too.  I would probably end up using a less secure password and use the same one for every website/application.  Same goes for websites/apps that email passwords in plaintext.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
