<?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: How to create a very strong password</title>
	<atom:link href="http://www.gfi.com/blog/create-strong-password/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gfi.com/blog/create-strong-password/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=create-strong-password</link>
	<description>Brought to you by GFI Software</description>
	<lastBuildDate>Fri, 13 Sep 2013 13:27:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Lemuel</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-17573</link>
		<dc:creator>Lemuel</dc:creator>
		<pubDate>Wed, 05 Jan 2011 04:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-17573</guid>
		<description><![CDATA[Science-fiction blog i09.com recently posted a security concern regarding its mother company Gawkermedia.com. Apparently, non-latin based characters were being registered as interchangeable with each other. Because of this non-English based passwords could actually be accessed by simply typing any order of non-English based characters. Although Gawkermedia is looking into the security concern now, it has urged all its registered users with non-English based passwords to change them immediately.

So much for using completely random characters.]]></description>
		<content:encoded><![CDATA[<p>Science-fiction blog i09.com recently posted a security concern regarding its mother company Gawkermedia.com. Apparently, non-latin based characters were being registered as interchangeable with each other. Because of this non-English based passwords could actually be accessed by simply typing any order of non-English based characters. Although Gawkermedia is looking into the security concern now, it has urged all its registered users with non-English based passwords to change them immediately.</p>
<p>So much for using completely random characters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaime</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-17536</link>
		<dc:creator>jaime</dc:creator>
		<pubDate>Tue, 04 Jan 2011 21:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-17536</guid>
		<description><![CDATA[I know of certain individuals who have completely reduced the memory of their own passwords to actual muscle memory. Offhand, they can only readily recall the very first character of their password, and trace the rest through a strange remembrance of movements and actions. They’ve admitted that without a keyboard in front of them, they wouldn’t be able to easily spell out their own password, which is as secure a password as you can get I can believe.]]></description>
		<content:encoded><![CDATA[<p>I know of certain individuals who have completely reduced the memory of their own passwords to actual muscle memory. Offhand, they can only readily recall the very first character of their password, and trace the rest through a strange remembrance of movements and actions. They’ve admitted that without a keyboard in front of them, they wouldn’t be able to easily spell out their own password, which is as secure a password as you can get I can believe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bryan reeves</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-17535</link>
		<dc:creator>bryan reeves</dc:creator>
		<pubDate>Tue, 04 Jan 2011 20:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-17535</guid>
		<description><![CDATA[@jonathan

I don’t think having your passwords named after personal items is a very safe (or smart) practice of security. I think it’s already been mentioned that individuals who know you personally will be able to guess your passwords straight of the bat, but strong decryption algorithms are designed to be able to “auto-complete” trillions of possible words and key phrases that could turn out to be your password. The more random your password, the better.]]></description>
		<content:encoded><![CDATA[<p>@jonathan</p>
<p>I don’t think having your passwords named after personal items is a very safe (or smart) practice of security. I think it’s already been mentioned that individuals who know you personally will be able to guess your passwords straight of the bat, but strong decryption algorithms are designed to be able to “auto-complete” trillions of possible words and key phrases that could turn out to be your password. The more random your password, the better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emmanuel Carabott</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-16315</link>
		<dc:creator>Emmanuel Carabott</dc:creator>
		<pubDate>Fri, 17 Dec 2010 10:13:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-16315</guid>
		<description><![CDATA[@Jonathan - The biggest problem with using names is not that the password is not that complex but that it&#039;s easily guessable by anyone who knows you. Risk changes depending on the attacker obviously. I imagine you use names cause you find them easy to remember and there is no need to throw that away; feel free to use names, just change them a bit to make them both stronger and impossible to guess. This can be done by substituting a particular letter with a symbol and add a couple of numbers. For example assuming you&#039;re using a fruit&#039;s name as password, say: Apple, this could in turn be changed to 12App&#124;e24 and all you need to remember is that l is substituted with &#124; (you can do that always) and if say 24 is your favorite number you put it at the end and 1/2 of it at the beginning. That would still be easy to remember but it&#039;s a lot stronger than before.

@Richard - So far in terms of computing power the situation on the graphic card front didn&#039;t change. The ATI HD5970 is still the card with the highest rated float point operations per second. The fastest I7, the 980 is rated at 107 Gflops]]></description>
		<content:encoded><![CDATA[<p>@Jonathan &#8211; The biggest problem with using names is not that the password is not that complex but that it&#8217;s easily guessable by anyone who knows you. Risk changes depending on the attacker obviously. I imagine you use names cause you find them easy to remember and there is no need to throw that away; feel free to use names, just change them a bit to make them both stronger and impossible to guess. This can be done by substituting a particular letter with a symbol and add a couple of numbers. For example assuming you&#8217;re using a fruit&#8217;s name as password, say: Apple, this could in turn be changed to 12App|e24 and all you need to remember is that l is substituted with | (you can do that always) and if say 24 is your favorite number you put it at the end and 1/2 of it at the beginning. That would still be easy to remember but it&#8217;s a lot stronger than before.</p>
<p>@Richard &#8211; So far in terms of computing power the situation on the graphic card front didn&#8217;t change. The ATI HD5970 is still the card with the highest rated float point operations per second. The fastest I7, the 980 is rated at 107 Gflops</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: richard</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-16164</link>
		<dc:creator>richard</dc:creator>
		<pubDate>Wed, 15 Dec 2010 16:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-16164</guid>
		<description><![CDATA[And to think that the kind of hardware that was used to run these kinds of tests are pretty dated. Though they are by no means obsolete; code breakers, hackers and internet vandals definitely pack a lot more punch than the mid range gear outlined in this article. It&#039;s curious to see what kind of results we&#039;d be seeing using i7/GTX type specs; stuff that&#039;s more than affordable in today&#039;s market.]]></description>
		<content:encoded><![CDATA[<p>And to think that the kind of hardware that was used to run these kinds of tests are pretty dated. Though they are by no means obsolete; code breakers, hackers and internet vandals definitely pack a lot more punch than the mid range gear outlined in this article. It&#8217;s curious to see what kind of results we&#8217;d be seeing using i7/GTX type specs; stuff that&#8217;s more than affordable in today&#8217;s market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Chester</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-15724</link>
		<dc:creator>Jonathan Chester</dc:creator>
		<pubDate>Sun, 12 Dec 2010 17:40:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-15724</guid>
		<description><![CDATA[Incredibly interesting stuff! I could have guessed that the average four core computers could crack a fair share of passwords, but to be able to churn out over a hundred million passwords per SECOND? I think I&#039;ve to start rethinking my passwords. So much for slacking off and naming everything after my pets, my family and my ex-girlfriends. If ever I get hacked, I probably deserve it. *knocks on wood*]]></description>
		<content:encoded><![CDATA[<p>Incredibly interesting stuff! I could have guessed that the average four core computers could crack a fair share of passwords, but to be able to churn out over a hundred million passwords per SECOND? I think I&#8217;ve to start rethinking my passwords. So much for slacking off and naming everything after my pets, my family and my ex-girlfriends. If ever I get hacked, I probably deserve it. *knocks on wood*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: daniel luther</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-15714</link>
		<dc:creator>daniel luther</dc:creator>
		<pubDate>Sun, 12 Dec 2010 17:05:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-15714</guid>
		<description><![CDATA[A lot of website and software applications that require passwords now run algorithms to determine just how strong your password is (usually ranking it from weak to very strong). However, some are far more reliable than others. Some applications simply count the number of characters in the password. Others go as far as checking that back to the number of discernable dictionary words plus non alphabet text. The more random, of course, the better.]]></description>
		<content:encoded><![CDATA[<p>A lot of website and software applications that require passwords now run algorithms to determine just how strong your password is (usually ranking it from weak to very strong). However, some are far more reliable than others. Some applications simply count the number of characters in the password. Others go as far as checking that back to the number of discernable dictionary words plus non alphabet text. The more random, of course, the better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Texas Data Vault</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-13852</link>
		<dc:creator>Texas Data Vault</dc:creator>
		<pubDate>Wed, 17 Nov 2010 17:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-13852</guid>
		<description><![CDATA[Emmanuel, great post. It really shows the importance of taking the time to figure out a strong password for yourself.  I had a client just yesterday who had her Joomla website hacked. When I asked her for her user and pw so that I could login and check it out she gave me admin, password. I thought, &quot;Wow, no wonder you were hacked&quot;. I am going to send this to her and will also be posting it on my site as this was very well done. Thanks.]]></description>
		<content:encoded><![CDATA[<p>Emmanuel, great post. It really shows the importance of taking the time to figure out a strong password for yourself.  I had a client just yesterday who had her Joomla website hacked. When I asked her for her user and pw so that I could login and check it out she gave me admin, password. I thought, &#8220;Wow, no wonder you were hacked&#8221;. I am going to send this to her and will also be posting it on my site as this was very well done. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emmanuel Carabott</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-11764</link>
		<dc:creator>Emmanuel Carabott</dc:creator>
		<pubDate>Mon, 25 Oct 2010 16:18:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-11764</guid>
		<description><![CDATA[@Shane:
The article does state what password combination you need to use to get a 2 year cracking time, but perhaps it&#039;s not very clear. Basically using mixed case and numbers you need 10 characters for a GPU setup based on the article specs to go through all the combinations in 2 years. If you also add symbols to the mix 9 characters will suffice. Bear in mind that all number are approximations of how long a system would need to get to try all the combinations. In real life it depends on how many guesses the cracking programs will take before reaching the correct combination.

@Michael G:
The most frightening part of using GPU is that it can easily scale. How much money you put in it is what determines how long it will take to crack a password. Double the amount of GPUs and you half the time needed to go though all the combinations; thus the times above are only a baseline indication of how long it will take. 

I have to agree with Richard, remote login attempts will propel the time needed to try a password by a lot! Basically all the advantages of using GPUs will be lost as the time required to establish the connection and try the password will be a lot more than the time required to try and guess the password or even generate the password combination. The only danger GPUs pose to passwords in this context is if someone has access to the hash itself so protecting that is paramount!]]></description>
		<content:encoded><![CDATA[<p>@Shane:<br />
The article does state what password combination you need to use to get a 2 year cracking time, but perhaps it&#8217;s not very clear. Basically using mixed case and numbers you need 10 characters for a GPU setup based on the article specs to go through all the combinations in 2 years. If you also add symbols to the mix 9 characters will suffice. Bear in mind that all number are approximations of how long a system would need to get to try all the combinations. In real life it depends on how many guesses the cracking programs will take before reaching the correct combination.</p>
<p>@Michael G:<br />
The most frightening part of using GPU is that it can easily scale. How much money you put in it is what determines how long it will take to crack a password. Double the amount of GPUs and you half the time needed to go though all the combinations; thus the times above are only a baseline indication of how long it will take. </p>
<p>I have to agree with Richard, remote login attempts will propel the time needed to try a password by a lot! Basically all the advantages of using GPUs will be lost as the time required to establish the connection and try the password will be a lot more than the time required to try and guess the password or even generate the password combination. The only danger GPUs pose to passwords in this context is if someone has access to the hash itself so protecting that is paramount!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sue Walsh</title>
		<link>http://www.gfi.com/blog/create-strong-password/comment-page-1/#comment-10430</link>
		<dc:creator>Sue Walsh</dc:creator>
		<pubDate>Mon, 27 Sep 2010 04:14:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=2890#comment-10430</guid>
		<description><![CDATA[Great post! I have always used a mix of mixed case letters and numbers for my passwords but I never thought of using symbols before. That&#039;s an excellent idea. 

Richard, it&#039;s funny you should mention disabling after so many bad login attempts. I was just thinking about how uneasy I feel about the fact one of the two banks I use lets you make unlimited login attempts. They don&#039;t lock the account after a certain amount of failed logins. My other bank on the other hand locks you out after the second failed attempt. Think one could learn something from the other?]]></description>
		<content:encoded><![CDATA[<p>Great post! I have always used a mix of mixed case letters and numbers for my passwords but I never thought of using symbols before. That&#8217;s an excellent idea. </p>
<p>Richard, it&#8217;s funny you should mention disabling after so many bad login attempts. I was just thinking about how uneasy I feel about the fact one of the two banks I use lets you make unlimited login attempts. They don&#8217;t lock the account after a certain amount of failed logins. My other bank on the other hand locks you out after the second failed attempt. Think one could learn something from the other?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: www.gfi.com @ 2013-09-15 06:16:08 by W3 Total Cache --