Opened 6 years ago

Last modified 5 years ago

#4116 new Defect

SASL authentication always results in NickServ Password dialog

Reported by: anonymous Owned by:
Component: Colloquy (Mac) Version: 2.4 (Mac)
Severity: Normal Keywords: SASL, authentication, nickserv


So, Freenode (more specifically NickServ?) allows a different user name to be associated with an account than the intended /nick.

When you are doing this, using SASL for the connection will always result in Colloquy responding with a password dialog, regardless of whether authentication happens or not.

Steps to reproduce:

  1. Register account with NickServ? on Freenode
  2. create new nick, and assign that nick to your account through /msg NickServ? GROUP
  3. Set the new nick to be default for freenode
  4. Quit and restart colloquy, you will now be asked to enter a password, and store it in the keychain. Do so
  5. Quit and restart colloquy again. You will still be asked to enter a password and store it.

Note that even if you're asked for the password, NickServ? _will_ identify you, so the dialog is just an annoyance

Only remedy I've found is to turn off SASL.

Change History (2)

comment:1 Changed 6 years ago by Jo Rhett <jrhett@…>

I am seeing this exact problem. I see the dialog every time I close my laptop lid and open it again, or any time my screensaver kicks in. In short, I hit cancel on this dialog no less than 50 times a day MINIMUM.

As reporter said, the dialog is pointless because it always properly authenticates using the SASL information configured in my preferences. As SASL auth is required by Freenode these days, resolving this bug would be greatly appreciated.

comment:2 Changed 5 years ago by anonymous


Persistently annoying, to the point of considering switching IRC client.

Note: See TracTickets for help on using tickets.