Ew! I think doing the 22 char test is a valid first step. After all, how many users actually will use a 22 char password. Secondly, for the really paraniod, one could then run a quick dictionary test against it just to ensure. Thirdly, an occasional vgrep of the password data may be needed ( darn that very capable human brain! ).
But the best answer is, IMHO, educational in nature. Just like you cannot legislate against stupidity, you cannot alway program against it either.
UPDATE: You could also have the "admin" function kick off an email or somesuch each time to remind the priviliged of their duty to hash. It would be annoying for them, sure. But they could never complain that they didn't know better.
HTH
--
idnopheq
Apply yourself to new problems without preparation, develop confidence in your ability to to meet situations as they arrise.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.