[Bug 17783] steamcommunity.com certificate not recognised

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=17783





--- Comment #16 from Austin English <austinenglish at gmail.com>  2009-04-18 17:15:11 ---
(In reply to comment #13)
> (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-pro/index.html
> > > 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?
> 

Runtime.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.