http://bugs.winehq.org/show_bug.cgi?id=21096
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|wininet |-unknown
--- Comment #29 from Juan Lang juan_lang@yahoo.com 2010-09-28 15:07:11 CDT --- (In reply to comment #28)
Two questions: A) do you need more logs
Not really, as this only points to a configuration error (which would make this invalid.) Let's look at the diff: http://source.winehq.org/git/wine.git/?a=commitdiff;h=6217326a09dda8d029f808...
Here's the substantive change: + pSSL_CTX_set_verify(ctx, SSL_VERIFY_PEER, netconn_secure_verify); That is, a function is set to enable checking the certificate. Before, no checking was done. Here's the function that actually checks the certificate:
+static int netconn_secure_verify(int preverify_ok, X509_STORE_CTX *ctx) +{ + SSL *ssl; + WCHAR *server; + + ssl = pX509_STORE_CTX_get_ex_data(ctx, + pSSL_get_ex_data_X509_STORE_CTX_idx()); + server = pSSL_get_ex_data(ssl, hostname_idx); + FIXME("verify %s\n", debugstr_w(server)); + return preverify_ok; +}
Basically, the function just returns preverify_ok. This is set by OpenSSL, and there's nothing we can do in Wine to fix it: you have to fix your OpenSSL configuration first.
B) do you need a separate regression test for the 12055 error?
No.