pidgin: 46bee021: The warning string for plaintext auth ov...

evands at pidgin.im evands at pidgin.im
Tue Apr 15 19:55:39 EDT 2008


-----------------------------------------------------------------
Revision: 46bee021fbbe0ea0cec1a72fe9fcdd885da13dfd
Ancestor: 18d75fa55ab4fa515205724091361fd8b79350f4
Author: evands at pidgin.im
Date: 2008-04-15T23:51:03
Branch: im.pidgin.pidgin
URL: http://d.pidgin.im/viewmtn/revision/info/46bee021fbbe0ea0cec1a72fe9fcdd885da13dfd

Modified files:
        libpurple/protocols/jabber/auth.c

ChangeLog: 

The warning string for plaintext auth over an unencrypted connection is found
in two places, but one of them is more informative, including the account
name, while the other just says 'this server'. Let's use the informative
message in both cases.

-------------- next part --------------
============================================================
--- libpurple/protocols/jabber/auth.c	30a16b10bc3edb17a6aacad8cd03dbadfd74192e
+++ libpurple/protocols/jabber/auth.c	b2095ab8bfd68a544933793bc20645ffe0033571
@@ -717,13 +717,16 @@ static void auth_old_cb(JabberStream *js
 		} else if(xmlnode_get_child(query, "password")) {
 			if(js->gsc == NULL && !purple_account_get_bool(js->gc->account,
 						"auth_plain_in_clear", FALSE)) {
+				char *msg = g_strdup_printf(_("%s requires plaintext authentication over an unencrypted connection.  Allow this and continue authentication?"),
+											js->gc->account->username);
 				purple_request_yes_no(js->gc, _("Plaintext Authentication"),
 						_("Plaintext Authentication"),
-						_("This server requires plaintext authentication over an unencrypted connection.  Allow this and continue authentication?"),
+						msg,
 						1,
 						purple_connection_get_account(js->gc), NULL, NULL,
 						purple_connection_get_account(js->gc), allow_plaintext_auth,
 						disallow_plaintext_auth);
+				g_free(msg);
 				return;
 			}
 			finish_plaintext_authentication(js);


More information about the Commits mailing list