aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorJens Lechtenboerger2017-04-11 12:27:37 +0300
committerEli Zaretskii2017-04-11 12:27:37 +0300
commit695eacc21ea08b7fa080a232eadae881b5295bef (patch)
tree175dfbbc0bb302b0d2554ade99b0b3cf07090119 /doc
parent291b76f91ea991c9fa8e57b55df1b68704931445 (diff)
downloademacs-695eacc21ea08b7fa080a232eadae881b5295bef.tar.gz
emacs-695eacc21ea08b7fa080a232eadae881b5295bef.zip
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. * doc/emacs/package.texi: Mention package-gnupghome-dir. * etc/NEWS: Mention package-gnupghome-dir.
Diffstat (limited to 'doc')
-rw-r--r--doc/emacs/package.texi15
1 files changed, 11 insertions, 4 deletions
diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi
index d6f88aaec3c..ecc955d3efe 100644
--- a/doc/emacs/package.texi
+++ b/doc/emacs/package.texi
@@ -193,15 +193,22 @@ and use only third parties that you think you can trust!
193can have in their packages by @dfn{signing} them. They generate a 193can have in their packages by @dfn{signing} them. They generate a
194private/public pair of cryptographic keys, and use the private key to 194private/public pair of cryptographic keys, and use the private key to
195create a @dfn{signature file} for each package. With the public key, you 195create a @dfn{signature file} for each package. With the public key, you
196can use the signature files to verify who created the package, and 196can use the signature files to verify the package creator and make sure
197that it has not been modified. A valid signature is not a cast-iron 197the package has not been tampered with. Signature verification uses
198@uref{https://www.gnupg.org/, the GnuPG package} via the EasyPG
199interface (@pxref{Top,, EasyPG, epa, Emacs EasyPG Assistant Manual}).
200A valid signature is not a cast-iron
198guarantee that a package is not malicious, so you should still 201guarantee that a package is not malicious, so you should still
199exercise caution. Package archives should provide instructions 202exercise caution. Package archives should provide instructions
200on how you can obtain their public key. One way is to download the 203on how you can obtain their public key. One way is to download the
201key from a server such as @url{http://pgp.mit.edu/}. 204key from a server such as @url{http://pgp.mit.edu/}.
202Use @kbd{M-x package-import-keyring} to import the key into Emacs. 205Use @kbd{M-x package-import-keyring} to import the key into Emacs.
203Emacs stores package keys in the @file{gnupg} subdirectory 206Emacs stores package keys in the directory specified by the variable
204of @code{package-user-dir}. 207@code{package-gnupghome-dir}, by default in the @file{gnupg}
208subdirectory of @code{package-user-dir}, which causes Emacs to invoke
209GnuPG with the option @samp{--homedir} when verifying signatures.
210If @code{package-gnupghome-dir} is @code{nil}, GnuPG's option
211@samp{--homedir} is omitted.
205The public key for the GNU package archive is distributed with Emacs, 212The public key for the GNU package archive is distributed with Emacs,
206in the @file{etc/package-keyring.gpg}. Emacs uses it automatically. 213in the @file{etc/package-keyring.gpg}. Emacs uses it automatically.
207 214