im.pidgin.pidgin: 3634d69c60fbdab75e20abe5dbe9a7840fe80804

markdoliner at markdoliner at
Fri Nov 16 03:04:02 EST 2007

Revision: 3634d69c60fbdab75e20abe5dbe9a7840fe80804
Ancestor: 79e477454f627b229f4455df01378b02fd13e05b
Author: markdoliner at
Date: 2007-11-16T07:49:55
Branch: im.pidgin.pidgin

Modified files:


Don't crash when connecting to  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?

-------------- next part --------------
--- libpurple/certificate.c	55984faf73878b5f8d069c9b0b99ac7e3b29603a
+++ libpurple/certificate.c	9c7bed14716966db0acbe177473e12ef66049480
@@ -1359,6 +1359,7 @@ x509_tls_cached_unknown_peer(PurpleCerti
 		/* Okay, we're done here */
+		return;
 	} /* if (signature chain not good) */
 	/* Next, attempt to verify the last certificate against a CA */

More information about the Commits mailing list