Enforcing Crytographically Strong Passwords
Saqib Ali writes "The WebAppSec mailing list at SecurityFocus is currently having an interesting discussion on how to force users to use cryptographically strong passwords. The original poster suggested displaying a list of randomly generated password for the user to choose from. Two issues pointed with this concept, were Shoulder surfing and the fact that a bunch of randomly generated passwords are hard to remember. A counter proposal was to use pronounceable but randomly generated password. A full summary of this discussion is available. Any thoughts from slashdotters?"
No-one will ever guess my super-secret password: GOD
To Terminate, or not to Terminate, that's the question - SCSIROB
We faced the same problem when generating random passwords for users and decided that the best method was to generate two short (4-6 characters) english words with a number at the end. This creates passwords such as swimeasy12, turnright62, sidedoor81, etc. These proved to be very easy to rememeber and we only had one complaint: A secretary had her random password set to fatgirl13 and was really not happy, even after we expained the random process.
Input error. Replace user and press any key to continue.
Stop posting my password on Slashdot, Zonk!
/^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
I find that test/test works fine for my root login...
I still say that using one's spouse's name as the password is best.
If you think it's a weak policy for your organization, then your employees aren't changing their spouses fast enough....
that builds grammatical sentences by taking a valid syntax and plugging in random verbs, nouns and adjectives in the right places.
Or I could just send you the documentation we got back with the last project we outsourced to India.
Glonoinha the MebiByte Slayer