3 ms·
The german BSI does not recommend SHA1 and NIST only recommends it for 128bit security applications. And knowing if your application is not vulnerable to prefix
by zaarn 6y ago
The german BSI does not recommend SHA1 and NIST only recommends it for 128bit security applications. And knowing if your application is not vulnerable to prefix attacks can be a bit of a challenge, depending on what you do. If you have to ask yourself what to use, you probably shouldn't be starting to use SHA1. If your application supports it, then you're good to go for "2020 - 2030 & beyond", otherwise I'd just go with SHA256/SHA3-256 or even SHA512/SHA3-512.
- upofadown 6y agoFrom the 2020 BSI report: >From a security-technical perspective, however, there is, according to present knowledge,no reason speaking against using it in constructions which do not require collision resistance...
- zaarn 6y agoJust because there is no reason against using something doesn't mean it's a good idea. They recommend SHA256 and upwards, they see no reason that SHA1 must be removed immediately from some corners of cryptography, those are no conflicting viewpoints. Just don't use SHA1 unless you absolutely are forced to do so, not when you make something new from scratch that can use SHA256.
- upofadown 6y agoFor all we know using SHA-1 where collisions are not an issue is a good idea. This sort of question has already came up for MD5 used where collisions were not an issue. Everyone spent a lot of time, money and compatibility moving away from MD5. We were told to move to SHA-1 which is now broken in the same way. It was pointless effort caused by pointless hysteria. Now we have pointless SHA-1 hysteria...
- zaarn 6y agoMaybe stop hardcoding cryptoalgo's so you have to spend a lot of money to migrate? This is why protocols like TLS support negotiations.