On 06/10/16 12:38, Jakob Bohm wrote: > Which is why I have repeatedly suggested that maybe the rules should be > changed to promote/demote some of the historic SHA-1 root certs into > "SHA-1 forever" roots that can service older devices and browsers, even > for regular websites concerned about allowing visits from older devices > while transitioning their websites to HTTPS-only.
That has effectively happened; those roots have been removed from current root stores, but if you talk to the right CA you can still get a cert from one. > Ideally, there should also be a way for TLS servers (such as web > servers) to detect if the TLS client suffers from historic public key > limitations such as SHA-1 only, low maximum DH key size etc., thus > allowing the TLS server to use stronger certificates and FS keys for > new clients. Again, this exists - people use the cipher suite set, or support (or lack of it) for TLS or TLS 1.2. Gerv _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
