[git] gnupg-doc - branch, master, updated. 8def37abf07d60384864377829a42e3849578623
by Werner Koch
cvs at cvs.gnupg.org
Thu Nov 6 11:31:18 CET 2014
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GnuPG website and other docs".
The branch, master has been updated
via 8def37abf07d60384864377829a42e3849578623 (commit)
via 8bb197809ffedf711ac08332071e9fb39d1ddbbb (commit)
via eacffee435910dc5c2199f25a5de8bcee2d09467 (commit)
via 89f1a299bb6f4e0f3ef9e513aca88e67aa6b8655 (commit)
from da2e0aee2b18f23e154319cbfd7e8ad404cfb2ad (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 8def37abf07d60384864377829a42e3849578623
Author: Werner Koch <wk at gnupg.org>
Date: Thu Nov 6 00:05:47 2014 +0100
web: Release of GnuPG 2.1.0
diff --git a/web/documentation/manuals.org b/web/documentation/manuals.org
index d94b393..c324329 100644
--- a/web/documentation/manuals.org
+++ b/web/documentation/manuals.org
@@ -7,9 +7,10 @@
This is a list of online available manuals. Those marked as "draft" may
document features not yet available in the released software version.
- - GnuPG (2.0) manual : [[file:manuals/gnupg/][HTML]], [[file:manuals/gnupg.pdf][PDF]], [[file:manuals/gnupg-devel/][HTML (draft)]].
- - Dirmngr manual : [[file:manuals/dirmngr/][HTML]], [[file:manuals/dirmngr.pdf][PDF]].
+ - GnuPG (2.1) manual : [[file:manuals/gnupg/][HTML]], [[file:manuals/gnupg.pdf][PDF]]
+# , [[file:manuals/gnupg-devel/][HTML (draft)]].
- Libgcrypt manual : [[file:manuals/gcrypt/][HTML]], [[file:manuals/gcrypt.pdf][PDF]], [[file:manuals/gcrypt-devel/][HTML (draft)]].
- Libksba manual : [[file:manuals/ksba/][HTML]], [[file:manuals/ksba.pdf][PDF]].
- Libassuan manual : [[file:manuals/assuan/][HTML]], [[file:manuals/assuan.pdf][PDF]].
- GPGME manual : [[file:manuals/gpgme/][HTML]], [[file:manuals/gpgme.pdf][PDF]].
+ - Dirmngr manual : [[file:manuals/dirmngr/][HTML]], [[file:manuals/dirmngr.pdf][PDF]] (for GnuPG 2.0).
diff --git a/web/download/index.org b/web/download/index.org
index a9dfbc5..ede8133 100644
--- a/web/download/index.org
+++ b/web/download/index.org
@@ -1,6 +1,7 @@
#+TITLE: GnuPG - Download
#+STARTUP: showall align
#+SETUPFILE: "../share/setup.inc"
+#+OPTIONS: ^:{}
#+macro: check_sig_note GnuPG distributions are signed. It is wise and more secure to check out for their [[integrity_check.org][@@html:<a href="integrity_check.html">@@integrity@@html:</a>@@]].
#+macro: ftpopen @@html:<a href="@@
#+macro: ftpclose @@html:">download</a>@@
@@ -43,7 +44,7 @@
|---------------+------------------------+-------------------------+----------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------|
| | <l> | <r> | | |
| GnuPG stable | {{{gnupg_ver}}} | {{{gnupg_size}}} | {{{ftpopen}}}{{{ftp_base}}}/gnupg/gnupg-{{{gnupg_ver}}}.tar.bz2{{{ftpclose}}} | {{{ftpopen}}}{{{ftp_base}}}/gnupg/gnupg-{{{gnupg_ver}}}.tar.bz2.sig{{{ftpclose}}} |
- | GnuPG modern | {{{gnupg21_ver}}} | | --- | |
+ | GnuPG modern | {{{gnupg21_ver}}} | {{{gnupg21_size}}} | {{{ftpopen}}}{{{ftp_base}}}/gnupg/gnupg-{{{gnupg21_ver}}}.tar.bz2{{{ftpclose}}} | {{{ftpopen}}}{{{ftp_base}}}/gnupg/gnupg-{{{gnupg21_ver}}}.tar.bz2.sig{{{ftpclose}}} |
| GnuPG classic | {{{gnupg1_ver}}} | {{{gnupg1_size}}} | {{{ftpopen}}}{{{ftp_base}}}/gnupg/gnupg-{{{gnupg1_ver}}}.tar.bz2{{{ftpclose}}} | {{{ftpopen}}}{{{ftp_base}}}/gnupg/gnupg-{{{gnupg1_ver}}}.tar.bz2.sig{{{ftpclose}}} |
|---------------+------------------------+-------------------------+----------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------|
| [[../related_software/libgpg-error/index.org][Libgpg-error]] | {{{libgpg_error_ver}}} | {{{libgpg_error_size}}} | {{{ftpopen}}}{{{ftp_base}}}/libgpg-error/libgpg-error-{{{libgpg_error_ver}}}.tar.bz2{{{ftpclose}}} | {{{ftpopen}}}{{{ftp_base}}}/libgpg-error/libgpg-error-{{{libgpg_error_ver}}}.tar.bz2.sig{{{ftpclose}}} |
@@ -100,13 +101,13 @@
|---------+--------------------+---------------------------------------------|
| | <18> | |
| Windows | [[http://gpg4win.org/download.html][Gpg4win]] | Installers for /GnuPG stable/ |
- | | --- | Simple installer for /GnuPG modern/ |
+ | | {{{ftpopen}}}{{{ftp_base}}}/binary/gnupg-w32-{{{gnupg21_w32_ver}}}.exe{{{ftpclose}}} {{{ftpopen}}}{{{ftp_base}}}/binary/gnupg-w32-{{{gnupg21_w32_ver}}}.exe.sig{{{ftpcloseS}}} | Simple installer for /GnuPG modern/ |
| | {{{ftpopen}}}{{{ftp_base}}}/binary/gnupg-w32cli-{{{gnupg1_w32cli_ver}}}.exe{{{ftpclose}}} {{{ftpopen}}}{{{ftp_base}}}/binary/gnupg-w32cli-{{{gnupg1_w32cli_ver}}}.exe.sig{{{ftpcloseS}}} | Simple installer for /GnuPG classic/ |
| OS X | [[http://gpgtools.org][Mac GPG]] | Installer from the gpgtools project |
| Debian | [[https://www.debian.org][Debian site]] | GnuPG stable and classic are part of Debian |
| RPM | [[http://rpmfind.net/][rpmfind]] | RPM packages for different OS |
| Android | [[https://guardianproject.info/code/gnupg/][Guardian project]] | Provides a GnuPG 2.1 framework |
- | VMS | [[http://www.antinode.info/dec/sw/gnupg.html][antinode.info]] | A port of GnupG to OpenVMS |
+ | VMS | [[http://www.antinode.info/dec/sw/gnupg.html][antinode.info]] | A port of GnuPG to OpenVMS |
| RISC OS | [[http://www.sbellon.de/gnupg.html][home page]] | Sources and binaries for RISC OS |
|---------+--------------------+---------------------------------------------|
diff --git a/web/download/integrity_check.org b/web/download/integrity_check.org
index 8bff4ed..7d70c7c 100644
--- a/web/download/integrity_check.org
+++ b/web/download/integrity_check.org
@@ -1,6 +1,7 @@
#+TITLE: GnuPG - Integrity Check
#+STARTUP: showall
#+SETUPFILE: "../share/setup.inc"
+#+OPTIONS: ^:{}
* Integrity Check
#+index: integrity check
@@ -56,9 +57,10 @@
For your convenience, all SHA-1 check-sums available for software
that can be downloaded from [[ftp://ftp.gnupg.org/][our site]], have been gathered below.
-# {{{gnupg21_sha1}}} gnupg-{{{gnupg21_ver}}}.tar.bz2
{{{begin_chksum}}}
{{{gnupg_sha1}}} gnupg-{{{gnupg_ver}}}.tar.bz2
+ {{{gnupg21_sha1}}} gnupg-{{{gnupg21_ver}}}.tar.bz2
+ {{{gnupg21_w32_sha1}}} gnupg-w32-{{{gnupg21_w32_ver}}}.exe
{{{gnupg1_sha1}}} gnupg-{{{gnupg1_ver}}}.tar.bz2
{{{gnupg1_sha1_gz}}} gnupg-{{{gnupg1_ver}}}.tar.gz
{{{gnupg1_patch_sha1}}} gnupg-{{{gnupg1_patch_ver}}}.diff.bz2
diff --git a/web/index.org b/web/index.org
index 5027f49..701dc84 100644
--- a/web/index.org
+++ b/web/index.org
@@ -52,6 +52,13 @@ all [[file:news.org][news of previous years]] is also available.
# point or paste the [[news.en.rss][RSS file]] into your aggregator.
+** GnuPG 2.1.0 with ECC support released (2014-11-06)
+
+This is the first released of the new /modern/ branch of GnuPG. It
+features a lot of new things including support for ECC. Read more at
+the [[file:faq/whats-new-in-2.1.org][feature overview]] page and in the [[http://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000358.html][announcement]] mail.
+
+
** A beta for GnuPG 2.1.0 released (2014-10-03)
A beta release for the forthcoming GnuPG 2.1 version is now
diff --git a/web/swdb.mac b/web/swdb.mac
index 5911436..1279c6d 100644
--- a/web/swdb.mac
+++ b/web/swdb.mac
@@ -19,6 +19,12 @@
#
#+macro: gnupg21_ver 2.1.0
#+macro: gnupg21_branch master
+#+macro: gnupg21_size 3039k
+#+macro: gnupg21_sha1 2fcd0ca6889ef6cb59e3275e8411f8b7778c2f33
+#
+#+macro: gnupg21_w32_ver 2.1.0_20141105
+#+macro: gnupg21_w32_size 6225k
+#+macro: gnupg21_w32_sha1 9907cb6509a0e63331b27a92e25c1ef956caaf3b
#
@@ -115,8 +121,8 @@
#
# GpgEX
#
-#+macro: gpgex_ver 1.0.1
-#+macro: gpgex_sha1 eb54767fd8e3728e8d14c7c158e0841b67c714a6
+#+macro: gpgex_ver 1.0.2
+#+macro: gpgex_sha1 8892dafc405255731b82a0c299960a5da59d3191
#
commit 8bb197809ffedf711ac08332071e9fb39d1ddbbb
Author: Werner Koch <wk at gnupg.org>
Date: Tue Nov 4 20:54:24 2014 +0100
faq: Finished the "What's new in 2.1" page.
diff --git a/web/faq/whats-new-in-2.1.org b/web/faq/whats-new-in-2.1.org
index 4fc28bb..ae1633c 100644
--- a/web/faq/whats-new-in-2.1.org
+++ b/web/faq/whats-new-in-2.1.org
@@ -1,95 +1,697 @@
#+TITLE: GnuPG - What’s new in 2.1
#+STARTUP: showall indent
#+SETUPFILE: "share/setup.inc"
+#+DATE: 2014-11-04
+#+macro: more @@html:<a href="#$1"><span class="morelink"> ⇒</a>@@
+
+#+BEGIN_ASCII
+A possibly revised version of this article can be found at:
+https://gnupg.org/faq/whats-new-in-2.1.html
+#+END_ASCII
* What’s new in GnuPG 2.1
GnuPG version 2.1 comes with a bag of new features which changes some
things old-timers are used to. This page explains the more important
-ones. It expects that the user is somewhat familiar with GnuPG
-version 2.0 and is aware that GnuPG consists of /gpg/, /gpgsm/, and
-/gpg-agent/ as its main components.
+ones. It expects that the reader is familiar with GnuPG version 2.0
+and aware that GnuPG consists of /gpg/, /gpgsm/, and /gpg-agent/ as
+its main components.
+#+html: <div style="width: 80%">
- The file /secring.gpg/ is not anymore used to store the secret keys.
- Merging of secret keys is now supported.
+ Merging of secret keys is now supported.{{{more(nosecring)}}}
-- All support for /PGP-2 keys/ has been removed for security reasons.
+- All support for /PGP-2 keys/ has been removed for security
+ reasons.{{{more(nopgp2)}}}
-- Support for /Elliptic Curve Cryptography/ (ECC) is now available
+- The standard key generation interface is now much leaner. This will
+ help a new user to quickly generate a suitable
+ key.{{{more(leangenkey)}}}
-- The standard key generation interface is much leaner now to help the
- new user creating a suitable key.
+- Support for /Elliptic Curve Cryptography/ (ECC) is now
+ available.{{{more(ecc)}}}
- Commands to create and sign keys from the command line without any
- extra prompts are now available.
+ extra prompts are now available.{{{more(quickgen)}}}
-- The Pinentry dialog may now show two fields to enter a new
- passphrase and a confirmation of it.
+- The Pinentry may now show the new passphrase entry and the
+ passphrase confirmation entry in one dialog.{{{more(pinentry)}}}
- There is no more need to manually start the gpg-agent. It is now
- started by any part of GnuPG as needed.
+ started by any part of GnuPG as needed.{{{more(autostart)}}}
- Problems with importing keys with the same long key id have been
- addressed.
+ addressed.{{{more(longkid)}}}
- The /dirmngr/ is now part of GnuPG proper and also takes care of
- accessing keyserver.
+ accessing keyserver.{{{more(dirmngr)}}}
-- Keyserver pools are now handled in a smarter way.
+- Keyserver pools are now handled in a smarter
+ way.{{{more(keyserver)}}}
- A new format for locally storing the public keys is now used. This
- considerable speeds up operations on large keyrings.
+ considerable speeds up operations on large
+ keyrings.{{{more(keybox)}}}
-- /Revocation certificates/ are now created by default.
+- /Revocation certificates/ are now created by
+ default.{{{more(autorev)}}}
- Card support has been updated, new readers and token types are
- supported.
+ supported.{{{more(scd)}}}
- The format of the key listing has been changed to better identify
- the properties of a key.
+ the properties of a key.{{{more(keylist)}}}
- The gpg-agent may now be used on Windows as /pageant/ replacement
for /putty/ in the same way it is used for years on Unix as
- /ssh-agent/ replacement.
+ /ssh-agent/ replacement.{{{more(pageant)}}}
- Creation of X.509 certificates has been improved. It is now also
possible to export them directly in PKCS#8 and PEM format for use on
- TLS servers.
+ TLS servers.{{{more(x509)}}}
+
+- The scripts to create a Windows installer are now part of
+ GnuPG.{{{more(w32inst)}}}
+
+#+html: </div>
+
+Now for the detailed description of these new features:
+
+** Removal of the secret keyring
+:PROPERTIES:
+:CUSTOM_ID: nosecring
+:END:
+
+gpg used to keep the public key pairs in two files: =pubring.gpg= and
+=secring.gpg=. The only difference is that secring stored in addition
+to the public part also the private part of the key pair. The secret
+keyring thus contained only the keys for which a private key is
+available, that is the user’s key. It required a lot of code to keep
+both versions of the key in sync and led to sometimes surprising
+inconsistencies.
+
+The design of GnuPG-2 demands that only the gpg-agent has control over
+the private parts of the keys and the actual encryption engine (gpg or
+gpgsm) does not know about the private key but care only about session
+keys and keys for symmetric encryption. This has been implemented
+about 10 years ago for /gpgsm/ (the S/MIME part of GnuPG). However,
+/gpg/ (the OpenPGP part) used the gpg-agent only as passphrase entry
+and cache device but handles the private key itself.
+
+With GnuPG 2.1 this changed and /gpg/ now also delegates all private
+key operations to the gpg-agent. Thus there is no more code in the
+/gpg/ binary for handling private keys. En passant this allows the
+long time requested “merging of secret keys” and several other
+advanced key management techniques.
+
+To ease the migration to the no-secring method, /gpg/ detects the
+presence of a =secring.gpg= and converts the keys on-the-fly to the
+the key store of /gpg-agent/ (this is the =private-keys-v1.d=
+directory below the GnuPG home directory (=~/.gnupg=)). This is done
+only once and an existing =secring.gpg= is then not anymore touched by
+/gpg/. This allows co-existence of older GnuPG versions with GnuPG
+2.1. However, any change to the private keys using the new /gpg/ will
+not show up when using pre-2.1 versions of GnuPG and vice versa.
+
+Note that the command =--export-secret-keys= still creates an OpenPGP
+compliant file with the secret keys. This is achieved by asking
+/gpg-agent/ to convert a key and return it in the OpenPGP protected
+format. The export operation requires that the passphrase for the key
+is entered so that /gpg-agent/ is able to change the protection from
+its internal format to the OpenPGP required format.
-- The scripts to create a Windows installer is now part of GnuPG.
+** Removal of PGP-2 support
+:PROPERTIES:
+:CUSTOM_ID: nopgp2
+:END:
+
+Some algorithms and parts of the protocols as used by the 20 years old
+[[https://en.wikipedia.org/wiki/Pretty_Good_Privacy][PGP-2]] software are meanwhile considered unsafe. In particular the
+baked in use of the [[https://en.wikipedia.org/wiki/MD5][MD5]] hash algorithm limits the security of PGP-2
+keys to non-acceptable rate. Technically those PGP-2 keys are called
+version 3 keys (v3) and are easily identified by a shorter fingerprint
+which is commonly presented as 16 separate double hex digits.
+
+With GnuPG 2.1 all support for those keys has gone. If they are in an
+existing keyring they will eventually be removed. If GnuPG encounters
+such a key on import it will not be imported due to the not anymore
+implemented v3 key format. Removing the v3 key support also reduces
+complexity of the code and is thus better than to keep on handling
+them with a specific error message.
+
+There is one use case where PGP-2 keys may still be required: For
+existing encrypted data. We suggest to keep a version of GnuPG 1.4
+around which still has support for these keys (it might be required to
+use the =--allow-weak-digest-algos= option). A better solution is to
+re-encrypt the data using a modern key.
-** Removal of the secret keyring.
+** Leaner key generation interface
+:PROPERTIES:
+:CUSTOM_ID: leangenkey
+:END:
-Explain...
+This is best shown with an example:
-** Removal of PGP-2 support
+#+begin_example
+$ gpg2 --gen-key
+gpg (GnuPG) 2.1.0; Copyright (C) 2014 Free Software Foundation, Inc.
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
-** Support for ECC
+gpg: keybox '/home/foo/.gnupg/pubring.kbx' created
+Note: Use "gpg --full-gen-key" for a full featured key generation dialog.
-** Leaner key generation interface
+GnuPG needs to construct a user ID to identify your key.
+
+Real name: Glenn Greenwald
+Email address: glenn at example.org
+You selected this USER-ID:
+ "Glenn Greenwald <glenn at example.org>"
+
+Change (N)ame, (E)mail, or (O)kay/(Q)uit? o
+[...]
+pub rsa2048/68FD0088 2014-11-03
+ Key fingerprint = 0290 5ABF 17C7 81FB C390 9B00 636A 1BBD 68FD 0088
+uid [ultimate] Glenn Greenwald <glenn at example.org>
+sub rsa2048/84439DCD 2014-11-03
+#+end_example
+
+Thus only the name and the mail address are required. For all other
+parameters the default values are used. Many graphical frontends
+works in the same way. Note that /gpg/ prints a hint for the old time
+gpg users on how to get the full option menu.
+
+** Support for ECC
+:PROPERTIES:
+:CUSTOM_ID: ecc
+:END:
+
+GnuPG now support Elliptic Curve keys for public key encryption. This
+is defined in [[https://rfc-editor.org/info/rfc6637][RFC-6637]]. Because there is no other mainstream OpenPGP
+implementation yet available which supports ECC, the use of such keys
+is still very limited. Thus GnuPG 2.1 currently hides the options to
+create an ECC key.
+
+For those who want to experiment with ECC or already want to prepare a
+key for future use, the command =--gen-full-key= along with the option
+=--expert= is the enabler:
+
+#+begin_example
+$ gpg2 --expert --full-gen-key
+gpg (GnuPG) 2.1.0; Copyright (C) 2014 Free Software Foundation, Inc.
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
+
+Please select what kind of key you want:
+ (1) RSA and RSA (default)
+ (2) DSA and Elgamal
+ (3) DSA (sign only)
+ (4) RSA (sign only)
+ (7) DSA (set your own capabilities)
+ (8) RSA (set your own capabilities)
+ (9) ECC and ECC
+ (10) ECC (sign only)
+ (11) ECC (set your own capabilities)
+Your selection? 9
+Please select which elliptic curve you want:
+ (2) NIST P-256
+ (3) NIST P-384
+ (4) NIST P-521
+ (5) Brainpool P-256
+ (6) Brainpool P-384
+ (7) Brainpool P-512
+Your selection? 2
+Please specify how long the key should be valid.
+ 0 = key does not expire
+ <n> = key expires in n days
+ <n>w = key expires in n weeks
+ <n>m = key expires in n months
+ <n>y = key expires in n years
+Key is valid for? (0)
+Key does not expire at all
+Is this correct? (y/N) y
+
+GnuPG needs to construct a user ID to identify your key.
+
+Real name: Edward Snowden
+Email address: edward at example.org
+Comment:
+You selected this USER-ID:
+ "Edward Snowden <edward at example.org>"
+
+Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
+[...]
+pub nistp256/382660E3 2014-11-03
+ Key fingerprint = E630 27CF 3D68 22A7 6FF2 093E D179 9E72 3826 60E3
+uid [ultimate] Edward Snowden <edward at example.org>
+sub nistp256/48C9A997 2014-11-03 nistp256
+#+end_example
+
+In this example we created a primary ECC key for signing and an subkey
+for encryption. For both we use the NIST P-256 curve. The key may
+now be used in the same way as any other key. It is possible to add
+an RSA subkey or one can create an RSA or DSA main key and add an ECC
+subkey for signing or encryption. Note that the list of offered
+curves depends on the installed Libgcrypt version.
+
+For many people the NIST and also the Brainpool curves have an
+doubtful origin and thus the plan for GnuPG is to use Bernstein’s
+[[http://cr.yp.to/ecdh/curve25519-20060209.pdf][Curve 25519]] as default. GnuPG 2.1.0 already comes with support for
+signing keys using the [[http://dx.doi.org/10.1007/s13389-012-0027-1][Ed25519]] variant of this curve. This has not
+yet been standardized by the IETF (i.e. there is no RFC) but we won’t
+wait any longer and go ahead using the proposed format for this
+signing algorithm. The format for an encryption key has not yet been
+finalized and will be added to GnuPG in one of the next point
+releases. Recall that an encryption subkey can be added to a key at
+any time. If you want to create a signing key you may do it this way:
+
+#+begin_example
+$ gpg2 --expert --full-gen-key
+gpg (GnuPG) 2.1.0; Copyright (C) 2014 Free Software Foundation, Inc.
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
+
+Please select what kind of key you want:
+ (1) RSA and RSA (default)
+ (2) DSA and Elgamal
+ (3) DSA (sign only)
+ (4) RSA (sign only)
+ (7) DSA (set your own capabilities)
+ (8) RSA (set your own capabilities)
+ (9) ECC and ECC
+ (10) ECC (sign only)
+ (11) ECC (set your own capabilities)
+Your selection? 10
+Please select which elliptic curve you want:
+ (1) Curve 25519
+ (2) NIST P-256
+ (3) NIST P-384
+ (4) NIST P-521
+ (5) Brainpool P-256
+ (6) Brainpool P-384
+ (7) Brainpool P-512
+Your selection? 1
+gpg: WARNING: Curve25519 is not yet part of the OpenPGP standard.
+Use this curve anyway? (y/N) y
+Please specify how long the key should be valid.
+ 0 = key does not expire
+ <n> = key expires in n days
+ <n>w = key expires in n weeks
+ <n>m = key expires in n months
+ <n>y = key expires in n years
+Key is valid for? (0)
+Key does not expire at all
+Is this correct? (y/N) y
+
+GnuPG needs to construct a user ID to identify your key.
+
+Real name: Laura Poitras
+Email address: laura at example.org
+Comment:
+You selected this USER-ID:
+ "Laura Poitras <laura at example.org>"
+
+Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
+[...]
+pub ed25519/5C1AFC2A 2014-11-03
+ Key fingerprint = ED85 4D98 5D8F 502F C6C5 FFB2 AA81 319E 5C1A FC2A
+uid [ultimate] Laura Poitras <laura at example.org>
+#+end_example
+
+Support for ECC keys is available only on some keyservers but it is
+expected that this will be fixed over the next few months.
** Quick generate and sign commands
+:PROPERTIES:
+:CUSTOM_ID: quickgen
+:END:
+
+Sometimes it is useful to use only command line options without any
+parameter file or interactive prompts for generating a key or to sign a
+key. This can now be accomplished with a few new commands:
+
+#+begin_example
+$ gpg2 --batch --quick-gen-key 'Daniel Ellsberg <ellsberg at example.org>'
+gpg: key 911B90A9 marked as ultimately trusted
+#+end_example
+
+If a key with that user id already exists, gpg bails out with an error
+message. You can force creation using the option =--yes=. If you
+want some more control, you may not use =--batch= and gpg will ask for
+confirmation and show the resulting key:
+
+#+begin_example
+$ gpg2 --quick-gen-key 'Daniel Ellsberg <ellsberg at example.org>'
+About to create a key for:
+ "Daniel Ellsberg <ellsberg at example.org>"
+
+Continue? (Y/n) y
+gpg: A key for "Daniel Ellsberg <ellsberg at example.org>" already exists
+Create anyway? (y/N) y
+gpg: creating anyway
+[...]
+pub rsa2048/BD19AC1C 2014-11-04
+ Key fingerprint = 15CB 723E 2000 A1A8 2505 F3B7 CC00 B501 BD19 AC1C
+uid [ultimate] Daniel Ellsberg <ellsberg at example.org>
+sub rsa2048/72A4D018 2014-11-04
+#+end_example
+
+Another common operation is to sign a key. /gpg/ can do this directly
+from the command line by giving the fingerprint of the to-be-signed
+key:
+
+#+begin_example
+$ gpg2 --quick-sign-key '15CB 723E 2000 A1A8 2505 F3B7 CC00 B501 BD19 AC1C'
+
+pub rsa2048/BD19AC1C
+ created: 2014-11-04 expires: never usage: SC
+ trust: ultimate validity: ultimate
+ Primary key fingerprint: 15CB 723E 2000 A1A8 2505 F3B7 CC00 B501 BD19 AC1C
+
+ Daniel Ellsberg <ellsberg at example.org>
+
+#+end_example
+
+In case the key has already been signed, the command prints a note and
+exits with success. In case you want to check that it really worked,
+use ==--check-sigs= as usual:
+
+#+begin_example
+$ gpg2 --check-sigs '15CB 723E 2000 A1A8 2505 F3B7 CC00 B501 BD19 AC1C'
+gpg: checking the trustdb
+gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
+gpg: depth: 0 valid: 6 signed: 1 trust: 0-, 0q, 0n, 0m, 0f, 6u
+pub rsa2048/BD19AC1C 2014-11-04
+uid [ full ] Daniel Ellsberg <ellsberg at example.org>
+sig!3 BD19AC1C 2014-11-04 Daniel Ellsberg <ellsberg at example.org>
+sig! 68FD0088 2014-11-04 Glenn Greenwald <glenn at example.org>
+sub rsa2048/72A4D018 2014-11-04
+sig! BD19AC1C 2014-11-04 Daniel Ellsberg <ellsberg at example.org>
+#+end_example
+
+
+The fingerprint may also be given without the spaces in which case
+there is no need for the quotes. If you want to sign only certain
+user ids of a key, list those user id verbatim after the fingerprint.
+To create a non-exportable key signature, use the command
+=--quick-lsign-key= instead.
** Improved Pinentry support
+:PROPERTIES:
+:CUSTOM_ID: pinentry
+:END:
+
+When using a recent Pinentry module (0.90, GTK+ variant), the
+gpg-agent will not anymore show two separate Pinentry dialogs to enter
+a new passphrase and later to confirm the new passphrase. Instead the
+first dialog also has the confirm/repeat entry and internally checks
+whether they match.
+
+With any Pinentry version the several separate dialogs to inform and
+ask for confirmation about questionable properties of a new passphrase
+(e.g. length, only alpha letters) have been combined into one dialog
+to show all non-asserted constraints at once.
+
+The GTK+ Pinentry does now allow pasting of values into the entries.
+Copying them from the entries is still inhibited on purpose.
+Depending on the system, the option =no-grab= may be required for in
+the =gpg-agent.conf= file to actually make use of the paste feature.
** Auto-start of the gpg-agent
+:PROPERTIES:
+:CUSTOM_ID: autostart
+:END:
+
+The /gpg-agent/ is the central part of the GnuPG system. It takes
+care of all private (secret) keys and if required diverts operations
+to a smartcard or other token. It also provides support for the
+Secure Shell by implementing the ssh-agent protocol.
+
+The classic way to run /gpg-agent/ on Unix systems is by launching it
+at login time and use an environment variable (=GPG_AGENT_INFO=) to
+tell the other GnuPG modules how to connect to the agent. However,
+correctly managing the start up and this environment variable is
+cumbersome so that that an easier method is required. Since GnuPG
+2.0.16 the =--use-standard-socket= option already allowed to start the
+agent on the fly; however the environment variable was still required.
+
+With GnuPG 2.1 the need of =GPG_AGENT_INFO= has been completely
+removed and the variable is ignored. Instead a fixed Unix domain
+socket named =S.gpg-agent= in the GnuPG home directory (by default
+=~/.gnupg=) is used. The agent is also started on demand by all tools
+requiring services from the agent.
+
+If the option =--enable-ssh-support= is used the auto-start mechanism
+does not work because /ssh/ does not know about this mechanism.
+Instead it is required that the environment variable =SSH_AUTH_SOCK=
+is set to the =S.gpg-agent.ssh= socket in the GnuPG home directory.
+Further /gpg-agent/ must be started: Either by using a GnuPG command
+which implicitly starts /gpg-agent/ or by using =gpgconf --launch
+gpg-agent= to explicitly start it if not yet done.
** Duplicate long key id fixes
+:PROPERTIES:
+:CUSTOM_ID: longkid
+:END:
+
+A deficit of the OpenPGP protocol is that signatures carry only a
+limited indication on which public has been used to create a
+signature. Thus a verification engine may only use this “long key id”
+to look up the the key in its own store or from a public keyserver.
+Unfortunately it has now become possible to create a key with a long
+key id matching the key id of another key. Importing a key with a
+long key id already used by another key in gpg’s local key store was
+not possible due to checks done on import. Now, if the “wrong” key
+has been imported first /gpg/ would not allow to later import the
+second “correct” key. This problem has been fixed in 2.1 by allowing
+the import and by doing trial verification against all matching keys.
** Enhanced Dirmngr
+:PROPERTIES:
+:CUSTOM_ID: dirmngr
+:END:
+
+Before version 2.1, /gpg/ used so-called keyserver helpers to access
+the OpenPGP keyservers. A problem with that is that they are short
+living processes which are not able to keep a state. With 2.1, the
+formerly separate package Dirmngr (which was separate due to copyright
+assignment reasons) has been integrated into GnuPG.
+
+In the past /dirmngr/ was only used by /gpgsm/ for X.509 (S/MIME) CRL
+and OCSP handling. Being a proper part of GnuPG /dirmngr/ does now
+also care about accessing OpenPGP keyservers. This make its easier to
+debug problems with the keyservers and to exchange additional
+information about the keyserver between /gpg/ and /dirmngr/. It will
+eventually also be possible to run background tasks to refresh keys.
+
+Although the ability to start /dirmngr/ as a system service is still
+available, this is not anymore recommended and instead /dirmngr/ is
+now by default started on-demand, very similar to /gpg-agent/.
** Better keyserver pool support
+:PROPERTIES:
+:CUSTOM_ID: keyserver
+:END:
+
+For load balancing reasons, keyservers are organized in pools to
+enable instant round-robin DNS assignment of random keyservers. A
+problem with that approach is that the DNS resolver is not aware of
+the state of the keyserver. If a keyserver has gone down or a routing
+problems occurs, /gpg/ and its keyserver helpers were not ware of it
+and would try over and over to use the same, dead, keyserver up until
+the DNS information expires and a the DNS resolver assigned a new
+server from the pool.
+
+The new /dirmngr/ in GnuPG does not use the implicit round-robin of
+the DNS resolver but uses its own DNS look up and keeps an internal
+table of all hosts from the pool along with the encountered aliveness
+state. Thus after a failure (timeout) of a request, /dirmngr/ flags a
+host as dead and randomly selects another one from the pool. After a
+few hours the flag is removed so that the host will be tried again.
+It is also possible to mark a specif host from a pool explicitly as
+dead so that it won’t be used in future. To interact with the
+/dirmngr/ the =gpg-connect-agent= tool is used:
+
+#+begin_example
+$ gpg-connect-agent --dirmngr 'help keyserver' /bye
+$ gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye
+#+end_example
+
+The first command prints a help screen for the keyserver command and
+the second command prints the current host table.
** Faster keyring format
+:PROPERTIES:
+:CUSTOM_ID: keybox
+:END:
+
+The format GnuPG has always used for the public keyring is actually a
+slightly extended version of the on-the-wire format for OpenPGP key
+exchange. This format is quite inflexible to work with when random
+access to keys in the keyring is required. In fact /gpg/ always
+parsed all keys in the keyring until it encountered the desired one.
+With a large keyring (more than a few thousand keys) this could be
+quite slow.
+
+From its very beginning /gpgsm/ has used a different format to store
+public keys (certificates) which we call a /keybox/. That file format
+carries meta information about the stored keys and thus allows
+searching without actually parsing the key and computing fingerprints
+and such. The /keybox/ format has been designed protocol independent
+and with 2.1 support for OpenPGP keys has been added. Random access
+to the keys is now really fast and keyrings with 30000 keys and more
+are now easily possible. That change also enables us to easily
+introduce other storage methods
+
+If no =pubring.gpg= is found, /gpg/ defaults to the new /keybox/
+format and creates a =pubring.kbx= keybox file. If such a keybox file
+already exists, for example due to the use of /gpgsm/, it will also be
+used for OpenPGP keys. However, if a =pubring.gpg= is found and no
+keybox file with OpenPGP keys exists, the old =pubring.gpg= will be
+used. Take care: GnuPG versions before 2.1 will always use the
+=pubring.gpg= file and not know anything about keys stored in the
+keybox file.
+
+To convert an existing =pubring.gpg= file to the keybox format, you
+first rename the file to (for example) =publickeys= so it won’t be
+recognized by any GnuPG version and then you run the command
+
+#+begin_example
+$ gpg2 --import publickeys
+#+end_example
+
+You may then rename the =publickeys= file back so that it can be used
+by older GnuPG versions. Remember that in this case you have two
+independent copies of the public keys.
-** Auto-generated revocation certificates
-** Imporved card support
+** Auto-generated revocation certificates
+:PROPERTIES:
+:CUSTOM_ID: autorev
+:END:
+
+This version creates an ASCII armored revocation certificate for each
+generated keypair and stores that certificate in a file named after
+the fingerprint of the key in the =openpgp-revocs.d= directory below
+the GnuPG home directory. Brief instructions on how to use this
+revocation certificate are put at the top of the file.
+
+** Improved card support
+:PROPERTIES:
+:CUSTOM_ID: scd
+:END:
+
+The /scdaemon/, which is responsible for accessing smardcards and
+other tokens, has received may updates. In particular plugable USB
+readers with a fixed card now work smoothless and similar to standard
+readers. The latest features of the /gnuk/ token are supported. Code
+for the HSM smartcard has been added. More card readers with a PIN
+pad are supported. The internal CCID driver does now also work with
+certain non-auto configuration equipped readers.
** New format for key listings
+:PROPERTIES:
+:CUSTOM_ID: keylist
+:END:
+
+Due to the introduction of ECC keys the old format to list keys was
+not anymore suitable. In particular, the length of an ECC key is
+defined but its expressiveness is limited without the other parameters
+of the curve. The common way to describe an ECC key is by using the
+assigned name of its curve. To allow for a common description
+we now either use the algorithm name with appended key length or use
+the name of the curve:
+
+#+begin_example
+pub 2048D/1E42B367 2007-12-31 [expires: 2018-12-31]
+pub dsa2048/1E42B367 2007-12-31 [expires: 2018-12-31]
+pub ed25519/0AA914C9 2014-10-18
+#+end_example
+
+The first two lines show the same key in the old format and in the new
+format. The third line shows an example of an ECC key using the
+ed25519 curve.
+
+As a further change the validity of a key is now shown by default;
+that is =show-uid-validity= is implicitly used for the
+=--list-options=.
+
+The annotated key listing produced by the =--with-colons= options did
+not change. However a couple of new fields have been added, for
+example if the new option =--with-secret-= is used the “S/N of a token
+field” indicates the presence of a secret key even in a public key
+listing. This option is supported by recent [[https://gnupg.org/related_software/gpgme/][GPGME]] versions and makes
+writing of key manager software easier.
** Support for Putty
+:PROPERTIES:
+:CUSTOM_ID: pageant
+:END:
-** Improved X.509 certificate creation
+On Windows the new option =--enable-putty-support= allows gpg-agent to
+act as a replacement for [[http://www.chiark.greenend.org.uk/~sgtatham/putty/][Putty]]’s authentication agent /Pageant/. It
+is the Windows counterpart for the =--enable-ssh-support= option as
+used on Unix.
-** Included code for a Windows installer
+** Improved X.509 certificate creation
+:PROPERTIES:
+:CUSTOM_ID: x509
+:END:
+
+In addition to an improved certificate signing request menu, it is now
+possible to create a self-signed certificate using the interactive
+menu of /gpgsm/.
+
+In batch mode the certificate creation dialog can now be controlled by
+a parameter file with several new keywords. Such a parameter file
+allows the creation of arbitrary X.509 certificates similar to what
+can be done with /openssl/. It may this be used as the base for a CA
+software. For details see the “CSR and certificate creation” section
+in the manual.
+
+The new commands =--export-secret-key-p8= and --export-secret-key-raw=
+may be used to export a secret key directly in PKCS#8 or PKCS#1
+format. Thus X.509 certificates for TLS use may be managed by /gpgsm/
+and directly exported in a format suitable for OpenSSL based servers.
+
+** Scripts to create a Windows installer
+:PROPERTIES:
+:CUSTOM_ID: w32inst
+:END:
+
+GnuPG now comes with the /speedo/ build system which may be used to
+quickly download and build GnuPG and all its direct dependencies on a
+decent Unix system. See the README file for more instructions.
+
+The very same script may also be used to build a complete NSIS based
+installer for Windows using the mingw-w64 cross-compiler toolchain.
+That installer will feature GnuPG proper, GPA as graphical frontend,
+and GpgEX as a Windows Explorer extension. GnuPG needs to be unpacked
+and from the top source directory you run this command
+
+#+begin_example
+make -f build-aux/speedo.mk w32-installer
+#+end_example
+
+This command downloads all direct dependencies, checks the signatures
+using the GnuPG version from the build system (all Linux distros
+feature a suitable GnuPG tool), builds everything from source, and uses
+NSIS to create the installer. Although this sounds easy, some
+experience in setting up a development machine is still required.
+Some versions of the toolchain exhibit bugs and thus your mileage may
+vary. Support for keyserver access over TLS is currently not
+available but will be added with one of the next point releases.
+
+
+
+#+BEGIN_ASCII
+# Copyright 2014 The GnuPG Project.
+# This work is licensed under the Creative Commons
+# Attribution-ShareAlike 4.0 International License. To view a copy of
+# this license, visit http://creativecommons.org/licenses/by-sa/4.0/
+# or send a letter to Creative Commons, PO Box 1866, Mountain View, CA
+# 94042, USA.
+#
+# The canonical source for this article can be found in the gnupg-doc
+# git repository as web/faq/whats-new-in-2.1.org.
+#+END_ASCII
diff --git a/web/share/site.css b/web/share/site.css
index 4e056c6..382ffcb 100644
--- a/web/share/site.css
+++ b/web/share/site.css
@@ -387,6 +387,17 @@ div.outline-text-3 {
}
*/
+.morelink {
+ font-size: smaller;
+ font-variant: normal;
+ font-weight: normal;
+ text-decoration: none;
+}
+
+.morelink:after {
+ content: "{more}";
+}
+
#cpyright {
padding-top: 4em;
commit eacffee435910dc5c2199f25a5de8bcee2d09467
Author: Werner Koch <wk at gnupg.org>
Date: Tue Nov 4 20:53:02 2014 +0100
web: Add pointer to an Android version to the download page.
Also remove the dead link to Unix Security software.
diff --git a/web/download/index.org b/web/download/index.org
index c07d7b9..a9dfbc5 100644
--- a/web/download/index.org
+++ b/web/download/index.org
@@ -96,19 +96,19 @@
also that some of them apply security patches on top of the
standard versions but keep the original version number.
- | OS | Where | Description |
- |---------+-----------------+---------------------------------------------|
- | | <15> | |
- | Windows | [[http://gpg4win.org/download.html][Gpg4win]] | Installers for /GnuPG stable/ |
- | | --- | Simple installer for /GnuPG modern/ |
+ | OS | Where | Description |
+ |---------+--------------------+---------------------------------------------|
+ | | <18> | |
+ | Windows | [[http://gpg4win.org/download.html][Gpg4win]] | Installers for /GnuPG stable/ |
+ | | --- | Simple installer for /GnuPG modern/ |
| | {{{ftpopen}}}{{{ftp_base}}}/binary/gnupg-w32cli-{{{gnupg1_w32cli_ver}}}.exe{{{ftpclose}}} {{{ftpopen}}}{{{ftp_base}}}/binary/gnupg-w32cli-{{{gnupg1_w32cli_ver}}}.exe.sig{{{ftpcloseS}}} | Simple installer for /GnuPG classic/ |
- | OS X | [[http://gpgtools.org][Mac GPG]] | Installer from the gpgtools project |
- | Debian | [[https://www.debian.org][Debian site]] | GnuPG stable and classic are part of Debian |
- | RPM | [[http://rpmfind.net/][rpmfind]] | RPM packages for different OS |
- | Unix | [[http://gnupg.unixsecurity.com.br][Unix Security]] | Packages for some other POSIX systems |
- | VMS | [[http://www.antinode.info/dec/sw/gnupg.html][antinode.info]] | A port of GnupG to OpenVMS |
- | RISC OS | [[http://www.sbellon.de/gnupg.html][home page]] | Sources and binaries for RISC OS |
- |---------+-----------------+---------------------------------------------|
+ | OS X | [[http://gpgtools.org][Mac GPG]] | Installer from the gpgtools project |
+ | Debian | [[https://www.debian.org][Debian site]] | GnuPG stable and classic are part of Debian |
+ | RPM | [[http://rpmfind.net/][rpmfind]] | RPM packages for different OS |
+ | Android | [[https://guardianproject.info/code/gnupg/][Guardian project]] | Provides a GnuPG 2.1 framework |
+ | VMS | [[http://www.antinode.info/dec/sw/gnupg.html][antinode.info]] | A port of GnupG to OpenVMS |
+ | RISC OS | [[http://www.sbellon.de/gnupg.html][home page]] | Sources and binaries for RISC OS |
+ |---------+--------------------+---------------------------------------------|
# eof #
commit 89f1a299bb6f4e0f3ef9e513aca88e67aa6b8655
Author: Werner Koch <wk at gnupg.org>
Date: Mon Nov 3 17:01:10 2014 +0100
web: Use standard colors for the links for easier reading.
diff --git a/web/share/site.css b/web/share/site.css
index c856a6b..4e056c6 100644
--- a/web/share/site.css
+++ b/web/share/site.css
@@ -52,7 +52,7 @@ h3:first-letter {
*/
a:link {
- color: #784c6c;
+/* color: #784c6c;*/
font-weight: bold;
text-decoration: none;
}
@@ -64,7 +64,7 @@ a:hover {
}
a:visited {
- color: #5c6064;
+/* color: #5c6064; */
font-weight: bold;
text-decoration: none;
}
-----------------------------------------------------------------------
Summary of changes:
web/documentation/manuals.org | 5 +-
web/download/index.org | 27 +-
web/download/integrity_check.org | 4 +-
web/faq/whats-new-in-2.1.org | 664 ++++++++++++++++++++++++++++++++++++--
web/index.org | 7 +
web/share/site.css | 15 +-
web/swdb.mac | 10 +-
7 files changed, 681 insertions(+), 51 deletions(-)
hooks/post-receive
--
The GnuPG website and other docs
http://git.gnupg.org
More information about the Gnupg-commits
mailing list