This attitude is the real problem. I don't mean you specifically, but generally across the web and beyond. Users are too stupid to remember more than one long word, so we'll have to force them into using mixed case and puntuation to achieve security!
Well ... yes and no. It's true that it's often done but it's not what Cracklib enforces. And yes, it's stupid---but something rather different from preventing stupid users from using "joe" as a password.
Yet every password guide or ruleset I've every read on a website goes with some variation on the 6-8 characters with at least 1 digit and 1 punctuation and "Don't share passwords between sites". We've programmed people into the very habits that lead to all the problems we are now having.

Also mostly true. I blame it on people (except for Phil Zimmermann and Randall Munroe) not actually thinking about what they're doing when writing such guides but always passing on "common knowledge" from a time when system passwords were limited to 8 characters.

However, having several passwords makes complete sense. Every day tens of thousands of passwords get snatched by trojans, and often (had it happen so several friends of mine) it's because people entered them on notoriously dodgy internet café machines. Now if I can't avoid entering say my freemailer passphrase on a potentially infected machine (I'm paranoid enough to have a Knoppix USB stick on my keyring to avoid having to but I wouldn't ask that of everyone) I'd hate the Nigerians to get the passphrase to my PGP keys and work computers as well. So I just have a handful of different passwords that I use depending on how secure I think their respective site is, and the higher security ones just don't get entered anywhere I can't be reasonably sure the system isn't safe.


In reply to Re^10: Password strength calculation by mbethke
in thread Password strength calculation by cavac

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.