Mercurial > pidgin.yaz
comparison libpurple/certificate.c @ 21553:5cd93ff08ecc
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?
| author | Mark Doliner <mark@kingant.net> |
|---|---|
| date | Fri, 16 Nov 2007 07:49:55 +0000 |
| parents | a20ef7180680 |
| children | 7109257d4612 |
comparison
equal
deleted
inserted
replaced
| 21552:9736ee1ca29e | 21553:5cd93ff08ecc |
|---|---|
| 1357 g_free(secondary); | 1357 g_free(secondary); |
| 1358 | 1358 |
| 1359 /* Okay, we're done here */ | 1359 /* Okay, we're done here */ |
| 1360 purple_certificate_verify_complete(vrq, | 1360 purple_certificate_verify_complete(vrq, |
| 1361 PURPLE_CERTIFICATE_INVALID); | 1361 PURPLE_CERTIFICATE_INVALID); |
| 1362 return; | |
| 1362 } /* if (signature chain not good) */ | 1363 } /* if (signature chain not good) */ |
| 1363 | 1364 |
| 1364 /* Next, attempt to verify the last certificate against a CA */ | 1365 /* Next, attempt to verify the last certificate against a CA */ |
| 1365 ca = purple_certificate_find_pool(x509_tls_cached.scheme_name, "ca"); | 1366 ca = purple_certificate_find_pool(x509_tls_cached.scheme_name, "ca"); |
| 1366 | 1367 |