From: Olivier Certner <ocert.dev@free.fr>
To: dev@lgcl.de, 45340@debbugs.gnu.org
Cc: larsi@gnus.org, bandali@gnu.org
Subject: bug#45340: erc-services.el: Auth-source support for passwords
Date: Fri, 15 Jan 2021 13:41:23 +0100 [thread overview]
Message-ID: <1936038.bl7DLxgNLY@ravel> (raw)
In-Reply-To: <87mtxalals.fsf@sol.hw.lgcl.de>
Hi Leon,
> 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.
Yes, seems to me that you are right, after activating IRC protocol debug
(`erc-toggle-debug-irc-protocol'), reconnecting to Freenode and looking at the
logs.
> 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.
Fine, I thought this may have been already implemented somehow because of
Freenode's special behavior.
Thanks for looking at this, and for this patch!
After reviewing the code more in details, I think it is great that `erc-
nickserv-get-password' first tries to find a password in `erc-nickserv-
passwords' before proceeding with auth source. `erc-nickserv-passwords' is the
easiest to customize, and I suspect it is mostly used for interactive override
or common presets in the init file.
I also have some further suggestion, beyond this enhancement. I think it would
be even more useful that `erc-prompt-for-nickserv-password' is not required to
be nil for auth source (or `erc-nickserv-passwords', for that purpose) to be
used, but rather that, if search in `erc-nickserv-passwords' and auth source
(if enabled) fails, then prompting should be used as a last resort (if
enabled). I think this would cover all the use cases I can think of (with
proper settings of `erc-prompt-for-nickserv-password' and `erc-use-auth-
source-for-nickserv-password'). If more customizations are required, or just
for the sake of 'simplicity' (YMMV), than maybe replacing these booleans with
a single list indicating the means to get the password and their order could
be nice.
What do people think?
Regards.
--
Olivier Certner
next prev parent reply other threads:[~2021-01-15 12:41 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
2021-01-15 12:41 ` Olivier Certner [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1936038.bl7DLxgNLY@ravel \
--to=ocert.dev@free.fr \
--cc=45340@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=dev@lgcl.de \
--cc=larsi@gnus.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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.