I am following various tutorials about using Freenode through Tor. I have tried irssi + cap_sasl.pl, and also weechat, which has builtin SASL support.
The connection fails in following way on both clients (irssi & weechat):
freenode | irc: connecting to server p4fsi4ockecnea7l.onion/6667 via socks5 proxy 127.0.0.1/9050...
freenode | irc: connected to p4fsi4ockecnea7l.onion/6667 (127.0.0.1)
freenode -- | asimov.freenode.net (asimov.freenode.net): *** Looking up your hostname...
freenode -- | asimov.freenode.net (asimov.freenode.net): *** Checking Ident
freenode -- | asimov.freenode.net (asimov.freenode.net): *** No Ident response
freenode -- | asimov.freenode.net (asimov.freenode.net): *** Couldn't look up your hostname
freenode -- | irc: client capability, server supports: account-notify extended-join identify-msg multi-prefix sasl
freenode -- | irc: client capability, requesting: sasl
freenode -- | irc: client capability, enabled: sasl
freenode -- | SASL authentication successful
freenode -- | asimov.freenode.net (asimov.freenode.net): *** Notice -- You need to identify via SASL to use this server
freenode =!= | Closing Link: gateway/tor-sasl/account (SASL access only)
freenode | irc: disconnected from server
The same happens on Irssi: "SASL authentication successful", and then the Notice from server & SASL as disconnection reason.
When I changed password to incorrect one, "SASL authentication failed" occured, so the message about successful SASL authentication is apparently meaningful and correct.
So why Freenode disconnects me?