Back in 2010, there was some discussion on this list of adding code to load certificates from the system cert store on Windows by default, since the default verification paths typically don't point to anything (this was ticket #2158, which was ultimately rejected). I have some interest in picking up where this was left off, but I'm a little out of my depth and have some questions.
Last time around, the sticking point was certificate purposes: we don't want to add a certificate that's only trusted for client authentication as trusted for server authentication. I still need to figure out how to extract purposes from the windows certs, but I'm also having a hard time seeing how you'd set x509 purposes in openssl. Where should I be looking? -Matt Stickney -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev