diff options
| author | Mark Doliner <markdoliner@pidgin.im> | 2007-11-16 07:49:55 +0000 |
|---|---|---|
| committer | Mark Doliner <markdoliner@pidgin.im> | 2007-11-16 07:49:55 +0000 |
| commit | 163e2f259e5eef80bc4dcbd944544cbfe0183ab2 (patch) | |
| tree | 5bcd815cdfb30fc44525c34b0c453440f83a39c0 /libpurple/certificate.c | |
| parent | e8726dc09277ddc384138054d32803a5b4902781 (diff) | |
| download | pidgin-163e2f259e5eef80bc4dcbd944544cbfe0183ab2.tar.gz | |
Don't crash when connecting to jabber.freenet.de. Michael Weitzel sent
an email about this to the Pidgin devel mailing list on 21 October
2007. I would appreciate if someone familiar with the certificate code
could check this change.
Also, should we prompt the user if they want to continue trying to
connect in the case where the certificate chain is invalid?
Diffstat (limited to 'libpurple/certificate.c')
| -rw-r--r-- | libpurple/certificate.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/libpurple/certificate.c b/libpurple/certificate.c index f6c2436a43..eab1114012 100644 --- a/libpurple/certificate.c +++ b/libpurple/certificate.c @@ -1359,6 +1359,7 @@ x509_tls_cached_unknown_peer(PurpleCertificateVerificationRequest *vrq) /* Okay, we're done here */ purple_certificate_verify_complete(vrq, PURPLE_CERTIFICATE_INVALID); + return; } /* if (signature chain not good) */ /* Next, attempt to verify the last certificate against a CA */ |