In this case, our algorithm is not accurate. Actually it didn't find SSL_new for other reasons. So the above result can't support our conclusion.
But later we verified the code manually and found that jabberd2 didn't call SSL_CTX_set_verify(), so it must be that jabberd2 didn't verify the certificate. Sorry for the confusion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380230 Title: Potential Vulnerability for X509 Certificate Verification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jabberd2/+bug/1380230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs