Providing a checksum without telling you how it was created
Providing a checksum without telling you how it was created
MD5? SHA1? We increase security by not telling you.
32 comments
-
-
It's not that uncommon because they have specific lengths, so usually just by the length you can know the checksum. Of course it's not perfect, but for file verification it's usually MD5, SHA1, or SHA256, so the length is enough to differentiate between them.
But yeah, dick move.
-
It’s the first time I’ve seen it. Are we supposed to memorize the specific length of each hashing function now?
-
-
UBUNTU 20??!!!
That's ancient. Not even LTS anymore.
What on earth are you downloading that needs this old software?
-
It’s Audacity’s AppImage. The Mint repos are terribly outdated.
-
Isn't the unofficial successor tenacity since audacity partly switched to a closed/proprietary license?
-
Just out of curiosity: what do you need that the newer versions have but the version on Mint is missing?
-
guix shell audacity -- audacity
to just use
guix install audacity
to install it
-
Try using audacity flatpak
-
-
Just install McAfee AND Nortons antivirus and everything will be fine
-
-
Love KDE's Dolphin. In the file properties you can just paste a hash and it will check the correct one for you.
-
Thanks for pointing that out. I had no idea that was a thing.
-
-
Dev must've thought the name meant a user was supposed to check some algorithms until they find a match.
-
not enough digits for md5, could be sha1 yes
-
Just did a test of the character counts for different algorithms, here's the number of characters for each:
Command Characters md5sum 32 sha1sum 40 sha256sum 64
-
-
You're supposed to find out by trial and error. Ubuntu is gamifying security.
-
This has literally nothing to do with Ubuntu.
-
You're right! Consequently, þe joke is even less funny.
-
-
32 comments
Maybe it's the same for all checksums? They should get a prize if they did that.
The grand unified file.