rfc:distrust-sha1-certificates
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision |
rfc:distrust-sha1-certificates [2017/05/29 10:56] – fix typo kelunik | rfc:distrust-sha1-certificates [2017/09/22 13:28] (current) – external edit 127.0.0.1 |
---|
===== RFC Impact ===== | ===== RFC Impact ===== |
| |
Browsers start on 2017-01-01 with no longer accepting SHA-1 certificates, too. Impact is expected to be rather low. People in need of SHA-1 certificates, e.g. for private CAs, can set the mentioned context option to ''80'' to get the previous behavior (except for MD5 not being accepted), but are strongly discouraged to do so. It is explicitly not possible to set this value lower than 80. There's no option to enable MD5. | Browsers started on 2017-01-01 with no longer accepting SHA-1 certificates. The impact is expected to be rather low. People in need of SHA-1 certificates, e.g. for private CAs, can set the mentioned context option to ''80'' to get the previous behavior (except for MD5 not being accepted), but are strongly discouraged to do so. It is explicitly not possible to set this value lower than 80. There's no option to enable MD5. |
| |
===== Future Scope ===== | ===== Future Scope ===== |
rfc/distrust-sha1-certificates.1496055373.txt.gz · Last modified: 2017/09/22 13:28 (external edit)