bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#15552: 24.3.50; epa-file-cache-passphrase-for-symmetric-encryption n


From: Ted Zlatanov
Subject: bug#15552: 24.3.50; epa-file-cache-passphrase-for-symmetric-encryption not respected with GnuPG 2.x
Date: Mon, 07 Oct 2013 20:46:34 -0400
User-agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux)

On Tue, 08 Oct 2013 08:41:40 +0900 Daiki Ueno <address@hidden> wrote: 

DU> tags 15552 notabug
DU> thanks

DU> Teodor Zlatanov <address@hidden> writes:

>> 1. On the local system, install GnuPG 2.x and don't run the gpg-agent
>> 2. Set epa-file-cache-passphrase-for-symmetric-encryption to t
>> 3. Open file.gpg: password dialog pops up
>> 4. close file.gpg
>> 5. Open file.gpg: password dialog pops up again
>> 
>> Step (5) should not prompt.  It works properly with GnuPG 1.x.

DU> That's intended behavior.  It is documented and I stated a number of
DU> times the reason and why I chose such a lengthy name of the variable and
DU> the default is nil:

DU> 1. Emacs heap is not so secure
DU> 2. Using Emacs for password input degrades the security

(please note I opened this at Stefan's request; I knew you wouldn't be
interested in resolving it)

I appreciate your concern for security, but the behavior is broken from
a user's perspective and you make no effort to help at the time the
issue occurs.  You could, for instance, check the GnuPG version and be
helpful.

At least fix the docstring and maybe emit a message to be helpful about
it.  There's no mention that it breaks with GnuPG 2.x:

epa-file-cache-passphrase-for-symmetric-encryption is a variable defined in 
`epa-file.el'.
Its value is t
Original value was nil

Documentation:
If non-nil, cache passphrase for symmetric encryption.

For security reasons, this option is turned off by default and
not recommended to use.  Instead, consider using public-key
encryption with gpg-agent which does the same job in a safer
way.

DU> You never hear or remember.

Right, thanks again.

Ted





reply via email to

[Prev in Thread] Current Thread [Next in Thread]