4 ms·
> How is a user supposed to know the difference between untrusted because of SHA-1 deprecation and untrusted because of a MITM? The whole reason SHA-1 is being
by jrochkind1 10y ago
> How is a user supposed to know the difference between untrusted because of SHA-1 deprecation and untrusted because of a MITM?
The whole reason SHA-1 is being deprecated is because it's judged no longer strong enough to protect against MITM.
So I'd say it's intentional and desirable to treat SHA-1 like MITM, rather than to try to get the user to distinguish. User's don't have the capacity to distinguish between, and shoudln't have to, any category of "someone may be viewing and/or altering the content in this connection." They are moving to judging SHA-1 such a category.
- makomk 10y agoExcept that SHA-1 is strong enough to protect against MITM and will be for the immediately foreseeable future. Well-financed attackers could probably achieve a collision but that doesn't get you very far these days.
- jrochkind1 10y agoThen you disagree with the browser vendors decision to gradually remove support/warn for SHA-1 entirely? They seem to disagree with you.
- user5994461 10y agoSHA1 is perfectly fine. Warning: The above sentence may not be right in 5-10 years so they are starting to shut it down now. I personally find the schedule rather aggressive. Stop issuing certs this year, block it next year. What's the average cert lifetime? 1-2-3 years? This is gonna give some warnings.
- spydum 10y agoSHA1 may not be defeated yet, but since it has been found weak, we would be foolish to continue using it. It does us little good to wait until it's actually broken. Especially since we have sha2 as a sufficient replacement.
- makomk 10y agoSHA-1 still isn't practical to exploit right now. Conditioning users to automatically click through SSL warnings, on the other hand, can be trivially exploited.