View Issue Details

IDProjectCategoryView StatusLast Update
0005092unrealircdpublic2018-06-11 08:32
ReporterGTAXL Assigned Tosyzop  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status resolvedResolutionfixed 
Product Version4.0.17 
Fixed in Version4.0.18 
Summary0005092: Add option to require SASL auth to connect
DescriptionOn user registration the IRCd, add an option to either the listen block or allow block to require the user to be SASL auth'd in order to connect. A lot of people have been requesting this idea. It's similar to how freenode does it for certain cellular networks. I'd say it'd be a better fit for the allow block, as you can specify what IP networks HAVE to be SASL auth'd such as networks that users share an IP like a cellular network, etc. plus in allow block if you wanted to require SASL auth for all users you could do a wildcard allow block, which is standard.
TagsNo tags attached.
3rd party modules



2018-05-01 11:35

administrator   ~0020110

yes, I agree


2018-05-02 23:58

reporter   ~0020122

Hello, we're interested in the same feature. uses charybdis (ratbox fork) and currently requires irccloud users to register an account with nickserv with a regular client. Irccloud users then have to use sasl authentication to get on a server. We would like very much to do this-- as with GTAXL's comment though, we're whitelisting certain nicknames for Tor and such, and it would be ideal to confine those whitelisted nicks to a special server requiring SASL authentication [so that someone can't bypass the tor check by logging in as "jenny1234" if that were an exempted nickname.] Thank you!


2018-05-31 11:27

reporter   ~0020133

Hi, we're also interested in this feature.

We're looking to use this to require users of Tor to first register an account with NickServ over non-Tor before they can connect through our Tor hidden service.


2018-06-03 17:31

reporter   ~0020134

This feature is highly wanted. We are also very interested.


2018-06-11 08:32

administrator   ~0020139

Added in git / future 4.0.18. I'll release an RC shortly.

commit cd6d7a2bb7967092f303dfd7fe09cf8748c12d39
Author: Bram Matthys <>
Date: Mon Jun 11 08:22:29 2018 +0200

    Add allow::options::sasl (or require-sasl) to require SASL authentication
    as suggested in
    The allow block documentation has been updated, including an example at
    the end of the page -

I see it was also previously suggested in 0004231 and in a comment of 0003243

Issue History

Date Modified Username Field Change
2018-04-27 18:20 GTAXL New Issue
2018-05-01 11:35 syzop Status new => acknowledged
2018-05-01 11:35 syzop Note Added: 0020110
2018-05-02 23:58 razingeden Note Added: 0020122
2018-05-31 11:27 jesopo Note Added: 0020133
2018-06-03 17:31 HeXiLeD Note Added: 0020134
2018-06-11 08:32 syzop Assigned To => syzop
2018-06-11 08:32 syzop Status acknowledged => resolved
2018-06-11 08:32 syzop Resolution open => fixed
2018-06-11 08:32 syzop Fixed in Version => 4.0.18
2018-06-11 08:32 syzop Note Added: 0020139