 | | Re: Automated password appraisal (Re: New feature: Article rating) —Larry Pieniazek
|
| | | (...) I am starting to think that this password checker, in its current form (which I'd like to see left accessable as it IS useful) shouldn't actually block a password. It should tell me that "maybe this isn't a good choice" but it doesn't know (...) (25 years ago, 30-Mar-00, to lugnet.admin.general) !
|
| | | |
| | | | | Re: Automated password appraisal (Re: New feature: Article rating) —Todd Lehman
|
| | | | | (...) Yum, yum! :-s Well, ya gotta also figure that decreasing the safety margin from 100,000 to 1000 is one thing (bad -- and I don't think that's case here), but decreasing it from, say, eleventeen hundred quintrillion down to fifty-seven (...) (25 years ago, 31-Mar-00, to lugnet.admin.general)
|
| | | | | |
| | | | | Re: Automated password appraisal (Re: New feature: Article rating) —Selçuk Göre
|
| | | | Larry Pieniazek wrote: <snip> (...) I'm not a guru on the subject by any means, but while an attacker using wordlists and trying to crack a password with bruteforce or something like, I mean, by trial and error, I think any combination of dates are (...) (25 years ago, 31-Mar-00, to lugnet.admin.general)
|
| | | | |
| | | | | | Re: Automated password appraisal (Re: New feature: Article rating) —Larry Pieniazek
|
| | | | (...) from (...) ALL (...) that (...) numbers (...) This was a hypothetical example. Dates are not actually good passwords, but they're easy to use to demonstrate differences in context. my birthday is a bad password for me (one of the first few (...) (25 years ago, 31-Mar-00, to lugnet.admin.general)
|
| | | | |
