Hi, just noticed this:
Percona-Server-5.5.30-rel30.1.tar.gz 2013-03-06 21.5 MB
Percona-Server-5.5.30-rel30.2.tar.gz 2013-05-14 21.5 MB
yaSSL Release notes, version 2.2.3 (04/23/2013) "This release of yaSSL updates the test certificates as they were expired."
BUT
$ grep Release Percona-Server-5.5.30-rel30.1/extra/yassl/README | head -1 yaSSL Release notes, version 2.2.2 (7/5/2012)
$ grep Release Percona-Server-5.5.30-rel30.2/extra/yassl/README | head -1 yaSSL Release notes, version 2.2.2 (7/5/2012)
Back to yassl/certs:
$ openssl x509 -noout -in client-cert.pem -dates notAfter=Mar 26 18:39:40 2013 GMT
$ openssl x509 -noout -in server-cert.pem -dates notAfter=Mar 26 18:52:17 2013 GMT
$ openssl x509 -noout -in dsa-cert.pem -dates notAfter=Mar 26 18:56:39 2013 GMT
So the Percona-Server-5.5.30-rel30.2 sources bundle a version of yassl with expired certificates, no idea on the effect of this anyway and if it can be related to this bug.
Hi,
just noticed this:
Percona- Server- 5.5.30- rel30.1. tar.gz 2013-03-06 21.5 MB
Percona- Server- 5.5.30- rel30.2. tar.gz 2013-05-14 21.5 MB
yaSSL Release notes, version 2.2.3 (04/23/2013)
"This release of yaSSL updates the test certificates as they were expired."
BUT
$ grep Release Percona- Server- 5.5.30- rel30.1/ extra/yassl/ README | head -1
yaSSL Release notes, version 2.2.2 (7/5/2012)
$ grep Release Percona- Server- 5.5.30- rel30.2/ extra/yassl/ README | head -1
yaSSL Release notes, version 2.2.2 (7/5/2012)
Back to yassl/certs:
$ openssl x509 -noout -in client-cert.pem -dates
notAfter=Mar 26 18:39:40 2013 GMT
$ openssl x509 -noout -in server-cert.pem -dates
notAfter=Mar 26 18:52:17 2013 GMT
$ openssl x509 -noout -in dsa-cert.pem -dates
notAfter=Mar 26 18:56:39 2013 GMT
So the Percona- Server- 5.5.30- rel30.2 sources bundle a version of yassl with expired certificates, no idea on the effect of this anyway and if it can be related to this bug.