From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Freenode sasl authentication error rcirc
Date: Fri, 16 Apr 2021 03:26:26 +0200 [thread overview]
Message-ID: <8735vrc94t.fsf@nckx> (raw)
In-Reply-To: <87zgy0l2yq.fsf@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
Bone Baboon writes:
> I am not using Tor.
This bugged me, so I asked in #freenode.
> I have not changed my rcirc configuration that was working.
But Freenode probably changed theirs:
<jess> nckx: some IP ranges are sasl required
<jess> high risk ranges
<nckx> jess: Aha. That's probably it.
<nckx> It would explain the suddenly.
<jess> it's an unfortunate measure but sometimes necessary
<darsie> VPNs used for password guessing?
<jess> we did it to some domestic ranges fairly recently in
response to significant abuse
<jess> darsie: some VPNs require SASL to make it more work to
evade/abuse using them
<nckx> So my suggestions are: (1) move (2) change ISPs/use a
bouncer (3) just set up SASL
<nckx> Definitely not in that order.
<jess> nckx: does rcirc not support sasl?
<jess> sasl is very good
<nckx> That I don't know yet.
<nckx> SASL is sweet and tasty.
<jess> if it doesn't, aim me at someone to whom i can explain sasl
<nckx> I'll keep that in mind.
Unless you can obtain a new IP that isn't part of these ‘high-risk
ranges’, or connect through a bouncer elsewhere, you *need* to set
up SASL. How that's done differs per client.
I briefly looked for rcirc how-tos but found none. The manual[0]
doesn't mention SASL at all. I'm not going to spend time learning
about rcirc, but every modern IRC client should support SASL. If
it doesn't, find a better one, or take one of the alternative
actions above.
jess seems to be willing to explain SASL to the rcirc developers
if needed.
> I have tried adding the `gnutls`, `gsasl` and `cyrus-sasl`
> packages to
> my system configuration and reconfiguring. These packages do
> not fix
> this problem.
Simply installing some packages won't cut it. You need to
actually register your nickname and configure your client to log
you in using SASL.
Some very general information:
<https://freenode.net/kb/answer/sasl>
Kind regards,
T G-R
[0]:
https://www.gnu.org/software/emacs/manual/html_mono/rcirc.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-04-16 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 0:06 Freenode sasl authentication error rcirc Bone Baboon
2021-04-15 0:08 ` Frosku
2021-04-15 2:06 ` Bone Baboon
2021-04-15 0:17 ` Tobias Geerinckx-Rice
2021-04-15 2:02 ` Bone Baboon
2021-04-16 1:26 ` Tobias Geerinckx-Rice [this message]
2021-04-16 2:18 ` Frosku
2021-04-21 0:17 ` Bone Baboon
2021-04-23 18:37 ` Bone Baboon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735vrc94t.fsf@nckx \
--to=me@tobias.gr \
--cc=bone.baboon@disroot.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).