5 ms·
The "expert" is still suggesting special characters instead of full sentences? Sigh.
by Someone1234 12y ago
The "expert" is still suggesting special characters instead of full sentences? Sigh.
- freehunter 12y agoI blame Active Directory and the "use strong password" which focuses on special characters and not entropy.
- Someone1234 12y agoAgreed. AD's password rule enforcement is almost completely inflexible[0] and originates from 1980s US Government requirements they incorporated to get some certification. It is completely inappropriate in 2014 and don't even get me started on how convoluted Microsoft make adding 2 factor to NT login (i.e. use our expensive convoluted solution or nothing, no RFC 6238 you can just slot in). [0] http://technet.microsoft.com/en-us/library/cc875814.aspx http://technet.microsoft.com/en-us/library/cc875814.aspx
- the-dude 12y agoAppleID does this too.
- drzaiusapelord 12y agoMeh, that's a GPO setting. Don't turn it on if you don't like it. Bill Gates isn't holding a gun to your head here. Hell, its not even turned on by default! AD can handle long passphrases. Granted, its cryptography only considers the first 14 characters, but I've read case studies where shops have moved away from complexity to minimum 14 characters and suddenly things like password resets become a thing of the past. Turns out its easier for humans to process "mydogsnameismrmittens" vs "M1tt3ns" I've tried long passphrases in embedded devices like cameras and routers. Most of the time they can't handle it. Don't knock AD as being the bad guy here. Go after the nightmarish cockup that defines the security of consumer embedded world.
- freehunter 12y agoI understand it's not actually the fault of that particular setting, it's the fault of the admins using it as a set-it-and-forget-it action. Specially my experience lies in PCI audits, where PCI DSS requirement 8.5.11 says to use passwords containing both numeric and alphabetic characters. 8.5.10 requires a password length of 7 characters. When you need to meet PCI standard, are you going to set your password policy by hand or just turn on AD's default secure password policy? The password policy which is terrible, but meets PCI requirements and makes the boss happy? And even if you make a policy that meets PCI requirements, I've been in many-a PCI audit where the auditor doesn't want to move past the password policy section if you don't use AD's 'strong password' feature. Because it takes a bit of time and effort to explain your password policy without that little checkbox. It's not Microsoft's fault that everyone uses their strong password checkbox. But Microsoft could move into the 21st century and make sure that what they label as 'strong passwords' actually meet the criteria of being strong passwords.
- tyho 12y agoWhat's worse IMO is that he says: > use some form of secure password vault on your phone [instead of writing them down] Writing passwords on a piece of paper and keeping that paper in your wallet makes it impossible for a remote hacker to obtain your passwords from you. It is only against very powerful adversaries like the government or a targeted attack where this becomes a weakness. Compare this with storing your passwords in "some form of secure password vault". 1. A remote hack targeting thousands of people at once from the comfort of ones own home is now possible, any weakness in the vault can now be exploited en mass. 2. Instead of trusting that you can keep you wallet secure, you now need to: a. Trust the manufacturer of the phone b. Trust the supplier of nearly every IC to the manufacturer of the phone. c. Trust the author of the baseband processor blob (Broadcom). d. Trust the Android operating system e. Trust the modifications to the Android operating system on your device. f. Trust Google play services (which has root access to android). g. Trust that Google will not use it's privileged position in your phone to grab your passwords on behalf of any three letter agency. h. Trust the author of the password vault 3. To make the password vault any more effective than paper in your wallet, you need to encrypt the vault with a strong pass-phrase, and you are back to square one again. 4. The chances are that the average Joe that reads that and chooses to use "some form of secure password vault" will choose a bad one. The only reason to use a "password vault" if for convenience once you have too many passwords to write on a small piece of paper in your wallet or if you face a adversary where you expect them to be able to steal your wallet. In which case just memorize some 100 bit diceware passwords which is surprisingly easy.
- pavel_lishin 12y ago> The only reason to use a "password vault" if for convenience once you have too many passwords to write on a small piece of paper in your wallet Isn't this true for most people? Paying my bills and utilities alone requires nearly a dozen passwords: bank, rent, electricity, gas, water, internet access, phone bill, health insurance, renters' insurance, car insurance.
- tyho 12y agoTo be fair, yes. I personally use Lastpass although I am not totally satisfied with it because it has not been audited and is not open source. What the "expert" was effectively telling people was to search "secure password vault" and choose the first result.