It looks like other people have already suggested alternatives to crypt, but if you are set on using crypt, here's two suggestions

1. You should always send the user's entire encrypted password as the salt, not just the first two characters:
$password = crypt($INPUT{'password'},$encrypted_password);

2. If you are storing the passwords in mysql, there might be an easier, non-perl solution to authentication for you using the mysql builtin function 'PASSWORD':

my $user = $dbh->quote( $INPUT{'user'} ); my $input_pass = $dbh->quote( $INPUT{'password'} ); my $sth = $dbh->prepare ( "SELECT pass as encrypted_password, PASSWORD( $input_pass , pass ) as input_password WHERE user like $user FROM passwd_table " );


In reply to Re: Is this use of crypt() appropriate? by ehdonhon
in thread Is this use of crypt() appropriate? by Anonymous Monk

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.