3 ms·
It's one thing to keep SHA1 in old services, but why do they keep pushing SHA1 into new ones?
by higherpurpose 12y ago
It's one thing to keep SHA1 in old services, but why do they keep pushing SHA1 into new ones?
- annnnd 12y agoFrom what I understand, the keys stay the same - this is the whole point of this approach. So it's not a "new service". I agree that SHA1 should be deprecated ASAP though.
- jgrahamc 12y agoWhat use of SHA-1 are you talking about?
- rakoo 12y agoFrom the user POV, nothing is changed. The decision to deprecate SHA1 or not isn't specific to Keyless SSL (ie, Keyless SSL isn't a new product for the users) From the bank's point of view, where we can say that Keyless SSL is a new product, only 2 cipher suites are allowed: ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-RSA-AES256-GCM-SHA384 which, as you can see, don't include sha1.