[Pidgin] #1112: SASL code doesn't always honour username

Pidgin trac at pidgin.im
Fri May 18 20:17:38 EDT 2007


#1112: SASL code doesn't always honour username
-----------------------------------------+----------------------------------
 Reporter:  sxw                          |       Type:  defect
   Status:  new                          |   Priority:  minor 
Component:  libpurple                    |    Version:  2.0   
 Keywords:  Jabber SASL GSSAPI Kerberos  |    Pending:  0     
-----------------------------------------+----------------------------------
 When using Kerberos with the Cyrus SASL code for authentication to a
 Jabber server, Pidgin won't honour the 'username' passed to it by the
 user. Instead, it will connect as the prinicpal in the user's Kerberos
 credentials cache. This can be confusing, for example in cases where a
 user has multiple JIDs on a server, that they want to access from the same
 (local) account, using GSSAPI for authentication.

 It should be stressed that this bug is likely to be rarely seen. It will
 only affect those users using GSSAPI (a small group), and connecting with
 GSSAPI to a jabber server as a username other than that in their GSSAPI
 credentials. Still, it should be fixed - I just need to think about how to
 do so - a patch should be forthcoming this weekend.

 Simon.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/1112>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list