From: Tassilo Horn <tsdh@gnu.org>
To: emacs-devel@gnu.org
Cc: Alex McGrath <amk@amk.ie>, Philip Kaludercic <philipk@posteo.net>
Subject: About SASL authentication in rcirc
Date: Mon, 28 Jun 2021 12:36:34 +0200 [thread overview]
Message-ID: <87h7hijlmz.fsf@gnu.org> (raw)
Hi Alex,
thanks for bringing SASL authentication to rcirc. I'm using the
rcirc-update branch of Philip for my IRC needs where Philip has
cherry-picked your commit implementing SASL authentication for rcirc.
So obviously I wanted to try that out and changed my
--8<---------------cut here---------------start------------->8---
(setq rcirc-authinfo
`(("libera" nickserv "tsdh" ,th/nickserv-password-liberachat)))
--8<---------------cut here---------------end--------------->8---
to
--8<---------------cut here---------------start------------->8---
(setq rcirc-authinfo
`(("libera" sasl "tsdh" ,th/nickserv-password-liberachat)))
--8<---------------cut here---------------end--------------->8---
and restarted my rcirc session after rebuilding emacs.
After that, the *irc.libera.chat* buffer contained a message that tsdh
is a registered nick but not the message afterwards that I'm
successfully registered now (as it is the case with nickserv
authentication). And when querying NickServ, it told me that I'm not
logged it.
If I understand SASL/IRC correctly, it should have logged in immediately
on connecting, right?
So apparently, it seems that it didn't work when I've tried. I'd be
happy to debug where it fails if you give me some pointers what to look
for.
Bye,
Tassilo
next reply other threads:[~2021-06-28 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 10:36 Tassilo Horn [this message]
2021-06-28 12:46 ` About SASL authentication in rcirc amk
2021-06-28 19:35 ` Tassilo Horn
2021-06-28 19:58 ` Tassilo Horn
2021-06-28 20:12 ` Alex McGrath
2021-06-29 4:58 ` Tassilo Horn
2021-06-29 8:04 ` Philip Kaludercic
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7hijlmz.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=amk@amk.ie \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).