unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Bone Baboon <bone.baboon@disroot.org>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix@gnu.org
Subject: Re: Freenode sasl authentication error rcirc
Date: Fri, 23 Apr 2021 14:37:35 -0400	[thread overview]
Message-ID: <875z0c3l00.fsf@disroot.org> (raw)
In-Reply-To: <8735vkqyno.fsf@disroot.org>

I am now able to connect to Freenode using Circe with SASL
authentication.

I received help from wasamasa in #emacs-circe and staff in #freenode to
debug an issue with Circe's SASL authentication.  A fix was pushed to
the Circe repository.

This logging variable was helpful during Circe debugging:
`(setq irc-debug-log t)` 

Here is the contents of my Circe configuration that is working for me:

```
(setq circe-network-options
      '(("Freenode"
         :tls t
         :nick "bone-baboon"
         :user "bone-baboon"
         :realname "bone-baboon"
         :sasl-username "bone-baboon"
         :sasl-password "<password>")))
```

The sasl-username and sasl-password are the username and password used
when registering an account with Freenode.

Bone Baboon writes:

> Thank you
>
> Tobias Geerinckx-Rice writes:
>> 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.
>
>> 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.
>
> I have registered an account with Freenode.  I will try to setup an
> Emacs IRC client with SASL or CertFP for that account.
>
> Searching melpa.org and emacs-tw/awesome-emacs on GitHub for irc I find:
>
> - ERC (included with Emacs)
> -- on #erc I was told
> --- ERC does not currently support SASL but it is being worked on
> --- ERC will support CertFP when Emacs 28 is released
>
> - rcirc (included with Emacs)
> -- no matches when searching for SASL or CertFP in the rcirc info
>    document 
>
>> I briefly looked for rcirc how-tos but found none.  The manual[0]
>> doesn't mention SASL at all. 
>
> - Riece
> -- Riece's documentation does not mention of SASL or CertFP
>
> - Circe
> -- Circe's readme shows support for SASL and CertFP
>
> I asked on #freenode if CertFP would work as an alternative to SASL and was told that it would.
>
> I am going to try to get Circe connecting to Freenode using SASL or CertFP.
>
> What Emacs IRC client's are people able to successfully connect to Freenode with using SASL or CertFP?
>
> Are there other Emacs IRC clients that I should look into?



      reply	other threads:[~2021-04-23 18:41 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
2021-04-16  2:18       ` Frosku
2021-04-21  0:17       ` Bone Baboon
2021-04-23 18:37         ` Bone Baboon [this message]

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=875z0c3l00.fsf@disroot.org \
    --to=bone.baboon@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).