From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Robert Pluim <rpluim@gmail.com>
Cc: "Bartosz Kaczyński" <bk@asterio.cloud>
Subject: bug#58807: 28.1; Authentication in Gnus using password-store backend of auth-source
Date: Thu, 27 Oct 2022 20:55:25 +0300 [thread overview]
Message-ID: <m2h6zpup6a.fsf@fastmail.fm> (raw)
In-Reply-To: <874jvptems.fsf@gmail.com> (Robert Pluim's message of "Thu, 27 Oct 2022 18:28:27 +0200")
On 27/10/2022 18:28 +0200, Robert Pluim wrote:
>>>>>> On Thu, 27 Oct 2022 17:04:18 +0300, Filipp Gunbin <fgunbin@fastmail.fm> said:
> Filipp> (defun auth-source-pass-entries ()
> Filipp> "Return a list of all password store entries."
> Filipp> (let ((store-dir (expand-file-name auth-source-pass-filename)))
> Filipp> (mapcar
> Filipp> (lambda (file) (file-name-sans-extension (file-relative-name file store-dir)))
> Filipp> (directory-files-recursively store-dir "\\.gpg\\'"))))
>
> So `auth-source-pass-filename' is actually a *directory*. <sigh>
> Perhaps we need an obsoletion and and alias.
>
> Filipp> I tested using setup similar to yours, but with gpg files -- it worked.
>
> I saw nothing in Bartoszʼ original bugreport indicating that the files
> were not gpg encrypted, nor that they were.
I thought that these were files/dirs:
> Password Store
> ├── 127.0.0.1
[..]
But now I see that it's the output of "pass" (never used "pass" or
auth-source-pass before).
So probably the files are good, and it was really
auth-source-forget-all-cached that helped (auth-source-pass-enable does
nothing more than modifying auth-sources and calling it).
Filipp
next prev parent reply other threads:[~2022-10-27 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 19:30 bug#58807: 28.1; Authentication in Gnus using password-store backend of auth-source bk
2022-10-27 9:08 ` Robert Pluim
2022-10-27 9:15 ` Bartosz Kaczyński
2022-10-27 9:45 ` Robert Pluim
2022-10-27 13:19 ` Eli Zaretskii
2022-10-27 14:04 ` Filipp Gunbin
2022-10-27 16:28 ` Robert Pluim
2022-10-27 17:55 ` Filipp Gunbin [this message]
2022-10-28 7:38 ` Robert Pluim
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=m2h6zpup6a.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=bk@asterio.cloud \
--cc=rpluim@gmail.com \
/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.