From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt
Date: Mon, 30 Sep 2013 20:40:08 -0400 [thread overview]
Message-ID: <jwvli2dq0y5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87wqlxx4ss.fsf@flea.lifelogs.com> (Ted Zlatanov's message of "Mon, 30 Sep 2013 19:34:11 -0400")
SM> AFAIK it's perfectly OK to popup a password prompt when needed and
SM> I don't know under what circumstance this would be a problem.
> Using symmetric (passphrase) encryption:
> open authinfo.gpg in a buffer -> prompt
> edit
> save -> prompt
> VCS commit -> 2 or 3 prompts
I don't see how that relates to your previous question, which was about
preventing the prompt from appearing at all, rather than about making
sure that previous passwords are recorded and reused in subsequent uses.
Stefan
next prev parent reply other threads:[~2013-10-01 0:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 9:22 bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt Ted Zlatanov
2013-09-29 15:07 ` Thierry Volpiatto
2013-09-29 17:48 ` Ted Zlatanov
2013-09-29 15:24 ` Daiki Ueno
2013-09-29 17:57 ` Ted Zlatanov
2013-10-02 7:23 ` Daiki Ueno
2013-10-02 10:34 ` Ted Zlatanov
2013-10-02 12:48 ` Daiki Ueno
2013-10-02 13:27 ` Andrey Kotlarski
2013-10-02 13:38 ` Ted Zlatanov
2013-10-03 1:52 ` Daiki Ueno
2013-10-03 13:59 ` Ted Zlatanov
2013-10-03 14:59 ` Stefan Monnier
2013-10-04 21:05 ` Ted Zlatanov
2013-10-05 16:21 ` Stefan Monnier
2013-10-07 18:15 ` Ted Zlatanov
2013-10-07 22:46 ` Stefan Monnier
2013-10-04 0:12 ` Daiki Ueno
2013-10-04 16:11 ` Ted Zlatanov
2013-09-30 18:53 ` Stefan Monnier
2013-09-30 19:24 ` Ted Zlatanov
2013-09-30 22:49 ` Stefan Monnier
2013-09-30 23:34 ` Ted Zlatanov
2013-10-01 0:40 ` Stefan Monnier [this message]
2013-10-01 1:13 ` Ted Zlatanov
2013-10-01 2:23 ` Stephen J. Turnbull
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=jwvli2dq0y5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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.