For a while now, 11 of the connector tests have failed when Wocky is built with OpenSSL. Specifically: Failure: /connector/multica-verification/tls/nohost/ok Failure: /connector/cert-verification/tls/crl/fail Failure: /connector/cert-verification/tls/expired/fail Failure: /connector/cert-verification/tls/inactive/fail Failure: /connector/cert-verification/tls/selfsigned/fail Failure: /connector/cert-verification/ssl/crl/fail Failure: /connector/cert-verification/ssl/expired/fail Failure: /connector/cert-verification/ssl/inactive/fail Failure: /connector/cert-verification/ssl/selfsigned/fail Failure: /connector/cert-nonverification/tls/crl/fail Failure: /connector/cert-nonverification/ssl/crl/fail The first fails as follows: /connector/multica-verification/tls/nohost/ok: Error: wocky-tls-cert-error.4: SSL Certificate for weasel-juice.org is insecure (unknown signer) The others, as of Wocky master, just segfault. With a patch to be attached, it's clearer that they fail because the connection attempt succeeds when it's expected to fail with a specific error.
Actually I'm a bad person and just pushed that patch without waiting for review because it's right and I'm impatient. http://cgit.freedesktop.org/wocky/commit/?id=5f5db5c78ee12adc08e36d3bede1b10615838715
I tried to bisect, but I couldn't find a revision at which these tests passed. I looked back a year or so: I'm pretty sure they have passed between now and then. ;) So I don't think it's caused by changes in wocky-openssl.c. :/
Fixed while tracking down bug #49805
*** This bug has been marked as a duplicate of bug 49085 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.