http://bugs.winehq.org/show_bug.cgi?id=17783
--- Comment #13 from Justin H Haynes justin@justinhaynes.com 2009-04-18 15:52:22 --- (In reply to comment #11)
(In reply to comment #7)
I'm fairly sure it's just a matter of installing the two certificates on http://www.verisign.com/support/verisign-intermediate-ca/extended-validation... into whatever wine-gecko is using as a certificate store. One of them is signed by an existing trusted Verisign root certificate, the other is signed by the former, and the Steam certificate is signed by the latter, completing the chain of trust.
I believe crypt32 handles that, which checks your native keychain store. See CRYPT_knownLocations in crypt32/rootstore.c
So I find:
static const char * const CRYPT_knownLocations[] = { "/etc/ssl/certs/ca-certificates.crt", "/etc/ssl/certs", "/etc/pki/tls/certs/ca-bundle.crt", "/usr/local/share/certs/", };
Would the certificates need to be present at compile time or runtime?