@stephen-fox what's your use-case?

@icholy, I am working on a library that is utilized by a TLS server checking tool. One of the data points I would like to examine is whether a certificate provided by a TLS server is already in the CertPool containing the trusted CAs.

/cc @FiloSottile

You can do a map lookup of RawSubject against CertPool.Subjects(). Does that solve your use case?

Thank you for the suggestion. I initially thought the same thing. However, that only provides the subject field of each certificate in the CertPool.

In addition to the map lookup by subject, the CertPool.contains() method appears to use the Certificate.Equals() method to check certificate equality, which is a lot safer than only examining the subject. Leveraging the existing code would be less error prone, and more efficient than anything I could write outside of the x509 library.

For your purposes (checking if the server sent a root) the Subject should be enough: the only case I can think of in which a server would want to send a certificate with a Subject matching a trusted root is if it's a compatibility cross-cert, and you can simply check for that by verifying it's not self-signed.

Exposing contains would force us to retain full representations of the roots in memory, while we have pending CLs that lazy load them for performance, relying on the limited API, and we might not even have the full certificate for the system pool on some platforms (like Windows).

Interesting. You will have to forgive my naïve understanding of the x509 library - for my use case, there are two paths to initializing a CertPool:

• Creating an empty CertPool and then loading a PEM file / directory full of PEM files using the AppendCertsFromPEM() method
• Calling x509.SystemCertPool() (which does not appear to support Windows)

If I am understanding you correctly, the CertPool may not contain a full representation of a certificate depending how the CertPool was initialized?

My concern with using the Subjects() method is that a certificate provided by a TLS server may have the same subject as one in the pool, but might be a completely different certificate. My use case is a bit different than a standard TLS client in that my library can connect to TLS servers with validation disabled (tls.Config.InsecureSkipVerify = true). The purpose of this is falling back to collect certificates offered by the server for examination in the case of TLS validation / handshake failure. I wonder what would happen if a certificate in the CertPool expired, and the remote copy was replaced with a new certificate containing the same subject?

A few questions too - what do you mean by "CLs"? Also, when you say "relying on a limited API", are you referring to the CA trust store APIs offered by operating systems? I have been following your trials and tribulations with macOS, so that is my first guess :)

Thank you for bearing with me.

Subjects has been deprecated anyway, so not worth considering that. The depracation documentation seems to be lacking a good explanation of the reason, and nothing has been provided to replace it 🤦 All the tickets that were discussing these have since been 'FrozenDueToAge'.

Looks to me like this fundamental gap that's been opened up in the API has caused people to have to fork x509 all over the place 🙄 And now it looks like I might have to also 😭

FTR, my use case is simply to be able to count or iterate the certificates in a pool that has been created and passed to my function, so I can log a debug line.