all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: 15559@debbugs.gnu.org
Subject: bug#15559: 24.3.50; epg.el: pinentry prompt is not specific
Date: Tue, 08 Oct 2013 13:27:49 -0400	[thread overview]
Message-ID: <87a9ijwu3u.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <87zjqky3pe.fsf@flea.lifelogs.com>

On Tue, 08 Oct 2013 13:01:48 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

>> 1. run Emacs, nothing else (no gpg-agent, no idea if that would make a difference)
>> 2. open file1.gpg
>> 3. prompt is "Enter Passphrase"

SM> I just tried it and it opened the file without prompting (so presumably
SM> the password is cached somewhere: I have no gpg-agent running, only an
SM> ssh-agent and a polkit-gnome-authentication-agent-1).

I'm not sure about your setup.  The dialog shows up for me on Gentoo.

In any case, the problem is that the pinentry dialog is not showing the
filename or anything else to identify which passphrase is requested.  I
can't tell how to change that with GnuPG command-line options, although
I could conceivably write my own pinentry program and use that with some
environment variables to set the message appropriately.  So I don't
think epg.el can fix this issue from the Emacs side.

Ted






  reply	other threads:[~2013-10-08 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  1:02 bug#15559: 24.3.50; epg.el: pinentry prompt is not specific Teodor Zlatanov
2013-10-08  3:17 ` Stefan Monnier
2013-10-08 10:39   ` Ted Zlatanov
2013-10-08 17:01     ` Stefan Monnier
2013-10-08 17:27       ` Ted Zlatanov [this message]
2019-08-30 11:05         ` Lars Ingebrigtsen
2019-08-30 12:23           ` Eli Zaretskii
2019-09-29  7:25             ` Lars Ingebrigtsen
2019-08-30 11:06         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a9ijwu3u.fsf@flea.lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=15559@debbugs.gnu.org \
    --cc=bug-gnu-emacs@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.