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: | Mon, 18 Apr 2005 14:38:14 -0400 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Saqib Ali wrote:
| 1) Shoulder surfing might be problem for this type of solution, | since you will need to display the password on the screen for the | user to choose one.
I agree this is a threat.
| | 2) In my experience, if the password is randomly generated bunch of | letters, it becomes hard for the user to remember, and they tend | to write them down on a piece of paper and paste on the bottom of | the keyboard. :-(
I suppose you could generate word-form passwords such as g@L@xi3$ (galaxies) to try and manage the user. You have to compare the threats: is it more of a threat for a user to write down their password or to use the same password they have on 50 other web sites. I'm not sure what the answer is here....
| | 3) Your system will NOT generate "random" password, instead it will | generate "PSUEDO-RANDOM" passwords.
No offense, but DUH! Isn't it impossible for a computer to generate a truly random number without user interaction (such as random mouse movements to generate entropy, as gnupg asks the user to do when generating pub/priv keypairs)? Nevertheless, as your pseudo-randomness tends toward zero you will hit a point that is statistically acceptable. Like when scientists agree that 1x10^-200 chance of occurence can reasonably be considered impossible.
| this process can can be duplicated by an attacker to generate a | list of all possible passwords, and use it in a dictionary attack. | | | An easier and better approach is to let the user choose their own | password, and then run a dictionary/bruteforce attack on the | password file to make sure they are strong password. If they are | not, prompt the user to change them. | This is a not a bad idea, but I'm not sure my server can handle doing a dictionary/bruteforce attack on a user chosen password on the fly in enough time to return a response to the user. Some of these systems are running pretty minimal hardware. There is trade-space here that can be explored which is size-of-dictionary versus computation-time but what is the inflection point where you are searching too few words?
Anyway, thanks for the feedback.
- -Jim
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (MingW32)
iD8DBQFCY/6QVtbq2E0xxN0RAulUAJ9xQKdpm0NxDetUpS1Fb1cp7UHNfQCgg0jR mrYH8RTpknU7aBWXdKCDuS0= =ahVn -----END PGP SIGNATURE-----
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: suggesting passwds to users, Saqib Ali |
|---|---|
| Next by Date: | RE: Dropping connection instead of returning 400, Matt Fisher |
| Previous by Thread: | Re: suggesting passwds to users, Saqib Ali |
| Next by Thread: | Re: suggesting passwds to users, Saqib Ali |
| Indexes: | [Date] [Thread] [Top] [All Lists] |