all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Frosku" <frosku@frosku.com>
To: "Bone Baboon" <bone.baboon@disroot.org>, <help-guix@gnu.org>
Subject: Re: Freenode sasl authentication error rcirc
Date: Thu, 15 Apr 2021 01:08:40 +0100	[thread overview]
Message-ID: <CANUZG7O77S5.WYAVA7LMJY3Q@klugetown> (raw)
In-Reply-To: <871rbcmmwu.fsf@disroot.org>

On Thu Apr 15, 2021 at 1:06 AM BST, Bone Baboon wrote:
> I am trying to connect to Freenode. This was working fine but now I am
> receiving this error message:
>
> ```
> *** Notice -- You need to authenticate via sasl to use this server
> !!! Closing link: <gateway-information>
> (SASL access only)
> !!! freenode: connection broken by remote peer (closed)
> ```
>
> The IRC client I am using is rcirc an Emacs IRC client. I have not
> changed my rcirc configuration that was working.
>
> I am able to sign into Freenode without any trouble using Freenode's web
> irc client.
>
> I have tried adding the `gnutls`, `gsasl` and `cyrus-sasl` packages to
> my system configuration and reconfiguring. These packages do not fix
> this problem.
>
> The Emacs version is `27.2`.

Are you using tor? Because only certain forms of SASL authentication are
supported on tor.

https://freenode.net/news/tor-online

>>= %frosku = { os => 'gnu+linux', editor => 'emacs', coffee => 1 } =<<


  reply	other threads:[~2021-04-15  0:14 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANUZG7O77S5.WYAVA7LMJY3Q@klugetown \
    --to=frosku@frosku.com \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.