From: Daiki Ueno <ueno@gnu.org>
To: Teodor Zlatanov <tzz@lifelogs.com>
Cc: 15553-done@debbugs.gnu.org
Subject: bug#15553: 24.3.50; epg.el and GnuPG 2.x cause unavoidable pinentry prompts for symmetrically encrypted files
Date: Tue, 08 Oct 2013 08:54:17 +0900 [thread overview]
Message-ID: <87a9ikwsbi.fsf-ueno-ueno@gnu.org> (raw)
In-Reply-To: <87mwml0xib.fsf@flea.lifelogs.com> (Teodor Zlatanov's message of "Mon, 07 Oct 2013 14:03:08 -0400")
tags 15553 notabug
thanks
Teodor Zlatanov <tzz@lifelogs.com> writes:
> 1. Install GnuPG 2.x, don't run gpg-agent
> 2. Open file.gpg, X or curses pinentry dialog pops up
>
> The suggested workaround is to run gpg-agent.
So you can workaround, what's your problem?
> Problems:
>
> - on a headless server this can lock up Emacs
Not a problem if you use the workaround.
> - if the GPG agent is dead, locked up, or not running, there's no remedy
Ditto.
> - the X pinentry dialog is very non-specific ("Enter passphrase") so
> there's no way to know what passphrase is being requested and why if
> you don't have the specific instance in focus.
Unreleated to this bug, please open a new one.
> - there's no way to avoid the prompt in favor of an Emacs minibuffer query
As I said a number of times, that degrades security. If the insecurity
is okay for you, what's the reason you want to use GnuPG 2.x rather than
GnuPG 1.x?
next prev parent reply other threads:[~2013-10-07 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 18:03 bug#15553: 24.3.50; epg.el and GnuPG 2.x cause unavoidable pinentry prompts for symmetrically encrypted files Teodor Zlatanov
2013-10-07 23:54 ` Daiki Ueno [this message]
2013-10-08 1:01 ` Ted Zlatanov
2013-10-08 1:43 ` Daiki Ueno
2013-10-08 3:27 ` Stefan Monnier
2013-10-08 7:07 ` Daiki Ueno
2013-10-08 16:57 ` Stefan Monnier
2013-10-09 0:39 ` Daiki Ueno
2013-10-09 3:05 ` Stefan Monnier
2013-10-09 4:10 ` Daiki Ueno
2013-10-10 0:33 ` Stefan Monnier
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=87a9ikwsbi.fsf-ueno-ueno@gnu.org \
--to=ueno@gnu.org \
--cc=15553-done@debbugs.gnu.org \
--cc=tzz@lifelogs.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.