From: Lorenzo Martinico <lorenzo@martinico.me>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50953@debbugs.gnu.org
Subject: bug#50953: auth-source-pass should not be limited to a local directory
Date: Mon, 04 Oct 2021 21:53:24 +0100 [thread overview]
Message-ID: <87tuhw5x6k.fsf@martinico.me> (raw)
In-Reply-To: <877devvll1.fsf@gnus.org>
The pass command is the command to invoke password-store, "the
UNIX
password manager" (passwordstore.org), which is what
auth-source-pass
purports to use.
On my system, this is an alias for a process that fetches
passwords from another host in a compatible way to password store.
The
vault host is not accessible through ssh, so I
can't just change the gpg file location as suggested.
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Lorenzo Martinico <lorenzo@martinico.me> writes:
>
>> Apologies if this is not the appropriate mailing list for this
>> message.
>> I would like to put in a bug report / feature request for
>> auth-source-pass to stop using the local file directory and
>> just rely on
>> the output of the pass command (or provide an option to do that
>> instead).
>
> What's the "pass" command?
>
> larsi@elva:~/src/emacs/trunk$ type pass
> bash: type: pass: not found
>
>> For context, I would like to be able to use the pass command
>> (or rather,
>> an alias) to fetch files from a different host on every
>> request, but
>> not store the gpg files on my local machine.
>
> Can't you just set the gpg file location to
> "/ssh:other-host:.authinfo.gpg"?
next prev parent reply other threads:[~2021-10-04 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 22:06 bug#50953: auth-source-pass should not be limited to a local directory Lorenzo Martinico
2021-10-02 9:10 ` Lars Ingebrigtsen
2021-10-04 20:53 ` Lorenzo Martinico [this message]
2021-10-05 7:08 ` Lars Ingebrigtsen
2021-10-05 8:01 ` Lorenzo Martinico
2021-10-05 8:07 ` Lars Ingebrigtsen
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=87tuhw5x6k.fsf@martinico.me \
--to=lorenzo@martinico.me \
--cc=50953@debbugs.gnu.org \
--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 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).