From: Daiki Ueno <ueno@unixuser.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 9112-done@debbugs.gnu.org
Subject: bug#9112: 24.0.50; EasyPG - creating new gpg-encrypted files fails
Date: Tue, 02 Aug 2011 06:32:26 +0900 [thread overview]
Message-ID: <87tya095sl.fsf-ueno@unixuser.org> (raw)
In-Reply-To: <20022.49618.747295.789434@gargle.gargle.HOWL> (Roland Winkler's message of "Mon, 1 Aug 2011 10:10:10 -0500")
tags 9112 notabug
thanks
"Roland Winkler" <winkler@gnu.org> writes:
>> The default value of epa-file-select-keys has changed from nil to
>> 'silent in Emacs 24, which means symmetric encryption is now default.
>> You could set the variable to nil for the compatible behavior.
>
> I see. Just curious: what was the reason for this change? I browsed
> emacs-devel and bug-gnu-emacs (and etc/NEWS), but I could not find
> anything.
I found the bug which caused this change:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7487#49
> ...Well, it would be nice if either gpg or emacs could tell the user
> that the file the user wants to save is just about to go through
> symmetric encryption (and not any other encryption mechanism the
> user might hope for). Otherwise, any misunderstanding concerning the
> encryption mechanism could imply that a file is essentially lost
> after saving.
Right, but some people (Ted and Lars at least) feel the behavior too
verbose. Maybe pinentry could be improved to display what gpg will do.
Actually I sometimes use gnome-keyring-daemon's gpg-agent support, which
displays two passphrase entries for confirmation and that implies
symmetric encryption.
Regards,
--
Daiki Ueno
prev parent reply other threads:[~2011-08-01 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 2:53 bug#9112: 24.0.50; EasyPG - creating new gpg-encrypted files fails Roland Winkler
2011-08-01 2:28 ` Daiki Ueno
2011-08-01 15:10 ` Roland Winkler
2011-08-01 21:32 ` Daiki Ueno [this message]
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=87tya095sl.fsf-ueno@unixuser.org \
--to=ueno@unixuser.org \
--cc=9112-done@debbugs.gnu.org \
--cc=winkler@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 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).