Since it's dead, what does /g/ use?
>>51812672
md5++
Quadruple XOR hashing.
>>51812672
md6
rot26 for double the security and triple des with identical keys for triple the security of the double security (60x)
>>51812672
>since it's dead
are you actually only now switching from md5?
>>51812672
SHA1024
>>51812672
Is it still good for file checksum?
Why's it dead?
>>51812672
>>51812921
It's perfectly usable for checking whether files are the same. Accidental collisions aren't going to happen.
166578557E535 caesar cipher
>>51812835
>implying
>>51812672
SHA512
>>51812672
plain text
>>51812672
whirpool
>>51812672
Gentoo.
Dead for what? I use it for my duplicate file checking script. Yeah it's dead for security, that's not the only thing you use hashing functions for.
>>51812672
Whirlpool
What's wrong with MD5 checksums?
>>51813279
I see you are contributing greatly to the thread and your opinion totally differs from anything I've ever seen in this website. Congratulations and thank you for being such a nice person in this particular thread!
>>51812781
>>51812781
>>51812781
>>51812781
https://github.com/Rabrennie/anything.js/blob/a52176da69f7e403547730b24a5569aec8b36bde/src/rot26.js
this
>>51813867
everything?
>A 2013 attack by Xie Tao, Fanbao Liu, and Dengguo Feng breaks MD5 collision resistance in 218 time.
SHA256
>>51813907
md2
>>51812954
>aren't going to happen.
Aren't going or are unlikely to happen?
Whirlpool, Skein, or GOST for insignificant stuff
Not a single person reading this(md5) will be affected by this.
Fuck off retards.
Security is "nice", you idiots overreact.
>>51812921
>>51812954
Yes, in general it will be fine.
Someone could possibly corrupt your backups that *intentionally* with a decent amount of effort, but unintentional collisions on an existing file with size and md5 on record almost can't happen.
