Script 1, stand alone script passing the name of a zip file:
use Digest::SHA1; $sha1 = Digest::SHA1->new; $fhIN = $ARGV[0]; open(IN,$fhIN) || die "\ncan open file for input"; binmode IN; $sha1->addfile(IN); $digest = $sha1->hexdigest; print "$digest\n";
Output:50bd187a208112091b035c62209baf9742c243bd
script 2, part of a CGI, passing the path to the same file as above:
sub generateDigest{ my ($file) = @_; my $sha1 = Digest::SHA1->new; open(FILE, $file) || die; binmode FILE; $sha1->addfile(*FILE); close(FILE); my $digest = $sha1->hexdigest; warn "$digest"; return $digest; }
Output: 7ba6487fefcc4467b21deccac79b38d7d3b69bf2
Why the difference?

In reply to Digest::Sha1 differences 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.