Re: md5sum not aware of different end-of-line conventions

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Shriramana Sharma on 12/16/2006 3:25 AM:
> Hello.
> 
> Recently I tried to verify the md5sums of a few files using md5sum -c.
> The md5 file was created in Windows and therefore it contained CR+LF as
> the end-of-line character. md5sum threw up an error saying it could not
> find the files mentioned. Apparently it thought the CR char is also part
> of the filename since it is searching only for LF (per *nix convention)
> as the EOL char. It worked however after I changed the EOL char using my
> editor.

Thanks for the report; you are not the first to request it.  I've been
meaning to submit a patch to *sum (md5sum, sha1sum, and others all share
the same underlying code) that encodes \r like it currently encodes \n, so
that it can then be taught on verification to ignore unencoded \r.  But I
haven't yet made time for this particular improvement.

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFhC2984KuGfSFAYARApt+AKDZmzIl0/asAWtq847URLBPxEUb+QCfXVc/
N4YNpHljncg3aB9W6DPEoQQ=
=Dubd
-----END PGP SIGNATURE-----