From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: GnuPG homedir and package.el?
Date: Mon, 20 Mar 2017 09:37:06 -0400 [thread overview]
Message-ID: <87k27k9iil.fsf@lifelogs.com> (raw)
In-Reply-To: 87lgs2esh6.fsf@informationelle-selbstbestimmung-im-internet.de
On Sat, 18 Mar 2017 12:26:13 +0100 Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> wrote:
JL> On 2017-03-14, at 15:37, Ted Zlatanov wrote:
>> On Sat, 04 Mar 2017 17:41:54 +0100 Jens Lechtenboerger
>> <jens.lechtenboerger@fsfe.org> wrote:
>>
JL> is there a reason that package.el sets up its own GnuPG homedir (in
JL> package-import-keyring and package--check-signature-content)?
>>
>> Isolation? That way package management, where typically the user's
>> personal setup doesn't matter, doesn't overlap with personal GnuPG usage.
JL> Signature verification seems personal to me.
The isolation serves a purpose. I think the default behavior is better
for ease of use out of the box: it's less likely to break if a user
tinkers with their personal GnuPG setup.
The defcustom you introduced is the missing piece for more
advanced users, so I think that resolves the issue for everyone. I hope
you agree.
Ted
next prev parent reply other threads:[~2017-03-20 13:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 16:41 GnuPG homedir and package.el? Jens Lechtenboerger
2017-03-14 19:37 ` Ted Zlatanov
2017-03-18 11:26 ` Jens Lechtenboerger
2017-03-20 13:37 ` Ted Zlatanov [this message]
2017-03-20 17:43 ` Jens Lechtenboerger
2017-03-26 7:41 ` Jens Lechtenboerger
2017-04-01 14:01 ` Jens Lechtenboerger
2017-04-01 14:22 ` Eli Zaretskii
2017-04-01 15:01 ` Jens Lechtenboerger
2017-04-01 15:18 ` Eli Zaretskii
2017-04-01 16:08 ` Jens Lechtenboerger
2017-04-01 17:19 ` Eli Zaretskii
2017-04-04 15:04 ` Ted Zlatanov
2017-04-05 10:21 ` Jens Lechtenboerger
2017-04-05 13:31 ` Ted Zlatanov
2017-04-05 14:49 ` Jens Lechtenboerger
2017-04-11 9:30 ` Eli Zaretskii
2017-04-11 12:43 ` Jens Lechtenboerger
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=87k27k9iil.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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 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).