SASL (3.2) REAUTH [$5] #515

New Issue

2026-10-05T04:26:41+02:00

adam commented

2026-10-05 04:26:41 +02:00

SASL REAUTH allows the user to identify using SASL if services were down during the initial connect.

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

cap-notify has been discussed earlier on multiple issues and is required for SASL REAUTH.
ZNC also requires it for enabling e.g account-notify, extended-join https://github.com/znc/znc/issues/316 and away-notify https://github.com/znc/znc/issues/315 if I understood correctly.

~~http://ircv3.net/specs/extensions/cap-notify-3.2.html~~

EDIT: cap-notify was implemented by #957.

--- There is a **[$5 open bounty](https://www.bountysource.com/issues/12139597-sasl-3-2-reauth?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

SASL REAUTH allows the user to identify using SASL if services were down during the initial connect. - http://ircv3.net/specs/extensions/sasl-3.2.html ~~cap-notify has been discussed earlier on multiple issues and is required for SASL REAUTH. ZNC also requires it for enabling e.g account-notify, extended-join https://github.com/znc/znc/issues/316 and away-notify https://github.com/znc/znc/issues/315 if I understood correctly.~~ - ~~http://ircv3.net/specs/extensions/cap-notify-3.2.html~~ EDIT: cap-notify was implemented by #957. ## <bountysource-plugin> --- There is a **[$5 open bounty](https://www.bountysource.com/issues/12139597-sasl-3-2-reauth?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam commented

2026-10-05 04:26:41 +02:00

SASL REAUTH allows the user to identify using SASL if services were down during the initial connect.

Currently this is only possible with the cert module.

> SASL REAUTH allows the user to identify using SASL if services were down during the initial connect. Currently this is only possible with [the cert module.](http://wiki.znc.in/Cert)

adam commented

2026-10-05 04:26:42 +02:00

I think the *sasl module also needs a new command, /msg *sasl authenticate [<username>] [<password>] and if username and password aren't specified, use the configured credentials.

I think the *sasl module also needs a new command, `/msg *sasl authenticate [<username>] [<password>]` and if username and password aren't specified, use the configured credentials.

adam commented

2026-10-05 04:26:43 +02:00

Preferably, it should also attempt REAUTH automatically when NickServ asks for a login.

Preferably, it should also attempt REAUTH automatically when NickServ asks for a login.

adam commented

2026-10-05 04:26:43 +02:00

SASL REAUTH has nothing to do with NickServ.

When SASL is unavailable, it's not visible in CAP LS and NAKed when requested. When SASL becomes available, cap-notify mentions it with CAP NEW :SASL and then clients can perform the reauthentication.

You can find the spec from http://ircv3.net/specs/extensions/sasl-3.2.html.

I am not fully sure on the cap commands, but you get how it works in theory anyway.

SASL REAUTH has nothing to do with NickServ. When SASL is unavailable, it's not visible in `CAP LS` and NAKed when requested. When SASL becomes available, cap-notify mentions it with `CAP NEW :SASL` and then clients can perform the reauthentication. You can find the spec from http://ircv3.net/specs/extensions/sasl-3.2.html. _I am not fully sure on the cap commands, but you get how it works in theory anyway._

adam referenced this issue

2026-10-05 04:56:22 +02:00

API for clients to get ZNC info #972

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#515