From: Tom Saarnio <tom.saarnio@suomi24.fi>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] SHA1 Hash calculation
Date: Wed, 23 Nov 2005 09:22:05 +0100 (MET) [thread overview]
Message-ID: <31192263.1132734126001.JavaMail.root@eni-cpps05.sth.basefarm.net> (raw)
>>
>> I am wondering whether it would be worth to implement a SHA1
hash
>> calculation over given memory address range. In this way one
could
>> assure for example that the binary image version is correct
or that
>> binary image is intact.
>
>Is the existing CRC32 checksum
not good enough for your purposes?
The CRC32 is not collision-proof in
similar fashion that SHA1. In real life, if two binary images give the
same SHA1 checksum, you can say that these binaries are identical. With
CRC32 this is not so - or at least I would not count on that :-)
br,
Tom
next reply other threads:[~2005-11-23 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 8:22 Tom Saarnio [this message]
2005-11-23 9:11 ` [U-Boot-Users] SHA1 Hash calculation Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-11-23 7:32 Tom Saarnio
2005-11-23 7:56 ` Wolfgang Denk
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=31192263.1132734126001.JavaMail.root@eni-cpps05.sth.basefarm.net \
--to=tom.saarnio@suomi24.fi \
--cc=u-boot@lists.denx.de \
/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