/!\ Beware sourceforge
#9
SHA1 isn't _broken_ broken, it has a known "theoretical weakness", and is as of now still secure in practice. Even MD5 works in practice unless someone with funding from a multinational megacorp or a nation-state is out to get you, which I doubt is the case with AC. I'm definitely not advocating MD5 though, but SHA1 is still fine.

No SHA1 collisions (even artificially produced) are known to exist, and it's widely enough used to be a safe common denominator (Microsoft's own file checker tool, for example, only does MD5 and SHA1 AFAIK), so a SHA1 checksum should probably be included at least for those users.
Thanks given by:


Messages In This Thread
/!\ Beware sourceforge - by damien - 11 Aug 15, 12:22PM
RE: /!\ Beware sourceforge - by ExodusS - 11 Aug 15, 02:41PM
RE: /!\ Beware sourceforge - by damien - 11 Aug 15, 02:55PM
RE: /!\ Beware sourceforge - by Mousikos - 11 Aug 15, 03:28PM
RE: /!\ Beware sourceforge - by damien - 11 Aug 15, 03:40PM
RE: /!\ Beware sourceforge - by Waffles - 11 Aug 15, 11:27PM
RE: /!\ Beware sourceforge - by damien - 12 Aug 15, 09:50AM
RE: /!\ Beware sourceforge - by Mousikos - 12 Aug 15, 03:37PM
RE: /!\ Beware sourceforge - by JMM - 13 Aug 15, 05:35AM
RE: /!\ Beware sourceforge - by damien - 19 Aug 15, 06:38PM
RE: /!\ Beware sourceforge - by Mousikos - 19 Aug 15, 08:22PM
RE: /!\ Beware sourceforge - by MorganKell - 20 Aug 15, 09:09AM
RE: /!\ Beware sourceforge - by JMM - 20 Aug 15, 09:49AM
RE: /!\ Beware sourceforge - by Brett - 22 Aug 15, 06:14AM