From: Andrew Shugg <andrew@neep.com.au>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] problems with checksums
Date: Thu, 12 Jul 2001 23:57:52 +0800 [thread overview]
Message-ID: <20010712235750.Q17064@neep.com.au> (raw)
In-Reply-To: <20010712082908.K531@tausq.org>; from randolph@tausq.org on Thu, Jul 12, 2001 at 08:29:09AM -0700
Quoth Randolph Chung:
> Be careful, Debian uses BSD md5sum instead of GNU md5, some other
> Linux systems use GNU md5sum. They produce different output for the
> same input!
It does? I've never seen a GNU md5sum. BSD's "md5" program has a
different output format although the algorithm is the same. Also the
various checksum programs I've found for Windows and Mac OS refer to the
algorithm as 'RSA MD5'. The only times I've found a discrepancy between
md5sum programs is the Windows command-line one that rudely assumes data
is ascii by default and has to be given the '-b' flag for checksums to
match those generated under a Unix or Mac.
(If you can set me straight off-list I'd be happy to listen.)
Andrew.
--
Andrew Shugg <andrew@neep.com.au> http://www.neep.com.au/
"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there? Well I'd like to meet him. I could do with a good laugh."
next prev parent reply other threads:[~2001-07-12 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 12:57 [parisc-linux] problems with checksums rpengelly
2001-07-12 13:07 ` Richard Hirst
[not found] ` <001e01c10ad6$588cb4e0$0f809b8e@ati.stlawrencec.on.ca>
[not found] ` <20010712145615.E18375@linuxcare.com>
2001-07-12 15:05 ` rpengelly
2001-07-12 15:29 ` Randolph Chung
2001-07-12 15:55 ` Randolph Chung
2001-07-12 16:13 ` Matthew Wilcox
2001-07-12 15:57 ` Andrew Shugg [this message]
2001-07-12 19:00 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2001-07-12 15:30 Matthieu Le Corre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010712235750.Q17064@neep.com.au \
--to=andrew@neep.com.au \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox