*** Original post on bio 719 at 2011-03-03 15:48:00 UTC *** There's a variety of authentication types for IRC, libpurple seems the only handle PASS (as far as I can tell). We can (and should) implement: Pass (Already supported!) Auth [1] SASL PLAIN (This uses base64 encoded plain password) [2] SASL BLOWFISH [3] NickServ [4] Selection would be by a drop down list in the advanced options defaulting to Pass (which some servers, i.e. Mozilla, automatically pass to the NickServ). [1] I haven't found any info on this, but it's possible it's in one of the specs I haven't full read yet. [2] For SASL authentication see: http://hg.atheme.org/charybdis/charybdis/raw-file/tip/doc/sasl.txt http://tools.ietf.org/html/rfc4422 http://tools.ietf.org/html/rfc4616 Note that this requires IRC Capabilities to be implemented. [3] There seems to be very little documentation on this (what a surprise). See http://freenode.net/sasl/README.txt for some information. I have a feeling I'll be reading source code to understand this one. DH-BLOWFISH algorithm and adds a +Z flag? This might be related/useful: https://tools.ietf.org/html/draft-burdis-cat-srp-sasl-08 [4] Ideally we should support the basic NickServ mechanism and even register the nick if someone logs in with an unregistered nick. I'm not sure how many different "types" of NickServs are out there, but it might also be necessary to allow users to type a custom name for the NickServ, please see bug 953609 (bio 162) for this.

*** Original post on bio 719 at 2012-02-27 15:38:00 UTC *** Moving IRC bugs to new IRC component.

*** Original post on bio 719 at 2013-01-08 00:57:24 UTC *** The only thing left in this bug is to support DH-BLOWFISH. This requires the Blowfish code that wnayes wrote for bug 954928 (bio 1495).

I'm going to close this. I don't know of any networks that implement blowfish SASL. Any other auth techniques we can file individual bugs for.