It seems it's quite common to create a certificate in MSFT Intune with an 
illegal URI format. in the SAN. My golang TLS server based on crypto/tls 
fails to complete handshake with a
Windows client that presents this broken certificate. However since only 
the SAN is impacted, it would be good if the handshake is allowed to 
complete and not fail it altogether.
The specific error returned by Conn.Read() is below. It's in the x509.go 
code that parses the certificate and runs into the misformatted URI

tls: failed to parse client certificate: x509: cannot parse URI 
\"AAD_Device_ID:97c4aaba-224d-4fe7-98ba-a996c016ba49\"

Any ideas on how I can work around this ?
Thanks
-gopal raman

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/golang-nuts/4125267a-a670-4930-9243-152b96319fa8n%40googlegroups.com.

Reply via email to