SASL support

[Asara]

Attempting to connect to a freenode from a AS running in AWS leads to this error:

{"command":"ERROR","rawCommand":"ERROR","commandType":"normal","args":["Closing Link: ec2-34-192-170-23.compute-1.amazonaws.com (SASL access only)"]}

Edit: Should probably just rename this to a feature request asking for SASL support in reality. Please feel free to do so if that is the case! :)

[Mikaela]

SASL specifications:

• http://ircv3.net/specs/extensions/sasl-3.1.html
• http://ircv3.net/specs/extensions/sasl-3.2.html

• This is an optional extension and not so widely supported yet, but it features SASL REAUTH which allows identifying with SASL after you are already connected e.g. after netsplit when you were connected to splitted server without services and the split is over and services return. Integrate with NickServ #82 (comment)

I think the issue would be better named as SASL PLAIN support for now and possibly later have separate issue for SASL EXTERNAL (aka/or CertFP (#459)) and I recommend my recommendation on ignoring ECDSA-NIST256p-CHALLENGE from #82 (comment) because of znc/znc#746 (comment).

[henk717]

!storepass is currently not supported on the Rizon bridge.
Rizon lacks PASS support, this can be solved by implementing this feature request.
SASL PLAIN is supported alongside EXTERNAL on there IRC network.

[Half-Shot]

Worth pointing out tthe upstream library supports this! It just needs careful integration.

[Half-Shot]

SASL PLAIN is now supported.

[Asara]

Is it possible to re-open this issue? I would say that #689 still being an issue means that SASL support isn't really baked in yet.

[Mikaela]

@Half-Shot I would also request reopening this issue until users can actually use SASL to login. I think it would be more clear for majority of users for this to be open than pointing to #673.

[Half-Shot]

Right yes. This needs #673 and #689 to be completed in order to close it.

[thiras]

Still waiting for it to start the migration to the matrix. Is there any ETA?

[Mikaela]

I think this is required for most (if not even all) Oragono Ergo deployments due to its integrated bouncer and force-nick-equals-account.

[poVoq]

Any news on this? Also SASL for the Matrixbot seems to fail when the IRC network (like Ergo.chat based ones) only supports real SASL login and not the fallback via server password it seems.

Edit: actually Ergo does support this, not sure why it still fails.

Edit: I set the bridge to force SASL and the bot still fails to use the SASL account on my Ergo IRC network and rather switches to an unregistered alt-nick. Something about the way this bridge does SASL is not standard conformant it seems.

Edit: So... apparently it works for user accounts but not the bridge bot...