From efc8056fb62ccb7501efae146abb646914f69b1d Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Wed, 7 Nov 2018 13:48:27 +0000 Subject: [PATCH] fix a couple of broken links --- proposals/1711-x509-for-federation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/1711-x509-for-federation.md b/proposals/1711-x509-for-federation.md index 9c20eab9f..a31ae4820 100644 --- a/proposals/1711-x509-for-federation.md +++ b/proposals/1711-x509-for-federation.md @@ -114,13 +114,13 @@ TLS keys for the whole domain. ### Extensions HTTP-Based Public Key Pinning (HPKP) and -[https://www.certificate-transparency.org](Certificate transparency) are +[Certificate transparency](https://www.certificate-transparency.org) are both HTTP extensions which attempt to work around some of the deficiencies in the CA model, by making it more obvious if a CA has issued a certificate incorrectly. HPKP has not been particularly successful, and is -[deprecated]((https://developers.google.com/web/updates/2018/04/chrome-67-deps-rems#deprecate_http-based_public_key_pinning) +[deprecated](https://developers.google.com/web/updates/2018/04/chrome-67-deps-rems#deprecate_http-based_public_key_pinning) in Google Chrome as of April 2018. Certificate transparency, however, is seeing widespread adoption from Certificate Authories and HTTP clients.