SASL support about teleirc HOT 13 CLOSED

I am not sure of the technicality, but SASL just works fine.

Freenode doesn't allow my bot to connect unless it is auth by SASL ( may be because my VPS' ip was blacklisted. )

So I had to use SASL and it worked smoothly.
This is how the config looks with SASL:

config.ircOptions = {
userName: 'nick',
nick: 'nick',
password: 'password',
sasl: true,
.
.
};

I guess this issue can be closed.

from teleirc.

I would also be interested in how this happens especially by using SASL which has option in the config file but nothing to tell how to actually use it.

Currently I am not using SASL, but instead have this in the config file:

config.ircPerformCmds = ['NICKSERV identify username password'];

This works as NICKSERV is server side command which checks that NickServ is the real NickServ and not random user nicked to it (possible in case of server misconfiguration and has happened on probably all networks including freenode) and then sends the message to NickServ and is thus safer than PRIVMSG NickServ :identify username password.

However as this is not SASL, the bot joins channels before identifying and only identifies after joining which can be a issue. Also if freenode decided to require SASL from DigitalOcean IP ranges again, at least my instance would go down.

SASL is a method to identifying to NickServ before even being visible to the network other than operators with snomask getting connection notices.

from teleirc.

Hi, yes SASL is undocumented and untested. It is simply a feature of node-irc, and the config parameters are passed directly to that module. According to this, it should be sufficient to set the sasl parameter to true, and also making sure a nick, userName and password is set. If this works we could document this feature.

from teleirc.

Where should the password be set?

from teleirc.

Looks like it should be set in the options object passed to node-irc, so in our case inside config.ircOptions = { ... }

from teleirc.

Did anyone get this working?

from teleirc.

It seems I never commented here that when I set the password like instructed on 3rd of April, it simply got stuck as it didn't send AUTHENTICATE or did something else wrong on the IRCd side.

It also didn't timeout which it should do as otherwise when SASL is enabled and services are down, it will just be in reconnect loop instead of at IRC relaying messages.

from teleirc.

PROTIP: config.ircPerformCmds = ['NICKSERV identify USERNAME PASSWORD', 'NICKSERV regain BOTNICK'];

• Identifies the bot to services (it would be nice if SASL did this, but AFAIK no one has gotten it to work).
• Disconnects the session usng BOTNICK and changes the bots nick to BOTNICK (this is nice especially if your users have scripts like WeeChats parse_relayed_msg so the bot doesn't most of time change its nick to something weird).

Should work with recent versions of Atheme IRC services and confirmed to work on freenode.

from teleirc.

Thanks @Rat-S, because you succeeded, I tried again and discovered from config file comment that I was missing : between password and the actual password, and I think it failed due to that.

The only difference to your config is that I didn't specify nick: 'nick' as it's specified elsewhere.

👍 for closing now, but this should possibly be documented somewhere outside of this issue tracker.

from teleirc.

So what is the situation with this?

from teleirc.

Works for me. Would be super cool if we could get SASL EXTERNAL/CertFP working, but SASL PLAIN works fine.

from teleirc.

I have been using SASL PLAIN with TeleIRC for a long time and I think that this issue would be just documenting the SASL support somewhere.

I propose https://github.com/FruitieX/teleirc/wiki as one possible place which also doesn't necressarily need commits or push access to the repository.

from teleirc.

I documented at https://github.com/FruitieX/teleirc/wiki/Identifying-to-NickServ so I am closing this. It's a wiki, so feel free to improve it if you see issues there :)

from teleirc.