unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Soham Gumaste <sohamg2@gmail.com>
To: Xiyue Deng <manphiz@gmail.com>
Cc: Michael Albinus <michael.albinus@gmx.de>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Potential bug/inconsistency in auth-source netrc vs plstore backends
Date: Sun, 10 Nov 2024 12:29:37 -0600	[thread overview]
Message-ID: <CAAr-Hh2pWbsvFADi2xuyjDdY4tCPFtvt4V77iGd==_+DYGnhaw@mail.gmail.com> (raw)
In-Reply-To: <87fro1s7ds.fsf@debian-hx90.lan>

>
> I think that's how auth-source is supposed to work.  People would need 2
> entries with different `:port's, one for imap(s), one for smtp, for both to
> work.  Or maybe there is a better way now?
>

Well, auth-source should also work if one has simply `password
<password>` in the netrc file, and that password would be used for
every port, every user etc. However, the plstore backed for
auth-sources currently requires that the keys host, user, password,
and port ALL are present in the entry for it to successfully match.

I wanted some insight into this discrepancy. My goal with the
oauth2.el changes is to have minimum viable integration with
auth-sources such that the existing functions using it work. It's
narrower in scope than your plugin, and perhaps when I have a final
patchset ready we can discuss the merits of each.

Thanks
-- 
Soham Gumaste
sohamg2@gmail.com



  reply	other threads:[~2024-11-10 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 20:34 Potential bug/inconsistency in auth-source netrc vs plstore backends Soham Gumaste
2024-11-07 20:43 ` Soham Gumaste
2024-11-07 21:34 ` Xiyue Deng
2024-11-08  2:28   ` Soham Gumaste
2024-11-08  8:40 ` Michael Albinus
2024-11-08 18:00   ` Soham Gumaste
2024-11-08 22:11     ` Xiyue Deng
2024-11-10 18:29       ` Soham Gumaste [this message]
2024-11-10 23:58         ` Xiyue Deng

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='CAAr-Hh2pWbsvFADi2xuyjDdY4tCPFtvt4V77iGd==_+DYGnhaw@mail.gmail.com' \
    --to=sohamg2@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=manphiz@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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).