Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: suggesting passwds to users |
|---|---|
| Date: | Wed, 20 Apr 2005 14:44:55 -0500 |
I suggest passphrases.. Have the users use short sentences granted the auth system supports it. -----Original Message----- From: Kelly John Rose [mailto:mllists@ptbcanadian.net] Sent: Wednesday, April 20, 2005 8:45 AM To: James Barkley Cc: webappsec@securityfocus.com Subject: Re: suggesting passwds to users The problem I see with this is that if the users are not going to use cryptographically strong passwords in the first place, what would make you believe that they will use one of the randomly generated passwords. The big problem that exists with those passwords is that end users (in my experience) do not like those type of passwords, and will just come up with their own favourites. As well, if you provide suggested passwords, there is more potential for abuse if someone gains access to that code, or is able to watch the "suggested" passwords. But, I think most importantly, if users are not going to use secure passwords in the first place, they are not going to use these suggested passwords either. .....Kelly John Rose..... James Barkley wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A user authenticates with a username/passwd and you not only give the user the option to change his/her password any time they want but also make it mandatory that they change their password at least once every so often (e.g. 6 months). You know that users are not good at choosing good passwords, but you happen to have a good application module for generating random strong passwords. So, when the user is at the change password page and about to type in "Mets4Ever" as their new password, why not give them a list of 10 or so cryptographically strong, randomly generated passwords as suggestions for them. Assuming you are using https, then this seems like reasonable security... or am I missing something? - -Jim Barkley -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (MingW32) iD8DBQFCX2sJVtbq2E0xxN0RAu/qAJ9IniLfMUhKv2UpSweiXVfQn/wGRwCbBNQt zPNrsUoEcHrAlvIqbunriPM= =EYEs -----END PGP SIGNATURE-----
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: webapp dependencies, Amit Klein (AKsecurity) |
|---|---|
| Next by Date: | RE: Dropping connection instead of returning 400, christopher |
| Previous by Thread: | SV: suggesting passwds to users, Fredrik Hesse |
| Next by Thread: | Re: Dropping connection instead of returning 400, Kanatoko |
| Indexes: | [Date] [Thread] [Top] [All Lists] |