On 9/26/20, Michael Stone <mst...@debian.org> wrote: > On Sat, Sep 26, 2020 at 02:11:30PM +0200, Albretch Mueller wrote: >>On 9/25/20, Michael Stone <mst...@debian.org> wrote: >>> Just one would be good enough (pick the sha256sum). What you're doing is >>> a waste of time. If you want to future proof then use sha3, via the >>> rhash package. >> >> Something that I have noticed is that texts are too close to people's >>hearts to expect for people to just be technical about them. I use >>those three algorithms because some people "understand", md5 and not >>sha###sum. I mean, you may get some legacy data with their md5sum but >>the maintainers of the data may not be around. Once I found an rsync >>log that included the CRC signatures, that is why I include these >>kinds fo algorithms. > > Sorry, still makes no sense and is a waste of time. You're creating new > hashes right now, it doesn't matter if someone else might have made some > other hash some other time.
But how could you have some assurance that that data relates to what their users thought of to be?
