From: Leon Vack <dev@lgcl.de>
To: Olivier Certner <ocert.dev@free.fr>
Cc: larsi@gnus.org, 45340@debbugs.gnu.org, bandali@gnu.org, dev@lgcl.de
Subject: bug#45340: erc-services.el: Auth-source support for passwords
Date: Fri, 15 Jan 2021 11:10:08 GMT [thread overview]
Message-ID: <87mtxalals.fsf@sol.hw.lgcl.de> (raw)
In-Reply-To: <4311421.VgBTkc7HA1@ravel>
Olivier Certner <ocert.dev@free.fr> writes:
> Hi,
>
Hello,
> Sorry to be late to the party, but what is exactly this bug (and the patch)
> about? I'm asking this because I've been using auth source for NickServ
> passwords for a while now, without any patch. And I just want to make sure
> that this is going to continue to work (of course, I don't mind possibly
> changing some configuration variables if required). I've skimmed through the
> bug report and the patch, and while I see no particular problem there, I
> wonder if some existing things have not been overlooked.
>
> I have `erc-prompt-for-password' set to nil (not `erc-prompt-for-nickserv-
> password'), and indeed I get prompted for a NickServ password. At this point,
> I just hit ENTER without entering anything, and my password from auth source
> is automatically picked up. So there seems to be an already existing mechanism
> for getting the password used for NickServ from auth source.
I was not aware of this, but I have done some debugging and the NickServ
authentication you use mostly likely does not go through erc-services,
but the core erc functionality to connect, which sends a PASS command
with a password from auth source. At least freenode accepts this as a way
to do NickServ authentication and the patch does not effect this
functionality at all. To check if that is indeed the case, maybe try
connecting without having the erc-services module loaded.
>
> Or is it a confusion on my part, and the introduced functionality is in fact
> different?
>
This patch introduces a different functionality as described above, as
erc-services, which only handles authentication with actual /nickserv
identify commands (not handled by the core connect functionality), did
not query auth source before this patch.
> Regards.
Regards,
Leon Vack
next prev parent reply other threads:[~2021-01-15 11:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 10:54 bug#45340: erc-services.el: Auth-source support for passwords Leon Vack
2020-12-21 4:46 ` Lars Ingebrigtsen
2020-12-21 5:44 ` Leon Vack
2020-12-29 0:12 ` Amin Bandali
2020-12-29 8:24 ` Leon Vack
2021-01-09 7:22 ` Leon Vack
2021-01-10 11:49 ` Lars Ingebrigtsen
2021-01-11 14:38 ` Leon Vack
2021-01-11 14:51 ` Lars Ingebrigtsen
2021-01-11 16:04 ` Leon Vack
2021-01-11 16:06 ` Lars Ingebrigtsen
2021-01-15 9:46 ` Olivier Certner
2021-01-15 11:10 ` Leon Vack [this message]
2021-01-15 12:41 ` Olivier Certner
2021-01-20 10:42 ` Leon Vack
2021-01-13 8:27 ` bug#45340: foo Richard Copley
2021-01-15 21:48 ` Basil L. Contovounesios
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=87mtxalals.fsf@sol.hw.lgcl.de \
--to=dev@lgcl.de \
--cc=45340@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=larsi@gnus.org \
--cc=ocert.dev@free.fr \
/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).