Re: Potential bug/inconsistency in auth-source netrc vs plstore backends

[Soham Gumaste <sohamg2@gmail.com>]

> Hmm, I would expect that a password is associated with an account
> identified by some user ID.  Is there any existing usage of this
> apply-to-all kind of password?
>

The auth-info manual does mention this towards the start, and mentions
that it is a bad idea cause you will get "pwned". SO its not really a
use-case, but the fact is that netrc backend will match an entry even
if it does not have one of the fields eg port from the query.

I think this discrepancy is because the netrc backend uses a custom
netrc parser, whereas the plstore backend simply uses `plstore-find`
[1], which requires every key to be present and match, unless the key
is specified as "t".

This makes my idea harder, as now I either need to store port numbers
in the oauth2 plstore file, or patch plstore or patch gnus, and my
goal is to make minimum viable changes, so its a bit complicated. I
initially thought editing the "returned keys" binding would fix
this,but that is clearly not the case.

Will report back once I have time to hack on this more. Thank you
everyone in this thread for the feedback.

[1]: https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/auth-source.el#n2115


-- 
Soham Gumaste
sohamg2@gmail.com