severity 660799 normal thanks
I have found that actually if I use the certficates from the MySQL, then it works. Obviously one cannot use those certficates in a production environment but that is now a separate issue requirin more investigation.
As regards the test suite by running the main.openssl_1 test with -record option the test was able to run. The attached patch shows that the only difference was the output from an SSL error message. So presumably that is a YaSSL/openssl issue.
Since this is now only a circumstanical build issue I will downgrade to normal.
-- Nicholas Bamber | http://www.periapt.co.uk/ PGP key 3BFFE73C from pgp.mit.edu
Author: Nicholas Bamber <nicho...@periapt.co.uk> Debian-Bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660799 Forwarded: no Last-Update: 2012-03-02 Subject: This test fails in the presence of libssl-dev and SSL functionality seems to fail without it. --- a/mysql-test/r/openssl_1.result +++ b/mysql-test/r/openssl_1.result @@ -44,9 +44,9 @@ drop user ssl_user1@localhost, ssl_user2@localhost, ssl_user3@localhost, ssl_user4@localhost, ssl_user5@localhost; drop table t1; -mysqltest: Could not open connection 'default': 2026 SSL connection error: ASN: bad other signature confirmation -mysqltest: Could not open connection 'default': 2026 SSL connection error: ASN: bad other signature confirmation -mysqltest: Could not open connection 'default': 2026 SSL connection error: ASN: bad other signature confirmation +mysqltest: Could not open connection 'default': 2026 SSL connection error: error:00000001:lib(0):func(0):reason(1) +mysqltest: Could not open connection 'default': 2026 SSL connection error: error:00000001:lib(0):func(0):reason(1) +mysqltest: Could not open connection 'default': 2026 SSL connection error: error:00000001:lib(0):func(0):reason(1) SSL error: Unable to get private key from '' mysqltest: Could not open connection 'default': 2026 SSL connection error: Unable to get private key SSL error: Unable to get certificate from ''
