From 063ce0f2f774563ff2143bd8b974ce7f89caa365 Mon Sep 17 00:00:00 2001 From: Filippo Valsorda Date: Fri, 5 Jun 2020 12:48:26 -0400 Subject: [PATCH] doc/go1.15: add release notes for crypto/x509 Updates #37419 Change-Id: Iedfd4b238980675be115c7e6e0a327d7745b5bed Reviewed-on: https://go-review.googlesource.com/c/go/+/236737 Reviewed-by: Katie Hockman Reviewed-by: Dmitri Shuralyov --- doc/go1.15.html | 47 ++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 46 insertions(+), 1 deletion(-) diff --git a/doc/go1.15.html b/doc/go1.15.html index 7506a6aa49..10b245fd8f 100644 --- a/doc/go1.15.html +++ b/doc/go1.15.html @@ -425,8 +425,53 @@ TODO
crypto/x509
+

+ If either the name on the certificate or the name being verified (with + VerifyOptions.DNSName + or VerifyHostname) + are invalid, they will now be compared case-insensitively without further + processing (without honoring wildcards or stripping trailing dots). + Invalid names include those with any characters other than letters, + digits, hyphens and underscores, those with empty labels, and names on + certificates with trailing dots. +

+ +

+ The deprecated, legacy behavior of treating the CommonName + field as a hostname when no Subject Alternative Names are present is now + disabled by default. It can be temporarily re-enabled by adding the value + x509ignoreCN=0 to the GODEBUG environment + variable. If the CommonName is an invalid hostname, it's + always ignored. +

+ +

+ The new CreateRevocationList + function and RevocationList type + allow creating RFC 5280-compliant X.509 v2 Certificate Revocation Lists. +

+ +

+ CreateCertificate + now automatically generates the SubjectKeyId if the template + is a CA and doesn't explicitly specify one. +

+ +

+ CreateCertificate + now returns an error if the template specifies MaxPathLen but is not a CA. +

+

- TODO: https://golang.org/cl/205237: load roots from colon separated SSL_CERT_DIR in loadSystemRoots + On Unix systems other than macOS, the SSL_CERT_DIR + environment variable can now be a colon-separated list. +

+ +

+ On macOS, binaries are now always linked against + Security.framework to extract the system trust roots, + regardless of whether cgo is available. The resulting behavior should be + more consistent with the OS verifier.