[svn] GnuPG - r5435 - trunk/doc
svn author wk
cvs at cvs.gnupg.org
Tue Oct 5 15:56:26 CEST 2010
Author: wk
Date: 2010-10-05 15:56:25 +0200 (Tue, 05 Oct 2010)
New Revision: 5435
Added:
trunk/doc/FAQ
Modified:
trunk/doc/ChangeLog
trunk/doc/Makefile.am
trunk/doc/faq.org
Log:
Add a static FAQ.
Add rules to build and upload the faqs.
Modified: trunk/doc/ChangeLog
===================================================================
--- trunk/doc/ChangeLog 2010-10-04 21:08:34 UTC (rev 5434)
+++ trunk/doc/ChangeLog 2010-10-05 13:56:25 UTC (rev 5435)
@@ -1,3 +1,7 @@
+2010-10-05 Werner Koch <wk at g10code.com>
+
+ * Makefile.am (faq.txt faq.html, faq-online): New.
+
2010-10-04 Werner Koch <wk at g10code.com>
* faq.org: New.
Added: trunk/doc/FAQ
===================================================================
--- trunk/doc/FAQ (rev 0)
+++ trunk/doc/FAQ 2010-10-05 13:56:25 UTC (rev 5435)
@@ -0,0 +1,13 @@
+GnuPG Frequently Asked Questions
+
+A FAQ is a fast moving target and thus we don't distribute it anymore
+with GnuPG. You may retrieve the current FAQ in HTML format at
+
+ http://www.gnupg.org/faq/GnuPG-FAQ.html
+
+or in plain text format at the FTP server:
+
+ ftp://ftp.gnupg.org/gcrypt/gnupg/GnuPG-FAQ.txt
+
+
+
Modified: trunk/doc/Makefile.am
===================================================================
--- trunk/doc/Makefile.am 2010-10-04 21:08:34 UTC (rev 5434)
+++ trunk/doc/Makefile.am 2010-10-05 13:56:25 UTC (rev 5435)
@@ -75,7 +75,7 @@
watchgnupg_SOURCE = gnupg.texi
-CLEANFILES = yat2m
+CLEANFILES = yat2m faq.txt faq.html
DISTCLEANFILES = gnupg.tmp gnupg.ops yat2m-stamp.tmp yat2m-stamp \
$(myman_pages) gnupg.7
@@ -140,3 +140,24 @@
rsync -vr --exclude='.svn' . \
$${user}@cvs.gnupg.org:webspace/manuals/gnupg$${dashdevel}/
+# Note that you need a recent version of emacs23 with org-mode 7.01h
+faq.txt faq.html: faq.org
+ @set -e; expopt="t nil nil nil \"$$(pwd)\""; \
+ emacs --batch \
+ --eval "(require 'org)" \
+ --visit "$(srcdir)/faq.org" \
+ --eval "(setq org-export-ascii-entities 'utf8)" \
+ --eval "(org-export-as-ascii org-export-headline-levels $${expopt})"\
+ --visit "$(srcdir)/faq.org" \
+ --eval "(setq org-export-html-style-include-default nil)" \
+ --eval "(setq org-export-html-style-include-scripts nil)" \
+ --eval "(org-export-as-html org-export-headline-levels $${expopt})"
+
+faq-online: faq.txt faq.html
+ set -e; \
+ user=werner ; \
+ echo "Uploading current FAQ to {www,ftp}.gnupg.org ..."; \
+ scp faq.html $${user}@ftp.gnupg.org:webspace/manuals/GnuPG-FAQ.html ; \
+ scp faq.txt $${user}@ftp.gnupg.org:gcrypt/gnupg/GnuPG-FAQ.txt ; \
+ echo "...ready"
+
Modified: trunk/doc/faq.org
===================================================================
--- trunk/doc/faq.org 2010-10-04 21:08:34 UTC (rev 5434)
+++ trunk/doc/faq.org 2010-10-05 13:56:25 UTC (rev 5435)
@@ -1,3 +1,4 @@
+# faq.org -*- coding: utf-8; -*-
#+STARTUP: overview
#+OPTIONS: H:2 num:t toc:t \n:nil @:t ::t |:t ^:t *:t TeX:t
#+EMAIL: wk at gnupg.org
@@ -6,9 +7,8 @@
#+TITLE: GnuPG Frequently Asked Questions
#+OPTIONS: H:3 num:nil toc:t \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
#+LINK: gnupgweb http://www.gnupg.org/
-#+LINK gnupgftp ftp://ftp.gnupg.org/gcrypt/
#+LINK: roundup https://bugs.g10code.com/gnupg/issue
-#+STYLE: <link rel="stylesheet" type="text/css" href="http://www.gnupg.org/share/site.css" />
+###+STYLE: <link rel="stylesheet" type="text/css" href="http://www.gnupg.org/share/site.css" />
# FIXME: This FAQ needs a heavy cleanup. For now I only switched to
# org-mode format for easier maintenance.
@@ -17,26 +17,36 @@
<a href="/"><img src="http://gnupg.org/share/logo-gnupg-light-purple-bg.png" class="logo-link" /></a>
#+end_html
+*WARNING: This FAQ is heavily outdated*. Mentioned versions of GnuPG
+have reached end of life many years ago. Almost all bugs and problems
+have been fixed in the now current versions of GnuPG. We will try to
+update this FAQ in the next month.
+
+
* Welcome
:PROPERTIES:
:CUSTOM_ID: welcome
:END:
- Welcome to the GnuPG FAQ. The latest HTML version is available
- [[gnupgweb:faq.html][here]].
+ Welcome to the GnuPG FAQ. The latest HTML version is available at\\
+ [[http://www.gnupg.org/faq/GnuPG-FAQ.html]]; \\
+ a plain text Gversion at \\
+ ftp://ftp.gnupg.org/gcrypt/gnupg/GnuPG-FAQ.txt.
+ See the end of this file for the release date.
+
The index is generated automatically, so there may be errors. Not
all questions may be in the section they belong to. Suggestions
about how to improve the structure of this FAQ are welcome.
- Please send additions and corrections to the gnupg users mailing
+ Please send additions and corrections to the gnupg-users mailing
list. It would be most convenient if you could provide the answer to
be included here as well. Your help is very much appreciated!
Please, don't send message like "This should be a FAQ - what's the
- answer?". If it hasn't been asked before, it isn't a FAQ. In that case
- you could search in the mailing list archive.
+ answer?". If it hasn't been asked before, it isn't a FAQ. In that
+ case you could search in the mailing list archive.
** What conventions are used in this FAQ?
:PROPERTIES:
@@ -46,9 +56,9 @@
Although GnuPG is being developed for several operating systems
(often in parallel), the conventions used in this FAQ reflect a
UNIX shell environment. For Win32 users, references to a shell
- prompt (`$') should be interpreted as a command prompt (`>'),
- directory names separated by a forward slash (`/') may need to be
- converted to a back slash (`\'), and a tilde (`~') represents a
+ prompt (=$=) should be interpreted as a command prompt (=>=),
+ directory names separated by a forward slash (=/=) may need to be
+ converted to a back slash (=\=), and a tilde (=~=) represents a
user's "home" directory (reference question [[id:how-do-i-put-my-keyring-in-a-different-directory][How do I put my keyring in a different directory?]] for an example).
Some command-lines presented in this FAQ are too long to properly
@@ -65,7 +75,9 @@
containing user options and settings has been renamed from "options"
to "gpg.conf". Information in the FAQ that relates to the options
file may be interchangable with the newer gpg.conf file in many
- instances. See question <Roptions> for details.
+ instances. See question
+ [[#gnupg-no-longer-installs-a-options-file-is-it-missing][GnuPG no longer installs a ~/.gnupg/options file. Is it missing?]]
+ for details.
* General Questions
@@ -88,7 +100,9 @@
In general, yes. GnuPG and newer PGP releases should be implementing
the OpenPGP standard. But there are some interoperability problems.
- See question <Rcompat> for details.
+ See question
+ [[#how-can-i-encrypt-a-message-so-that-pgp-is-able-to-decrypt-it][How can I encrypt a message with GnuPG so that PGP is able to decrypt it?]]
+ for details.
** Is GnuPG free to use for personal or commercial use?
:PROPERTIES:
@@ -110,47 +124,43 @@
:CUSTOM_ID: more-information-on-gnupg
:END:
- On-line resources:
+ On-line resources:
- [H ul]
- [H li]The documentation page is located at [H a href=[$hGPGHTTP]/documentation/]<[$hGPGHTTP]/documentation/>[H/a].
- Also, have a look at the HOWTOs and the GNU Privacy Handbook (GPH,
- available in English, Spanish and Russian). The latter provides a
- detailed user's guide to GnuPG. You'll also find a document about how
- to convert from PGP 2.x to GnuPG.
+ - The documentation page is located at [[gnupgweb:documentation/]].
+ Also, have a look at the HOWTOs and the GNU Privacy Handbook
+ (GPH, available in English, Spanish and Russian). The latter
+ provides a detailed user's guide to GnuPG. You'll also find a
+ document about how to convert from PGP 2.x to GnuPG.
- [H li]At [H a href=[$hGPGHTTP]/documentation/mailing-lists.html]<[$hGPGHTTP]/documentation/mailing-lists.html>[H/a] you'll find
- an online archive of the GnuPG mailing lists. Most interesting should
- be gnupg-users for all user-related issues and gnupg-devel if you want
- to get in touch with the developers.
+ - At [[gnupgweb:documentation/mailing-lists.html]] you'll find an
+ online archive of the GnuPG mailing lists. Most interesting
+ should be gnupg-users for all user-related issues and gnupg-devel
+ if you want to get in touch with the developers.
- In addition, searchable archives can be found on MARC, e.g.: [H br]
- gnupg-users: [H a href=http://marc.theaimsgroup.com/?l=gnupg-users&r=1&w=2]<http://marc.theaimsgroup.com/?l=gnupg-users&r=1&w=2>[H/a][H br]
- gnupg-devel: [H a href=http://marc.theaimsgroup.com/?l=gnupg-devel&r=1&w=2]<http://marc.theaimsgroup.com/?l=gnupg-devel&r=1&w=2>[H/a][H br]
+ In addition, searchable archives can be found on MARC, e.g.:\\
+ For gnupg-users : [[http://marc.theaimsgroup.com/?l=gnupg-users&r=1&w=2]]\\
+ For gnupg-devel : [[http://marc.theaimsgroup.com/?l=gnupg-devel&r=1&w=2]]
- [H b]PLEASE:[H /b]
- Before posting to a list, read this FAQ and the available documentation.
- In addition, search the list archive - maybe your question has already
- been discussed. This way you help people focus on topics that have not
- yet been resolved.
+ *Please:* Before posting to a list, read this FAQ and the
+ available documentation. In addition, search the list archive
+ --- maybe your question has already been discussed. This way you
+ help people focus on topics that have not yet been resolved.
- [H li]The GnuPG source distribution contains a subdirectory:
+ - The GnuPG source distribution contains a subdirectory:
- [H samp]
- ./doc
- [H /samp]
+ : ./doc
- where some additional documentation is located (mainly interesting
- for hackers, not the casual user).
- [H /ul]
+ where some additional documentation is located (mainly
+ interesting for hackers, not the casual user).
+
** Where do I get GnuPG?
:PROPERTIES:
:CUSTOM_ID: where-do-i-get-gnupg
:END:
You can download the GNU Privacy Guard from its primary FTP server
- [[gnupgftp:gnupg/][ftp.gnupg.org]] or from one of its [[gnupgweb:download/mirrors.html][mirrors]].
+ [[ftp://ftp.gnupg.org/gcrypt/gnupg/][ftp.gnupg.org]] or from one of its [[gnupgweb:download/mirrors.html][mirrors]].
The current stable version is FIXME. Please upgrade to this
version as it includes additional features, functions and security
@@ -163,13 +173,11 @@
:CUSTOM_ID: which-oses-does-gnupg-run-on
:END:
- It should run on most Unices as well as Windows versions (including
- Windows NT/2000) and Macintosh OS/X. A list of OSes reported to be OK
- is presented at:
+ It should run on most Unices as well as Windows versions
+ (including Windows NT/2000) and Macintosh OS/X. A list of OSes
+ reported to be OK is presented at:
- [H a href=[$hGPGHTTP]/download/supported_systems.html]
- <[$hGPGHTTP]/download/supported_systems.html>
- [H /a]
+ [[gnupgweb:download/supported_systems.html]]
** Which random data gatherer should I use?
:PROPERTIES:
@@ -183,30 +191,25 @@
systems. Also Solaris users with the SUNWski package installed have
a /dev/random. In these cases, use the configure option:
- [H samp]
- --enable-static-rnd=linux
- [H /samp]
+ : --enable-static-rnd=linux
In addition, there's also the kernel random device by Andi Maier
- [H a href= http://www.cosy.sbg.ac.at/~andi/SUNrand/]<http://www.cosy.sbg.ac.at/~andi/SUNrand/>[H /a], but it's still beta. Use at your
- own risk!
+ [[http://www.cosy.sbg.ac.at/~andi/SUNrand/]], but it's still beta. Use
+ at your own risk!
On other systems, the Entropy Gathering Daemon (EGD) is a good choice.
It is a perl-daemon that monitors system activity and hashes it into
- random data. See the download page [H a href=[$hGPGHTTP]/download/]<[$hGPGHTTP]/download/>[H /a]
+ random data. See the download page [[gnupgweb:download/]]
to obtain EGD. Use:
- [H samp]
- --enable-static-rnd=egd
- [H /samp]
+ : --enable-static-rnd=egd
here.
If the above options do not work, you can use the random number
- generator "unix". This is [H B]very[H /B] slow and should be avoided. The
+ generator "unix". This is *very slow* and should be avoided. The
random quality isn't very good so don't use it on sensitive data.
-<Didea>
** How do I include support for RSA and IDEA?
:PROPERTIES:
:CUSTOM_ID: how-do-i-include-support-for-rsa-and-idea
@@ -220,25 +223,19 @@
However, there is an unofficial module to include it even in earlier
versions of GnuPG. It's available from
- [H a href=ftp://ftp.gnupg.dk/pub/contrib-dk/]<ftp://ftp.gnupg.dk/pub/contrib-dk/>[H /a]. Look for:
+ [[ftp://ftp.gnupg.dk/pub/contrib-dk/]]. Look for:
- [H pre]
- idea.c.gz (c module)
- idea.c.gz.sig (signature file)
- [H /pre]
+ : idea.c.gz (c module)
+ : idea.c.gz.sig (signature file)
- [H pre]
- ideadll.zip (c module and win32 dll)
- ideadll.zip.sig (signature file)
- [H /pre]
+ : ideadll.zip (c module and win32 dll)
+ : ideadll.zip.sig (signature file)
Compilation directives are in the headers of these files. You will
- then need to add the following line to your ~/.gnupg/gpg.conf or
- ~/.gnupg/options file:
+ then need to add the following line to your =~/.gnupg/gpg.conf= or
+ =~/.gnupg/options= file:
- [H samp]
- load-extension idea
- [H /samp]
+ : load-extension idea
* Usage
@@ -254,9 +251,7 @@
have greater sizes, but you should then check the fingerprint of
this key:
- [H samp]
- $ gpg --fingerprint <user ID>
- [H /samp]
+ : $ gpg --fingerprint <user ID>
As for the key algorithms, you should stick with the default (i.e.,
DSA signature and Elgamal encryption). An Elgamal signing key has
@@ -312,15 +307,13 @@
If you do a 'gpg --help', you will get two separate lists. The first
is a list of commands. The second is a list of options. Whenever you
- run GPG, you [H b]must[H /b] pick exactly one command (with one exception,
- see below). You [H b]may[H /b] pick one or more options. The command should,
+ run GPG, you *must* pick exactly one command (with one exception,
+ see below). You *may* pick one or more options. The command should,
just by convention, come at the end of the argument list, after all
the options. If the command takes a file (all the basic ones do),
the filename comes at the very end. So the basic way to run gpg is:
- [H samp]
- $ gpg [--option something] [--option2] [--option3 something] --command file
- [H /samp]
+ : $ gpg [--option something] [--option2] [--option3 something] --command file
Some options take arguments. For example, the --output option (which
can be abbreviated as -o) is an option that takes a filename. The
@@ -333,49 +326,37 @@
followed by the file you wish to encrypt. Therefore in this example
the command-line issued would be:
- [H samp]
- $ gpg -r alice -o secret.txt -e test.txt
- [H /samp]
+ : $ gpg -r alice -o secret.txt -e test.txt
If you write the options out in full, it is easier to read:
- [H samp]
- $ gpg --recipient alice --output secret.txt --encrypt test.txt
- [H /samp]
+ : $ gpg --recipient alice --output secret.txt --encrypt test.txt
If you're encrypting to a file with the extension ".txt", then you'd
probably expect to see ASCII-armored text in the file (not binary),
so you need to add the --armor (-a) option, which doesn't take any
arguments:
- [H samp]
- $ gpg --armor --recipient alice --output secret.txt --encrypt test.txt
- [H /samp]
+ : $ gpg --armor --recipient alice --output secret.txt --encrypt test.txt
If you imagine square brackets around the optional parts, it becomes
a bit clearer:
- [H samp]
- $ gpg [--armor] [--recipient alice] [--output secret.txt] --encrypt test.txt
- [H /samp]
+ : $ gpg [--armor] [--recipient alice] [--output secret.txt] --encrypt test.txt
The optional parts can be rearranged any way you want:
- [H samp]
- $ gpg --output secret.txt --recipient alice --armor --encrypt test.txt
- [H /samp]
+ : $ gpg --output secret.txt --recipient alice --armor --encrypt test.txt
If your filename begins with a hyphen (e.g. "-a.txt"), GnuPG assumes
this is an option and may complain. To avoid this you have to either
- use "./-a.txt", or stop the option and command processing with two
- hyphens: "-- -a.txt".
+ use =./-a.txt=, or stop the option and command processing with two
+ hyphens: =-- -a.txt=.
- [H B]The exception to using only one command:[H /B] signing and encrypting
+ *The exception to using only one command*: signing and encrypting
at the same time. For this you can combine both commands, such as in:
- [H samp]
- $ gpg [--options] --sign --encrypt foo.txt
- [H /samp]
+ : $ gpg [--options] --sign --encrypt foo.txt
** I can't delete a user ID on my secret keyring because it has already been deleted on my public keyring. What can I do?
:PROPERTIES:
@@ -405,7 +386,8 @@
If you've lost your public key and need to recreate it instead
for continued use with your secret key, you may be able to use
- gpgsplit as detailed in question <Rgpgsplit>.
+ gpgsplit as detailed in question
+ [[#i-still-have-my-secret-key-but-lost-my-public-key][I still have my secret key, but lost my public key. What can I do?]].
@@ -454,7 +436,11 @@
:CUSTOM_ID: get-rid-of-the-version-and-comment-headers-in-armored-messages
:END:
- Use "--no-version --comment ''". Note that the left over blank line
+ Use
+
+ : --no-version --comment ''
+
+ Note that the left over blank line
is required by the protocol.
** What does the "You are using the xxxx character set." mean?
@@ -462,76 +448,82 @@
:CUSTOM_ID: what-does-the-you-are-using-the-xxx-character-set-mean
:END:
- This note is printed when UTF-8 mapping has to be done. Make sure
- that the displayed character set is the one you have activated on
- your system. Since "iso-8859-1" is the character set most used,
- this is the default. You can change the charset with the option
- "--charset". It is important that your active character set matches
- the one displayed - if not, restrict yourself to plain 7 bit ASCII
- and no mapping has to be done.
+ This note is printed when UTF-8 mapping has to be done. Make sure
+ that the displayed character set is the one you have activated on
+ your system. Since "iso-8859-1" is the character set most used,
+ this is the default. You can change the charset with the option
+ =--charset=. It is important that your active character set matches
+ the one displayed --- if not, restrict yourself to plain 7 bit
+ ASCII and no mapping has to be done.
** How can I get list of key IDs used to encrypt a message?
:PROPERTIES:
:CUSTOM_ID: how-can-i-get-list-of-key-ids-used-to-encrypt-a-message
:END:
- [H samp]
- $ gpg --batch --decrypt --list-only --status-fd 1 2>/dev/null |
- awk '/^\[GNUPG:\] ENC_TO / { print $3 }'
- [H /samp]
+ : $ gpg --batch --decrypt --list-only --status-fd 1 2>/dev/null | \
+ : awk '/^\[GNUPG:\] ENC_TO / { print $3 }'
** Why can't I decrypt files encrypted as symmetrical-only (-c) with a version of GnuPG prior to 1.0.1.
:PROPERTIES:
:CUSTOM_ID: why-cant-i-decrypt-symmetrical-only-with-gnupg-prior-to-1.0.1
:END:
- There was a bug in GnuPG versions prior to 1.0.1 which affected files
- only if 3DES or Twofish was used for symmetric-only encryption (this has
- never been the default). The bug has been fixed, but to enable decryption
- of old files you should run gpg with the option "--emulate-3des-s2k-bug",
- decrypt the file and encrypt it again without this option.
+ There was a bug in GnuPG versions prior to 1.0.1 which affected files
+ only if 3DES or Twofish was used for symmetric-only encryption (this has
+ never been the default). The bug has been fixed, but to enable decryption
+ of old files you should run gpg with the option =--emulate-3des-s2k-bug=,
+ decrypt the file and encrypt it again without this option.
- NOTE: This option was removed in GnuPG development version 1.1.0 and later
- updates, so you will need to use a version between 1.0.1 and 1.0.7 to
- re-encrypt any affected files.
+ NOTE: This option was removed in GnuPG development version 1.1.0 and later
+ updates, so you will need to use a version between 1.0.1 and 1.0.7 to
+ re-encrypt any affected files.
** How can I use GnuPG in an automated environment?
:PROPERTIES:
:CUSTOM_ID: how-can-i-use-gnupg-in-an-automated-environment
:END:
- You should use the option --batch and don't use passphrases as
- there is usually no way to store it more securely than on the
- secret keyring itself. The suggested way to create keys for an
- automated environment is:
+ You should use the option =--batch= and don't use passphrases as
+ there is usually no way to store it more securely than on the
+ secret keyring itself. The suggested way to create keys for an
+ automated environment is:
- On a secure machine:
- [H ol]
- [H li] If you want to do automatic signing, create a signing subkey
- for your key (use the interactive key editing menu by issueing
- the command 'gpg --edit-key keyID', enter "addkey" and select
- the DSA key type).
- [H li] Make sure that you use a passphrase (needed by the current
- implementation).
- [H li] gpg --export-secret-subkeys --no-comment foo >secring.auto
- [H li] Copy secring.auto and the public keyring to a test directory.
- [H li] Change to this directory.
- [H li] gpg --homedir . --edit foo and use "passwd" to remove the
- passphrase from the subkeys. You may also want to remove all
- unused subkeys.
- [H li] Copy secring.auto to a floppy and carry it to the target box.
- [H /ol]
+ On a secure machine:
+
+ 1. If you want to do automatic signing, create a signing subkey for
+ your key. Use the interactive key editing menu by issueing the
+ command
+ : gpg --edit-key keyID
+ enter "addkey" and select the DSA key type).
- On the target machine:
- [H ol]
- [H li] Install secring.auto as the secret keyring.
- [H li] Now you can start your new service. It's also a good idea to
- install an intrusion detection system so that you hopefully
- get a notice of an successful intrusion, so that you in turn
- can revoke all the subkeys installed on that machine and
- install new subkeys.
- [H /ol]
+ 1. Make sure that you use a passphrase (needed by the current
+ implementation).
+ 1.
+ : gpg --export-secret-subkeys --no-comment foo >secring.auto
+
+ 1. Copy secring.auto and the public keyring to a test directory.
+
+ 1. Change to this directory.
+
+ 1. Run the command
+ : gpg --homedir . --edit foo
+
+ and use the sub-command =passwd= to remove the passphrase from the
+ subkeys. You may also want to remove all unused subkeys.
+
+ 1. Copy secring.auto to a floppy and carry it to the target box.
+
+ On the target machine:
+
+ 1. Install secring.auto as the secret keyring.
+ 1. Now you can start your new service. It's also a good idea to
+ install an intrusion detection system so that you hopefully get
+ a notice of an successful intrusion, so that you in turn can
+ revoke all the subkeys installed on that machine and install new
+ subkeys.
+
** Which email-client can I use with GnuPG?
:PROPERTIES:
:CUSTOM_ID: which-email-client-can-i-use-with-gnupg
@@ -549,66 +541,62 @@
The following list is not exhaustive:
- [H pre]
- MUA OpenPGP ASCII How? (N,P,T)
- -------------------------------------------------------------
- Calypso N Y P (Unixmail)
- Elm N Y T (mailpgp,morepgp)
- Elm ME+ N Y N
- Emacs/Gnus Y Y T (Mailcrypt,gpg.el)
- Emacs/Mew Y Y N
- Emacs/VM N Y T (Mailcrypt)
- Evolution Y Y N
- Exmh Y Y N
- GNUMail.app Y Y P (PGPBundle)
- GPGMail Y Y N
- KMail (<=1.4.x) N Y N
- KMail (1.5.x) Y(P) Y(N) P/N
- Mozilla Y Y P (Enigmail)
- Mulberry Y Y P
- Mutt Y Y N
- Sylpheed Y Y N
- Claws-mail Y Y N
- TkRat Y Y N
- XEmacs/Gnus Y Y T (Mailcrypt)
- XEmacs/Mew Y Y N
- XEmacs/VM N Y T (Mailcrypt)
- XFmail Y Y N
+ | MUA | OpenPGP | ASCII | How? (N,P,T) |
+ |-----------------+---------+-------+----------------------|
+ | Calypso | N | Y | P (Unixmail) |
+ | Elm | N | Y | T (mailpgp,morepgp) |
+ | Elm ME+ | N | Y | N |
+ | Emacs/Gnus | Y | Y | T (Mailcrypt,gpg.el) |
+ | Emacs/Mew | Y | Y | N |
+ | Emacs/VM | N | Y | T (Mailcrypt) |
+ | Evolution | Y | Y | N |
+ | Exmh | Y | Y | N |
+ | GNUMail.app | Y | Y | P (PGPBundle) |
+ | GPGMail | Y | Y | N |
+ | KMail (<=1.4.x) | N | Y | N |
+ | KMail (1.5.x) | Y(P) | Y(N) | P/N |
+ | Mozilla | Y | Y | P (Enigmail) |
+ | Mulberry | Y | Y | P |
+ | Mutt | Y | Y | N |
+ | Sylpheed | Y | Y | N |
+ | Claws-mail | Y | Y | N |
+ | TkRat | Y | Y | N |
+ | XEmacs/Gnus | Y | Y | T (Mailcrypt) |
+ | XEmacs/Mew | Y | Y | N |
+ | XEmacs/VM | N | Y | T (Mailcrypt) |
+ | XFmail | Y | Y | N |
- N - Native, P - Plug-in, T - External Tool
- [H /pre]
+ ( N - Native, P - Plug-in, T - External Tool)
The following table lists proprietary MUAs. The GNU Project
suggests against the use of these programs, but they are listed
for interoperability reasons for your convenience.
- [H pre]
- MUA OpenPGP ASCII How? (N,P,T)
- -------------------------------------------------------------
- Apple Mail Y Y P (GPGMail)
- Becky2 Y Y P (BkGnuPG)
- Eudora Y Y P (EuroraGPG)
- Eudora Pro Y Y P (EudoraGPG)
- Lotus Notes N Y P
- Netscape 4.x N Y P
- Netscape 7.x Y Y P (Enigmail)
- Novell Groupwise N Y P
- Outlook N Y P (G-Data)
- Outlook Express N Y P (GPGOE)
- Pegasus N Y P (QDPGP,PM-PGP)
- Pine N Y T (pgpenvelope,(gpg|pgp)4pine)
- Postme N Y P (GPGPPL)
- The Bat! N Y P (Ritlabs)
- [H /pre]
+ | MUA | OpenPGP | ASCII | How? (N,P,T) |
+ |------------------+---------+-------+--------------------------|
+ | Apple Mail | Y | Y | P (GPGMail) |
+ | Becky2 | Y | Y | P (BkGnuPG) |
+ | Eudora | Y | Y | P (EuroraGPG) |
+ | Eudora Pro | Y | Y | P (EudoraGPG) |
+ | Lotus Notes | N | Y | P |
+ | Netscape 4.x | N | Y | P |
+ | Netscape 7.x | Y | Y | P (Enigmail) |
+ | Novell Groupwise | N | Y | P |
+ | Outlook | N | Y | P (G-Data) |
+ | Outlook Express | N | Y | P (GPGOE) |
+ | Pegasus | N | Y | P (QDPGP,PM-PGP) |
+ | Pine | N | Y | T (pgpenvelope,gpg4pine) |
+ | Postme | N | Y | P (GPGPPL) |
+ | The Bat! | N | Y | P (Ritlabs) |
- Good overviews of OpenPGP-support can be found at:[H br]
- [H a href=http://www.openpgp.fr.st/courrier_en.html]<http://www.openpgp.fr.st/courrier_en.html>[H /a] and[H br]
- [H a href=http://www.bretschneidernet.de/tips/secmua.html]<http://www.bretschneidernet.de/tips/secmua.html>[H /a].
+ Good overviews of OpenPGP-support can be found at:\\
+ [[http://www.openpgp.fr.st/courrier_en.html]] \\
+ http://www.bretschneidernet.de/tips/secmua.html
- Users of Win32 MUAs that lack OpenPGP support may look into
- using GPGrelay [H a href=http://gpgrelay.sourceforge.net]<http://gpgrelay.sourceforge.net>[H /a], a small
- email-relaying server that uses GnuPG to enable many email clients
- to send and receive emails that conform to PGP-MIME (RFC 2015).
+ Users of Win32 MUAs that lack OpenPGP support may look into using
+ GPGrelay http://gpgrelay.sourceforge.net, a small email-relaying
+ server that uses GnuPG to enable many email clients to send and
+ receive emails that conform to PGP-MIME (RFC 2015).
** Can't we have a gpg library?
:PROPERTIES:
@@ -619,60 +607,55 @@
of the GnuPG maintainers is that this would lead to several security
issues and will therefore not be implemented in the foreseeable
future. However, for some areas of application gpgme could do the
- trick. You'll find it at [H a href=[$hGPGFTP]/gcrypt/alpha/gpgme]<[$hGPGFTP]/gcrypt/alpha/gpgme>[H /a].
+ trick. You'll find it at [[gnupgweb:related_software/gpgme]].
** I have successfully generated a revocation certificate, but I don't understand how to send it to the key servers.
:PROPERTIES:
:CUSTOM_ID: how-to-send-a-revocation-to-the-keyservers
:END:
- Most keyservers don't accept a 'bare' revocation certificate. You
- have to import the certificate into gpg first:
+ Most keyservers don't accept a 'bare' revocation certificate. You
+ have to import the certificate into gpg first:
- [H samp]
- $ gpg --import my-revocation.asc
- [H /samp]
+ : $ gpg --import my-revocation.asc
- then send the revoked key to the keyservers:
+ then send the revoked key to the keyservers:
- [H samp]
- $ gpg --keyserver certserver.pgp.com --send-keys mykeyid
- [H /samp]
+ : $ gpg --keyserver certserver.pgp.com --send-keys mykeyid
- (or use a keyserver web interface for this).
+ (or use a keyserver web interface for this).
** How do I put my keyring in a different directory?
:PROPERTIES:
:CUSTOM_ID: how-do-i-put-my-keyring-in-a-different-directory
:END:
- GnuPG keeps several files in a special homedir directory. These
- include the options file, pubring.gpg, secring.gpg, trustdb.gpg,
- and others. GnuPG will always create and use these files. On unices,
- the homedir is usually ~/.gnupg; on Windows it is name "gnupg" and
- found below the user's application directory. Run the gpg and
- pass the option --version to see the name of that directory.
+ GnuPG keeps several files in a special homedir directory. These
+ include the options file, pubring.gpg, secring.gpg, trustdb.gpg,
+ and others. GnuPG will always create and use these files. On
+ unices, the homedir is usually ~/.gnupg; on Windows it is name
+ "gnupg" and found below the user's application directory. Run the
+ gpg and pass the option --version to see the name of that
+ directory.
- If you want to put your keyrings somewhere else, use the option:
+ If you want to put your keyrings somewhere else, use the option:
- [H samp]
- --homedir /my/path/
- [H /samp]
+ : --homedir /my/path/
- to make GnuPG create all its files in that directory. Your keyring
- will be "/my/path/pubring.gpg". This way you can store your secrets
- on a floppy disk. Don't use "--keyring" as its purpose is to specify
- additional keyring files.
+ to make GnuPG create all its files in that directory. Your keyring
+ will be "/my/path/pubring.gpg". This way you can store your secrets
+ on a floppy disk. Don't use "--keyring" as its purpose is to specify
+ additional keyring files.
** How do I verify signed packages?
:PROPERTIES:
:CUSTOM_ID: how-do-i-verify-signed-packages
:END:
- Before you can verify the signature that accompanies a package,
- you must first have the vendor, organisation, or issueing person's
- key imported into your public keyring. To prevent GnuPG warning
- messages the key should also be validated (or locally signed).
+ must first have the vendor, organisation, or issueing person's key
+ Before you can verify the signature that accompanies a package, you
+ imported into your public keyring. To prevent GnuPG warning
+ messages the key should also be validated (or locally signed).
You will also need to download the detached signature file along
with the package. These files will usually have the same name as
@@ -682,9 +665,7 @@
Once their key has been imported, and the package and accompanying
signature files have been downloaded, use:
- [H samp]
- $ gpg --verify sigfile signed-file
- [H /samp]
+ : $ gpg --verify sigfile signed-file
If the signature file has the same base name as the package file,
the package can also be verified by specifying just the signature
@@ -693,9 +674,7 @@
package named foobar.tar.gz against its detached binary signature
file, use:
- [H samp]
- $ gpg --verify foobar.tar.gz.sig
- [H /samp]
+ : $ gpg --verify foobar.tar.gz.sig
** How do I export a keyring with only selected signatures (keys)?
:PROPERTIES:
@@ -706,11 +685,8 @@
selected from a master keyring (for a club, user group, or company
department for example), simply specify the keys you want to export:
- [H samp]
- $ gpg --armor --export key1 key2 key3 key4 > keys1-4.asc
- [H /samp]
+ : $ gpg --armor --export key1 key2 key3 key4 > keys1-4.asc
-<Dgpgsplit>
** I still have my secret key, but lost my public key. What can I do?
:PROPERTIES:
:CUSTOM_ID: i-still-have-my-secret-key-but-lost-my-public-key
@@ -724,9 +700,7 @@
(it's actually a new option for gpgsplit) and is available with GnuPG
versions 1.2.1 or later (or can be found in CVS). It works like this:
- [H samp]
- $ gpgsplit --no-split --secret-to-public secret.gpg >publickey.gpg
- [H /samp]
+ : $ gpgsplit --no-split --secret-to-public secret.gpg >publickey.gpg
One should first try to export the secret key and convert just this
one. Using the entire secret keyring should work too. After this has
@@ -748,7 +722,6 @@
* Compatibility Issues
-<Dcompat>
** How can I encrypt a message with GnuPG so that PGP is able to decrypt it?
:PROPERTIES:
:CUSTOM_ID: how-can-i-encrypt-a-message-so-that-pgp-is-able-to-decrypt-it
@@ -756,40 +729,36 @@
It depends on the PGP version.
- [H ul]
- [H li]PGP 2.x[H br]
- You can't do that because PGP 2.x normally uses IDEA which is not
- supported by GnuPG as it is patented (see <Ridea>), but if you have a
- modified version of PGP you can try this:
+ - PGP 2.x ::
- [H samp]
- $ gpg --rfc1991 --cipher-algo 3des ...
- [H /samp]
+ You can't do that because PGP 2.x normally uses IDEA which is
+ not supported by GnuPG as it is patented (see [[#how-do-i-include-support-for-rsa-and-idea][How do I include
+ support for RSA and IDEA?]]), but if you have a modified version
+ of PGP you can try this:
- Please don't pipe the data to encrypt to gpg but provide it using a
- filename; otherwise, PGP 2 will not be able to handle it.
+ : $ gpg --rfc1991 --cipher-algo 3des ...
- As for conventional encryption, you can't do this for PGP 2.
+ Please don't pipe the data to encrypt to gpg but provide it
+ using a filename; otherwise, PGP 2 will not be able to handle
+ it.
- [H li]PGP 5.x and higher[H br]
- You need to provide two additional options:
+ As for conventional encryption, you can't do this for PGP 2.
- [H samp]
- --compress-algo 1 --cipher-algo cast5
- [H /samp]
+ - PGP 5.x and higher ::
- You may also use "3des" instead of "cast5", and "blowfish" does not
- work with all versions of PGP 5. You may also want to put:
+ You need to provide two additional options:
- [H samp]
- compress-algo 1
- [H /samp]
+ : --compress-algo 1 --cipher-algo cast5
- into your ~/.gnupg/options file - this does not affect normal GnuPG
- operation.
+ You may also use "3des" instead of "cast5", and "blowfish" does
+ not work with all versions of PGP 5. You may also want to put:
+ : compress-algo 1
+
+ into your =~/.gnupg/options= file --- this does not affect
+ normal GnuPG operation.
+
This applies to conventional encryption as well.
- [H /UL]
** How do I migrate from PGP 2.x to GnuPG?
:PROPERTIES:
@@ -800,8 +769,9 @@
patent has expired and RSA is included as of GnuPG 1.0.3, the IDEA
algorithm is still patented until 2007. Under certain conditions you
may use IDEA even today. In that case, you may refer to Question
- <Ridea> about how to add IDEA support to GnuPG and read
- [H a href=[$hGPGHTTP]/gph/en/pgp2x.html]<[$hGPGHTTP]/gph/en/pgp2x.html>[H /a] to perform the migration.
+ [[*How%20do%20I%20include%20support%20for%20RSA%20and%20IDEA][How do I include support for RSA and IDEA?]] about how to add
+ IDEA support to GnuPG and read
+ [[gnupgweb:gph/en/pgp2x.html]] to perform the migration.
** Why is PGP 5.x not able to encrypt messages with some keys?
:PROPERTIES:
@@ -834,9 +804,7 @@
There is a script in the tools directory to help you. After you have
imported the PGP keyring you can give this command:
- [H samp]
- $ lspgpot pgpkeyring | gpg --import-ownertrust
- [H /samp]
+ : $ lspgpot pgpkeyring | gpg --import-ownertrust
where pgpkeyring is the original keyring and not the GnuPG keyring
you might have created in the first step.
@@ -851,9 +819,7 @@
PGP is not really OpenPGP aware. A workaround is to export the
secret keys with this command:
- [H samp]
- $ gpg --export-secret-keys --no-comment -a your-KeyID
- [H /samp]
+ : $ gpg --export-secret-keys --no-comment -a your-KeyID
Another possibility is this: by default, GnuPG encrypts your secret
key using the Blowfish symmetric algorithm. Older PGPs will only
@@ -861,10 +827,8 @@
following method you can re-encrypt your secret gpg key with a
different algo:
- [H samp]
- $ gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1
- --compress-algo=1 --edit-key <username>
- [H /samp]
+ : $ gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1 \
+ : --compress-algo=1 --edit-key <username>
Then use passwd to change the password (just change it to the same
thing, but it will encrypt the key with CAST5 this time).
@@ -873,24 +837,23 @@
For PGP 6.x the following options work to export a key:
- [H samp]
- $ gpg --s2k-cipher-algo 3des --compress-algo 1 --rfc1991
- --export-secret-keys <KeyID>
- [H /samp]
+ : $ gpg --s2k-cipher-algo 3des --compress-algo 1 --rfc1991 \
+ : --export-secret-keys <KeyID>
-<Doptions>
+
** GnuPG no longer installs a ~/.gnupg/options file. Is it missing?
:PROPERTIES:
:CUSTOM_ID: gnupg-no-longer-installs-a-options-file-is-it-missing
:END:
- No. The ~/.gnupg/options file has been renamed to ~/.gnupg/gpg.conf for
- new installs as of version 1.1.92. If an existing ~/.gnupg/options file
- is found during an upgrade it will still be used, but this change was
- required to have a more consistent naming scheme with forthcoming tools.
- An existing options file can be renamed to gpg.conf for users upgrading,
- or receiving the message that the "old default options file" is ignored
- (occurs if both a gpg.conf and an options file are found).
+ No. The ~/.gnupg/options file has been renamed to
+ ~/.gnupg/gpg.conf for new installs as of version 1.1.92. If an
+ existing ~/.gnupg/options file is found during an upgrade it will
+ still be used, but this change was required to have a more
+ consistent naming scheme with forthcoming tools. An existing
+ options file can be renamed to gpg.conf for users upgrading, or
+ receiving the message that the "old default options file" is
+ ignored (occurs if both a gpg.conf and an options file are found).
** How do you export GnuPG keys for use with PGP?
:PROPERTIES:
@@ -915,25 +878,19 @@
values, as this will override them in case you have something else set
in your options file.
- [H samp]
- $ gpg --s2k-cipher-algo cast5 --s2k-digest-algo sha1 --s2k-mode 3
- --simple-sk-checksum --edit KeyID
- [H /samp]
+ : $ gpg --s2k-cipher-algo cast5 --s2k-digest-algo sha1 --s2k-mode 3 \
+ : --simple-sk-checksum --edit KeyID
Turn off some features. Set the list of preferred ciphers, hashes,
and compression algorithms to things that PGP can handle. (Yes, I
know this is an odd list of ciphers, but this is what PGP itself uses,
minus IDEA).
- [H samp]
- > setpref S9 S8 S7 S3 S2 S10 H2 H3 Z1 Z0
- [H /samp]
+ : > setpref S9 S8 S7 S3 S2 S10 H2 H3 Z1 Z0
Now put the list of preferences onto the key.
- [H samp]
- > updpref
- [H /samp]
+ : > updpref
Finally we must decrypt and re-encrypt the key, making sure that we
encrypt with a cipher that PGP likes. We set this up in the --edit
@@ -941,22 +898,16 @@
take effect. You can use the same passphrase if you like, or take
this opportunity to actually change it.
- [H samp]
- > passwd
- [H /samp]
+ : > passwd
Save our work.
- [H samp]
- > save
- [H /samp]
+ : > save
Now we can do the usual export:
- [H samp]
- $ gpg --export KeyID > mypublickey.pgp[H br]
- $ gpg --export-secret-key KeyID > mysecretkey.pgp
- [H /samp]
+ : $ gpg --export KeyID > mypublickey.pgp[H br]
+ : $ gpg --export-secret-key KeyID > mysecretkey.pgp
Thanks to David Shaw for this information!
@@ -968,67 +919,58 @@
:CUSTOM_ID: why-do-i-get-gpg_warning_using_insecure_memory
:END:
- On many systems this program should be installed as setuid(root).
- This is necessary to lock memory pages. Locking memory pages prevents
- the operating system from writing them to disk and thereby keeping your
- secret keys really secret. If you get no warning message about insecure
- memory your operating system supports locking without being root. The
- program drops root privileges as soon as locked memory is allocated.
+ On many systems this program should be installed as setuid(root).
+ This is necessary to lock memory pages. Locking memory pages
+ prevents the operating system from writing them to disk and thereby
+ keeping your secret keys really secret. If you get no warning
+ message about insecure memory your operating system supports
+ locking without being root. The program drops root privileges as
+ soon as locked memory is allocated.
- To setuid(root) permissions on the gpg binary you can either use:
+ To setuid(root) permissions on the gpg binary you can either use:
- [H samp]
- $ chmod u+s /path/to/gpg
- [H /samp]
+ : $ chmod u+s /path/to/gpg
- or
+ or
+
+ : $ chmod 4755 /path/to/gpg
- [H samp]
- $ chmod 4755 /path/to/gpg
- [H /samp]
+ Some refrain from using setuid(root) unless absolutely required for
+ security reasons. Please check with your system administrator if
+ you are not able to make these determinations yourself.
- Some refrain from using setuid(root) unless absolutely required for
- security reasons. Please check with your system administrator if you
- are not able to make these determinations yourself.
+ On UnixWare 2.x and 7.x you should install GnuPG with the 'plock'
+ privilege to get the same effect:
- On UnixWare 2.x and 7.x you should install GnuPG with the 'plock'
- privilege to get the same effect:
+ : $ filepriv -f plock /path/to/gpg
- [H samp]
- $ filepriv -f plock /path/to/gpg
- [H /samp]
+ If you can't or don't want to install GnuPG setuid(root), you can
+ use the option "--no-secmem-warning" or put:
- If you can't or don't want to install GnuPG setuid(root), you can
- use the option "--no-secmem-warning" or put:
+ : no-secmem-warning
- [H samp]
- no-secmem-warning
- [H /samp]
+ in your ~/.gnupg/options or ~/.gnupg/gpg.conf file (this disables
+ the warning).
- in your ~/.gnupg/options or ~/.gnupg/gpg.conf file (this disables
- the warning).
+ On some systems (e.g., Windows) GnuPG does not lock memory pages
+ and older GnuPG versions (<=1.0.4) issue the warning:
- On some systems (e.g., Windows) GnuPG does not lock memory pages
- and older GnuPG versions (<=1.0.4) issue the warning:
+ : gpg: Please note that you don't have secure memory
- [H samp]
- gpg: Please note that you don't have secure memory
- [H /samp]
+ This warning can't be switched off by the above option because it
+ was thought to be too serious an issue. However, it confused users
+ too much, so the warning was eventually removed.
- This warning can't be switched off by the above option because it
- was thought to be too serious an issue. However, it confused users
- too much, so the warning was eventually removed.
-
** Large File Support doesn't work
:PROPERTIES:
:CUSTOM_ID: large-file-support-does-not-work
:END:
- LFS works correctly in post-1.0.4 versions. If configure doesn't
- detect it, try a different (i.e., better) compiler. egcs 1.1.2 works
- fine, other gccs sometimes don't. BTW, several compilation problems
- of GnuPG 1.0.3 and 1.0.4 on HP-UX and Solaris were due to broken LFS
- support.
+ LFS works correctly in post-1.0.4 versions. If configure doesn't
+ detect it, try a different (i.e., better) compiler. egcs 1.1.2
+ works fine, other gccs sometimes don't. BTW, several compilation
+ problems of GnuPG 1.0.3 and 1.0.4 on HP-UX and Solaris were due to
+ broken LFS support.
** In the edit menu the trust values are not displayed correctly after signing uids. Why?
:PROPERTIES:
@@ -1131,9 +1073,7 @@
GnuPG installation in a recent state anyway. As a workaround, you can
force gpg to use a previous default cipher algo by putting:
- [H samp]
- cipher-algo cast5
- [H /samp]
+ : cipher-algo cast5
into your options file.
@@ -1199,9 +1139,7 @@
Until then, find the line setting CDPATH in the configure script
and place an:
- [H samp]
- unset CDPATH
- [H /samp]
+ : unset CDPATH
statement below it.
@@ -1278,9 +1216,7 @@
To generate a secret/public keypair, run:
- [H samp]
- $ gpg --gen-key
- [H /samp]
+ : $ gpg --gen-key
and choose the default values.
@@ -1327,9 +1263,7 @@
person it says it comes from. You should be very sure that is really
that person: You should verify the key fingerprint with:
- [H samp]
- $ gpg --fingerprint KeyID
- [H /samp]
+ : $ gpg --fingerprint KeyID
over the phone (if you really know the voice of the other person), at
a key signing party (which are often held at computer conferences),
@@ -1376,51 +1310,44 @@
You can see the validity (calculated trust value) using this
command.
- [H samp]
- $ gpg --list-keys --with-colons
- [H /samp]
+ : $ gpg --list-keys --with-colons
If the first field is "pub" or "uid", the second field shows you the
trust:
- [H pre]
- o = Unknown (this key is new to the system)
- e = The key has expired
- q = Undefined (no value assigned)
- n = Don't trust this key at all
- m = There is marginal trust in this key
- f = The key is full trusted
- u = The key is ultimately trusted; this is only used
- for keys for which the secret key is also available.
- r = The key has been revoked
- d = The key has been disabled
- [H /pre]
+ : o = Unknown (this key is new to the system)
+ : e = The key has expired
+ : q = Undefined (no value assigned)
+ : n = Don't trust this key at all
+ : m = There is marginal trust in this key
+ : f = The key is full trusted
+ : u = The key is ultimately trusted; this is only used
+ : for keys for which the secret key is also available.
+ : r = The key has been revoked
+ : d = The key has been disabled
The value in the "pub" record is the best one of all "uid" records.
You can get a list of the assigned trust values (how much you trust
the owner to correctly sign another person's key) with:
- [H samp]
- $ gpg --list-ownertrust
- [H /samp]
+ : $ gpg --list-ownertrust
The first field is the fingerprint of the primary key, the second
field is the assigned value:
- [H pre]
- - = No ownertrust value yet assigned or calculated.
- n = Never trust this keyholder to correctly verify others signatures.
- m = Have marginal trust in the keyholders capability to sign other
- keys.
- f = Assume that the key holder really knows how to sign keys.
- u = No need to trust ourself because we have the secret key.
- [H /pre]
+ : - = No ownertrust value yet assigned or calculated.
+ : n = Never trust this keyholder to correctly verify others signatures.
+ : m = Have marginal trust in the keyholders capability to sign other
+ : keys.
+ : f = Assume that the key holder really knows how to sign keys.
+ : u = No need to trust ourself because we have the secret key.
Keep these values confidential because they express your opinions
about others. PGP stores this information with the keyring thus it
- is not a good idea to publish a PGP keyring instead of exporting the
- keyring. GnuPG stores the trust in the trustdb.gpg file so it is okay
- to give a gpg keyring away (but we have a --export command too).
+ is not a good idea to publish a PGP keyring instead of exporting
+ the keyring. GnuPG stores the trust in the trustdb.gpg file so it
+ is okay to give a gpg keyring away (but we have a --export command
+ too).
** What kind of output is this: "key C26EE891.298, uid 09FB: ...."?
:PROPERTIES:
@@ -1441,24 +1368,18 @@
information which is prefixed with information about the checked
item.
- [H samp]
- "key 12345678.3456"
- [H /samp]
+ : "key 12345678.3456"
This is about the key with key ID 12345678 and the internal number
3456, which is the record number of the so called directory record
in the trustdb.
- [H samp]
- "uid 12345678.3456/ACDE"
- [H /samp]
+ : "uid 12345678.3456/ACDE"
This is about the user ID for the same key. To identify the user ID
the last two bytes of a ripe-md-160 over the user ID ring is printed.
- [H samp]
- "sig 12345678.3456/ACDE/9A8B7C6D"
- [H /samp]
+ : "sig 12345678.3456/ACDE/9A8B7C6D"
This is about the signature with key ID 9A8B7C6D for the above key
and user ID, if it is a signature which is direct on a key, the user
@@ -1509,9 +1430,9 @@
If you imported a key and you want to also import all the signer's
keys, you can do this with this command:
- gpg --check-sigs --with-colon KEYID \
- | awk -F: '$1 == "sig" && $2 == "?" { print $5 }' \
- | sort | uniq | xargs echo gpg --recv-keys
+ : gpg --check-sigs --with-colon KEYID \
+ : | awk -F: '$1 == "sig" && $2 == "?" { print $5 }' \
+ : | sort | uniq | xargs echo gpg --recv-keys
Note that the invocation of sort is also required to wait for the
of the listing before before starting the import.
@@ -1522,18 +1443,18 @@
:CUSTOM_ID: acknowledgements
:END:
- Many thanks to Nils Ellmenreich for maintaining this FAQ file for
- such a long time, Werner Koch for the original FAQ file, David
- D. Scribner as another maintainer and to all posters to
- gnupg-users and gnupg-devel. They all provided most of the
- answers.
+ Many thanks to Nils Ellmenreich for maintaining this FAQ file for
+ such a long time, David D. Scribner for continuing maintenance,
+ Werner Koch for the original FAQ file, and to all posters to
+ gnupg-users and gnupg-devel. They all provided most of the answers.
+ Converted to org-mode and removed from the tarballs in October 2010.
- Copyright (C) 2000, 2001, 2002, 2003, 2010 Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
- 02111, USA
+ Copyright (C) 2000, 2001, 2002, 2003, 2010 Free Software Foundation,
+ Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02111, USA
- Verbatim copying and distribution of this entire article is
- permitted in any medium, provided this notice is preserved.
+ This file is free software; as a special exception the author gives
+ unlimited permission to copy and/or distribute it, with or without
+ modifications, as long as this notice is preserved.
* COMMENT HTML style specifications
More information about the Gnupg-commits
mailing list