<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
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:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>gHacks Technology News &#124; Latest Tech News, Software And Tutorials &#187; weak-passwords</title> <atom:link href="http://www.ghacks.net/tag/weak-passwords/feed/" rel="self" type="application/rss+xml" /><link>http://www.ghacks.net</link> <description>A technology news blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description> <lastBuildDate>Fri, 10 Feb 2012 20:51:26 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/> <item><title>How Long It Would Take To Hack A Password</title><link>http://www.ghacks.net/2011/11/27/how-long-it-would-take-to-hack-a-password/</link> <comments>http://www.ghacks.net/2011/11/27/how-long-it-would-take-to-hack-a-password/#comments</comments> <pubDate>Sun, 27 Nov 2011 19:58:57 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Online Services]]></category> <category><![CDATA[Security]]></category> <category><![CDATA[password]]></category> <category><![CDATA[password strength]]></category> <category><![CDATA[weak-passwords]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=53218</guid> <description><![CDATA[Password strength has become more of a issue in recent years. While it has always been important to select secure passwords, advancements in processing power and distributed computing (for instance cloud computing) have made it more of a pressing matter. Passwords that may have taken weeks or years to crack in the past are now [...]]]></description> <content:encoded><![CDATA[<p>Password strength has become more of a issue in recent years. While it has always been important to select secure passwords, advancements in processing power and distributed computing (for instance cloud computing) have made it more of a pressing matter. Passwords that may have taken weeks or years to crack in the past are now crackable in days or even hours. That&#8217;s a big security issue considering that many computer users are still selecting weak passwords as their account passwords.</p><p>Services that test a password strength can help users in evaluating their passwords. Will it take days, years or even longer to crack a selected password? That&#8217;s what How Secure Is My Password will tell you.</p><p><a
href="http://www.ghacks.net/wp-content/uploads/2011/11/how-secure-is-my-password.jpg"><img
src="http://www.ghacks.net/wp-content/uploads/2011/11/how-secure-is-my-password-600x310.jpg" alt="how secure is my password" title="how secure is my password" width="600" height="310" class="alignnone size-medium wp-image-53219" /></a></p><p>Just head over to the service&#8217;s website and enter a password in the form. You do not necessarily have to enter a password that you use actively. You can alternatively enter a comparable password to find out how long it would take to hack your password with a brute force, or maybe a combined dictionary and brute force attack.</p><p><a
href="http://www.ghacks.net/wp-content/uploads/2011/11/strong-password.jpg"><img
src="http://www.ghacks.net/wp-content/uploads/2011/11/strong-password-600x232.jpg" alt="strong-password" title="strong-password" width="600" height="232" class="alignnone size-medium wp-image-53220" /></a></p><p>Experienced computer users know that they need to pick passwords that contain upper and lower case letters, digits as well as special characters to make it secure. Length suggestions vary from 12 to 16 in most cases. The How Secure Is My Password service suggests to use passwords with a length of at least 16 characters.</p><p>The password checker can be an eye opener for users who are using weak passwords. You can try out the service <a
href="http://www.howsecureismypassword.net/">here</a> or check our <a
href="http://www.ghacks.net/2010/08/11/how-secure-is-a-password/">How Secure Is A Password</a> guide for suitable alternatives.</p><p>But the service is not only displaying the time it would approximately take to hack your password, it also displays information and tips that can help you select a more secure password. In addition, it compares the selected password against the list of the top 10k passwords used on the Internet.</p><p>The estimated time to hack a password is based on the processing power of a modern desktop PC. Depending on the infrastructure used, it may take considerable less time to hack a password.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2011/11/27/how-long-it-would-take-to-hack-a-password/feed/</wfw:commentRss> <slash:comments>15</slash:comments> </item> <item><title>Weak Passwords</title><link>http://www.ghacks.net/2007/03/27/weak-passwords/</link> <comments>http://www.ghacks.net/2007/03/27/weak-passwords/#comments</comments> <pubDate>Tue, 27 Mar 2007 05:19:03 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Hacking]]></category> <category><![CDATA[The Web]]></category> <category><![CDATA[brute-force]]></category> <category><![CDATA[password-generation]]></category> <category><![CDATA[passwords]]></category> <category><![CDATA[strategy]]></category> <category><![CDATA[weak-passwords]]></category> <guid
isPermaLink="false">http://www.ghacks.net/2007/03/27/weak-passwords/</guid> <description><![CDATA[I came upon the article "How I would hack your weak passwords" yesterday and pondered if I should write an article about it. I decided that it would be worth it. The author of the article details how he would try and find out your passwords and get access to all of your accounts in the end. His first approach would be to use the most common used passwords by users on the net. He needs information about your personal life for some passwords but those information can be obtained pretty fast through social engineering. Trying those "top 10" passwords would already cover a large percentage of online users, statistically speaking that is.]]></description> <content:encoded><![CDATA[<p>I came upon the article &#8220;<a
href="http://onemansblog.com/2007/03/26/how-id-hack-your-weak-passwords/" target="_blank">How I would hack your weak passwords</a>&#8221; yesterday and pondered if I should write an article about it. I decided that it would be worth it. The author of the article details how he would try and find out your passwords and get access to all of your accounts in the end. His first approach would be to use the most common used passwords by users on the net. He needs information about your personal life for some passwords but those information can be obtained pretty fast through social engineering. Trying those &#8220;top 10&#8243; passwords would already cover a large percentage of online users, statistically speaking that is.</p><p>The common password approach is the one that could give him instant success if the user is really using one of those common passwords for his accounts. His next approach would be to brute force his way in by brute forcing the password on a website that has weak security. Those sites would not react if large amounts of password requests would come in in short time. Most sites however ban IPs at least temporary after several failed attempts, still no problem if you know how to use proxies to attack with different IPs.</p><p><span
id="more-1349"></span></p><p>But the brute force programs that he suggests are way outdated. Brutus ? wwwHack ? That&#8217;s last millennium. Current state of the art bruteforcers for basic authorization and form protected sites are <a
href="http://carpetboy.deny.de/" target="_blank">C-Force</a> or Sentry. The brute force approach has one disadvantage. If you do not know the username you have to try username and password combinations and there is no guarantee that you will discover the combination for the user that you want to hack. You could get login details for other users which are absolutely worthless to you. This means, bruteforcing is only an option if you know the username of the user.</p><p>There are actually two ways to bruteforce an account. The first would be to use pregenerated lists of usernames and passwords or try combinations to get into an account. The second to try every char combination possible. It should be noted that the second option could very well last several years or even centuries depending on the size of the selected password.</p><p>So, bruteforcing is not really an option and he is not explaining how he would get the username of the user in question except mentioning cookies. Cookies are stored on the targets machine which would mean that he needs either access to that machine or an exploit to get them while the user is online. Not very practicable.</p><p>So, what can users learn from his analysis ?</p><ul><li>Don&#8217;t overuse passwords, it&#8217;s more secure to use different passwords. If you only use one password someone who finds this one out gets access to everything else that is protected by that single password</li><li>Don&#8217;t use passwords that are easy to guess or common. No names, no sport teams, relatives, pets, work related, hobbies , and so on</li><li>Use numbers and special chars if possible to increase the security of the password. Remember that size matters.</li><li>Write them down locally and put them in a safe or use a software that encrypts them. You could for instance use a True Crypt partition to store a textfile with your passwords in them</li><li>Every password could be important to gain additional information about a user, never choose weak ones</li></ul> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2007/03/27/weak-passwords/feed/</wfw:commentRss> <slash:comments>12</slash:comments> </item> </channel> </rss>
