comparison libpurple/certificate.c @ 27764:4a213a2b3d3d

cert: Nevermind, not going to change that string. Trying to cram both the fact the user has no db of root certificates *and* that the subject name doesn't match is too impractical. The error will rarely occur anyway.
author Paul Aurich <paul@darkrain42.org>
date Fri, 31 Jul 2009 06:50:34 +0000
parents f834ffa7490b
children c72d171565c4 a8b61c00ceda
comparison
equal deleted inserted replaced
27763:f834ffa7490b 27764:4a213a2b3d3d
1362 /* Had no CA pool, so couldn't verify the chain *and* 1362 /* Had no CA pool, so couldn't verify the chain *and*
1363 * the subject name isn't valid. 1363 * the subject name isn't valid.
1364 * I think this is bad enough to warrant a fatal error. It's 1364 * I think this is bad enough to warrant a fatal error. It's
1365 * not likely anyway... 1365 * not likely anyway...
1366 */ 1366 */
1367 /* FIXME: 2.6.1 */
1368 purple_notify_error(NULL, /* TODO: Probably wrong. */ 1367 purple_notify_error(NULL, /* TODO: Probably wrong. */
1369 _("SSL Certificate Error"), 1368 _("SSL Certificate Error"),
1370 _("Invalid certificate chain"), 1369 _("Invalid certificate chain"),
1371 _("You have no database of root certificates, so " 1370 _("You have no database of root certificates, so "
1372 "this certificate cannot be validated.")); 1371 "this certificate cannot be validated."));