From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: emacs-devel@gnu.org
Subject: Re: GnuPG homedir and package.el?
Date: Sat, 18 Mar 2017 12:26:13 +0100 [thread overview]
Message-ID: <87lgs2esh6.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <87k27rejkw.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 14 Mar 2017 15:37:03 -0400")
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
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.
Signature verification seems personal to me.
> JL> Attached is a patch introducing a new user option to use the
> JL> default GnuPG home.
>
> JL> +(defcustom package-use-separate-gnupghome t
>
> Maybe this could also be a specific directory the user chooses, so it
> could be a choice of nil, t, or 'string.
You are right. I changed that to be a directory or nil.
Thanks
Jens
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Introduce-customizable-variable-package-gnupghome-di.patch --]
[-- Type: text/x-diff, Size: 3277 bytes --]
From 4c76844e067ccf029c57189058d161831ca25ac7 Mon Sep 17 00:00:00 2001
From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
Date: Sat, 18 Mar 2017 12:17:02 +0100
Subject: [PATCH] Introduce customizable variable package-gnupghome-dir
* lisp/emacs-lisp/package.el (package-import-keyring,
package--check-signature-content, package-check-signature):
Use new variable package-gnupghome-dir to control which GnuPG homedir
to use.
---
lisp/emacs-lisp/package.el | 28 +++++++++++++++++++---------
1 file changed, 19 insertions(+), 9 deletions(-)
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index 8d5fac9..a809e39 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -305,6 +305,16 @@ package-directory-list
(declare-function epg-find-configuration "epg-config"
(protocol &optional no-cache program-alist))
+(defcustom package-gnupghome-dir (expand-file-name "gnupg" package-user-dir)
+ "Directory containing GnuPG keyring or nil.
+This variable specifies the GnuPG home directory used by package.
+That directory is passed via the option \"--homedir\" to GnuPG.
+If nil, do not use the option \"--homedir\", but stick with GnuPG's
+default directory."
+ :type 'directory
+ :risky t
+ :version "26.0.50.2")
+
(defcustom package-check-signature
(if (and (require 'epg-config)
(epg-find-configuration 'OpenPGP))
@@ -1207,9 +1217,9 @@ package--check-signature-content
"Check signature CONTENT against STRING.
SIG-FILE is the name of the signature file, used when signaling
errors."
- (let* ((context (epg-make-context 'OpenPGP))
- (homedir (expand-file-name "gnupg" package-user-dir)))
- (setf (epg-context-home-directory context) homedir)
+ (let ((context (epg-make-context 'OpenPGP)))
+ (when package-gnupghome-dir
+ (setf (epg-context-home-directory context) package-gnupghome-dir))
(condition-case error
(epg-verify-string context content string)
(error (package--display-verify-error context sig-file)
@@ -1236,7 +1246,7 @@ package--check-signature
"Check signature of the current buffer.
Download the signature file from LOCATION by appending \".sig\"
to FILE.
-GnuPG keyring is located under \"gnupg\" in `package-user-dir'.
+GnuPG keyring location depends on `package-gnupghome-dir'.
STRING is the string to verify, it defaults to `buffer-string'.
If ASYNC is non-nil, the download of the signature file is
done asynchronously.
@@ -1476,11 +1486,11 @@ package-import-keyring
"Import keys from FILE."
(interactive "fFile: ")
(setq file (expand-file-name file))
- (let ((context (epg-make-context 'OpenPGP))
- (homedir (expand-file-name "gnupg" package-user-dir)))
- (with-file-modes 448
- (make-directory homedir t))
- (setf (epg-context-home-directory context) homedir)
+ (let ((context (epg-make-context 'OpenPGP)))
+ (when package-gnupghome-dir
+ (with-file-modes 448
+ (make-directory package-gnupghome-dir t))
+ (setf (epg-context-home-directory context) package-gnupghome-dir))
(message "Importing %s..." (file-name-nondirectory file))
(epg-import-keys-from-file context file)
(message "Importing %s...done" (file-name-nondirectory file))))
--
2.7.4
next prev parent reply other threads:[~2017-03-18 11:26 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 [this message]
2017-03-20 13:37 ` Ted Zlatanov
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=87lgs2esh6.fsf@informationelle-selbstbestimmung-im-internet.de \
--to=jens.lechtenboerger@fsfe.org \
--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).