Patches item #1668289, was opened at 2007-02-25 10:52
Message generated for change (Settings changed) made by sxw
You can respond by visiting:

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Simon Wilkinson (sxw)
>Assigned to: Nathan Walp (faceprint)
Summary: Jabber Cyrus SASL code should have optional passwords

Initial Comment:
Some Cyrus SASL mechanisms, such as GSSAPI, can operate without passwords. 
However, just making passwords optional for the Jabber protocol breaks those 
mechanisms which _do_ require passwords.

This patch implements an on-demand password prompter. It switches the Jabber 
protocol to make passwords optional, and then adds code to prompt for passwords 
as they are required by the various mechanisms. There is a small change to the 
Gaim core to expose the password prompter function.

The code takes advantage of the fact that if a password callback isn't 
registered with Cyrus, it won't attempt to use any mechanisms that require 
passwords. So, if we don't have a stored password, we don't register that 
callback, and try to start a SASL session. If we don't have any mechanisms 
available, or all of the available mechanisms fail, we prompt the user for a 
password before trying again.


You can respond by visiting:

Take Surveys. Earn Cash. Influence the Future of IT
Join's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
Gaim-patches mailing list

Reply via email to