That upstream bug looks likely to be the cause. I don't use client certificates. But regardless of the source of the error, shouldn't Ubuntu build its package in a way that works rather than one that doesn't? OpenSSL is already installed on the stock system (even openssh relies on libssl) - does YaSSL provide some compelling advantage? What rationale was there for building MySQL against an alternative library? I doubt that whoever made that decision reasoned it through; if they had, they would probably have tested the most common use case for SSL connections and made sure the two libraries could be interchanged.
I think the right solution here is to switch MySQL to build against OpenSSL rather than yassl, in the absence of an upstream recommendation or a solid rationale for making the opposite decision. -- mysql client package has broken SSL support https://bugs.launchpad.net/bugs/359309 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
