[git] gnupg-doc - branch, master, updated. 9d07f037eb8dbbb70f22289f458c077331dd6264
by Werner Koch
cvs at cvs.gnupg.org
Thu Jul 14 18:52:52 CEST 2016
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 9d07f037eb8dbbb70f22289f458c077331dd6264 (commit)
via 019c350ca36b9d6a2a1eefbc4c7b54f41d753f65 (commit)
from 993149b9b8f1e3b5bbcd928044bd52f124b822d8 (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 9d07f037eb8dbbb70f22289f458c077331dd6264
Author: Werner Koch <wk at gnupg.org>
Date: Thu Jul 14 18:48:03 2016 +0200
faq: Update whats-new-in.2.1
diff --git a/web/faq/whats-new-in-2.1.org b/web/faq/whats-new-in-2.1.org
index 2bf6da0..b4782d4 100644
--- a/web/faq/whats-new-in-2.1.org
+++ b/web/faq/whats-new-in-2.1.org
@@ -1,7 +1,7 @@
#+TITLE: GnuPG - What’s new in 2.1
#+STARTUP: showall indent
#+SETUPFILE: "share/setup.inc"
-#+DATE: 2016-01-14
+#+DATE: 2016-07-14
#+macro: more @@html:<a href="#$1"><span class="morelink"> ⇒</a>@@
#+BEGIN_ASCII
@@ -62,6 +62,12 @@ its main components.
- The format of the key listing has been changed to better identify
the properties of a key.{{{more(keylist)}}}
+- A file with the recipient’s key may now be used
+ directly. {{{more(option_f)}}}
+
+- Gpg can be used to filter out parts of a key.
+ {{{more(importexportfilter)}}}
+
- 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.{{{more(pageant)}}}
@@ -77,7 +83,9 @@ its main components.
#+html: </div>
-Now for the detailed description of these new features:
+Now for the detailed description of these new features. Note that the
+examples assume that that /gpg/ is installed as /gpg/. Your
+installation may have it installed under the name /gpg2/.
** Removal of the secret keyring
:PROPERTIES:
@@ -155,7 +163,7 @@ re-encrypt the data using a modern key.
This is best shown with an example:
#+begin_example
-$ gpg2 --gen-key
+$ gpg --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.
@@ -199,7 +207,7 @@ key for future use, the command =--full-gen-key= along with the option
=--expert= is the enabler:
#+begin_example
-$ gpg2 --expert --full-gen-key
+$ gpg --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.
@@ -268,7 +276,7 @@ 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 --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.
@@ -333,7 +341,7 @@ 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 --batch --quick-gen-key 'Daniel Ellsberg <ellsberg at example.org>'
gpg: key 911B90A9 marked as ultimately trusted
#+end_example
@@ -343,7 +351,7 @@ 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>'
+$ gpg --quick-gen-key 'Daniel Ellsberg <ellsberg at example.org>'
About to create a key for:
"Daniel Ellsberg <ellsberg at example.org>"
@@ -363,7 +371,7 @@ 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'
+$ gpg --quick-sign-key '15CB 723E 2000 A1A8 2505 F3B7 CC00 B501 BD19 AC1C'
pub rsa2048/BD19AC1C
created: 2014-11-04 expires: never usage: SC
@@ -379,7 +387,7 @@ 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 --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
@@ -402,11 +410,11 @@ Since version 2.1.4 it possible to directly add another user id to an
existing key:
#+begin_example
-$ gpg2 -k 8CFDE12197965A9A
+$ gpg -k 8CFDE12197965A9A
pub ed25519/8CFDE12197965A9A 2014-08-19
uid [ unknown] EdDSA sample key 1
-$ gpg2 --quick-adduid 8CFDE12197965A9A 'Sample 2 <me at example.org>'
-$ gpg2 -k 8CFDE12197965A9A
+$ gpg --quick-adduid 8CFDE12197965A9A 'Sample 2 <me at example.org>'
+$ gpg -k 8CFDE12197965A9A
pub ed25519/8CFDE12197965A9A 2014-08-19
uid [ unknown] Sample 2 <me at example.org>
uid [ unknown] EdDSA sample key 1
@@ -434,12 +442,12 @@ Since version 2.1.14 it possible to revoke a user id on an existing
key:
#+begin_example
-$ gpg2 -k 8CFDE12197965A9A
+$ gpg -k 8CFDE12197965A9A
pub ed25519/8CFDE12197965A9A 2014-08-19
uid [ unknown] Sample 2 <me at example.org>
uid [ unknown] EdDSA sample key 1
-$ gpg2 --quick-revuid 8CFDE12197965A9A 'EdDSA sample key 1'
-$ gpg2 -k 8CFDE12197965A9A
+$ gpg --quick-revuid 8CFDE12197965A9A 'EdDSA sample key 1'
+$ gpg -k 8CFDE12197965A9A
pub ed25519/8CFDE12197965A9A 2014-08-19
uid [ unknown] Sample 2 <me at example.org>
#+end_example
@@ -610,8 +618,8 @@ then run import, and finally restore the ownertrust values:
$ cd ~/.gnupg
$ gpg --export-ownertrust >otrust.lst
$ mv pubring.gpg publickeys
-$ gpg2 --import-options import-local-sigs --import publickeys
-$ gpg2 --import-ownertrust otrust.lst
+$ gpg --import-options import-local-sigs --import publickeys
+$ gpg --import-ownertrust otrust.lst
#+end_example
You may then rename the =publickeys= file back so that it can be used
@@ -687,6 +695,57 @@ 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.
+** Recipient key from file
+:PROPERTIES:
+:CUSTOM_ID: option_f
+:END:
+
+Since version 2.1.14 it is possible to specify the recipient’s key by
+providing a file with that key. This done with the new options
+=--recipient-file= (or short =-f=) and =--hidden-recipient-file= (or
+short =-F=). The file must containing exactly one key in binary or
+armored format. All keys specified with those options are always
+considered fully valid. These option may be mixed with the regular
+options to specify a key. Along with the new convenience option
+=--no-keyring= it is now possible to encrypt data without maintaining
+a local keyring.
+
+** Using gpg as a filter
+:PROPERTIES:
+:CUSTOM_ID: importexportfilter
+:END:
+
+Since version 2.1.14 the export and import options have been enhanced
+to allow the use of /gpg/ to modify a key without first stroing it in
+the keyring. For example:
+
+#+begin_example
+$ gpg --import-options import-minimal,import-export \
+ --output smallkey.gpg --import key.gpg
+#+end_example
+
+copies the keys in =keys.gpg= to =smallkey.gpg= while also removing
+all key signatures except for the latest self-signatures. This can
+even be further restricted to copy only a specific user ID to the
+output file:
+
+#+begin_example
+$ gpg --import-options import-minimal,import-export \
+ --import-filter keepuid='mbox = foo at example.org' \
+ --output smallkey.gpg --import key.gpg
+#+end_example
+
+Here the new =--import-filter= option is used to remove all user IDs
+except for those which have the mail address “foo at example.org”. The
+same is also possible while exporting a key:
+
+#+begin_example
+$ gpg --export-filter keepuid='mbox = me at example.org' \
+ --armor --export 8CFDE12197965A9A >smallkey.asc
+#+end_example
+
+
+
** Support for Putty
:PROPERTIES:
:CUSTOM_ID: pageant
commit 019c350ca36b9d6a2a1eefbc4c7b54f41d753f65
Author: Werner Koch <wk at gnupg.org>
Date: Thu Jul 14 18:04:22 2016 +0200
swdb,web: Several releases
diff --git a/web/index.org b/web/index.org
index ab14258..b8834be 100644
--- a/web/index.org
+++ b/web/index.org
@@ -78,6 +78,17 @@ The latest release news:\\
# GnuPG's latest news are available as [[http://feedvalidator.org/check.cgi?url%3Dhttps://www.gnupg.org/news.en.rss][RSS 2.0 compliant]] feed. Just
# point or paste the [[news.en.rss][RSS file]] into your aggregator.
+** GnuPG 2.1.14 released (2016-07-14)
+
+A new version of the /modern/ branch of GnuPG has been released.
+Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000393.html][announcement mail]] for details.
+
+** Libgcrypt 1.7.2 released (2016-07-14)
+
+We are pleased to announce the availability of Libgcrypt version
+1.7.2. This is a maintenance release for the stable version of
+[[file:related_software/libgcrypt/index.org][Libgcrypt]] with a few bug fixes. [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000392.html][{more}]]
+
** GnuPG 2.1.13 released (2016-06-16)
A new version of the /modern/ branch of GnuPG has been released.
diff --git a/web/swdb.mac b/web/swdb.mac
index 44cf687..e2b2988 100644
--- a/web/swdb.mac
+++ b/web/swdb.mac
@@ -21,18 +21,17 @@
#
# GnuPG-2.1
#
-#+macro: gnupg21_ver 2.1.13
-#+macro: gnupg21_date 2016-06-16
-#+macro: gnupg21_branch STABLE-BRANCH-2-2
-#+macro: gnupg21_size 5415k
-#+macro: gnupg21_sha1 6ec1ae6db7815fdbd4151fb6b0b7197b65b05d1f
-#+macro: gnupg21_sha2 4f9d83a6221daa60130fa79f0b1d37d6c20fffdd0320b640c7a597c5b6219675
+#+macro: gnupg21_ver 2.1.14
+#+macro: gnupg21_date 2016-07-14
+#+macro: gnupg21_size 5572k
+#+macro: gnupg21_sha1 bc7609a3a0daf0ed0efb22f77b43e82f28e20e34
+#+macro: gnupg21_sha2 9450dee9693b6a12bf0c374dae77b66c30f69ff8f35fc9266ab8dd76998eba42
#
-#+macro: gnupg21_w32_ver 2.1.13_20160616
-#+macro: gnupg21_w32_date 2016-06-16
-#+macro: gnupg21_w32_size 3527k
-#+macro: gnupg21_w32_sha1 2debd757534d777bb9c69c18f9492e9a9e5a3a72 gnupg-w32-2.1.13_20160616.exe
-#+macro: gnupg21_w32_sha2 c868b7fadd5907bb598b11490e0214ce2f11340609bb5829e0d9b0875684d876 gnupg-w32-2.1.13_20160616.exe
+#+macro: gnupg21_w32_ver 2.1.14_20160714
+#+macro: gnupg21_w32_date 2016-07-14
+#+macro: gnupg21_w32_size 3576k
+#+macro: gnupg21_w32_sha1 8871e1b596a208403c7240498fa3d83c33ced4b2
+#+macro: gnupg21_w32_sha2 43ac527c85cc2651d4c96fa7c104caadf303ae88dff3cf8ec27f98ef76fa2d89
@@ -83,11 +82,11 @@
#
# LIBGCRYPT
#
-#+macro: libgcrypt_ver 1.7.1
-#+macro: libgcrypt_date 2016-06-15
-#+macro: libgcrypt_size 2777k
-#+macro: libgcrypt_sha1 b688add52b622bb96bbd823ba21aa05a116d442f
-#+macro: libgcrypt_sha2 450d9cfcbf1611c64dbe3bd04b627b83379ef89f11406d94c8bba305e36d7a95
+#+macro: libgcrypt_ver 1.7.2
+#+macro: libgcrypt_date 2016-07-14
+#+macro: libgcrypt_size 2778k
+#+macro: libgcrypt_sha1 85a6a936bcab4c3c05f5efbf6ce847f23d35c0c4
+#+macro: libgcrypt_sha2 3d35df906d6eab354504c05d749a9b021944cb29ff5f65c8ef9c3dd5f7b6689f
#
@@ -112,20 +111,21 @@
#
# LIBGPG-ERROR
#
-#+macro: libgpg_error_ver 1.23
-#+macro: libgpg_error_date 2016-06-15
-#+macro: libgpg_error_size 763k
-#+macro: libgpg_error_sha1 c6a0c49211955e924593527b32e4b2736cafcda5
-#+macro: libgpg_error_sha2 7f0c7f65b98c4048f649bfeebfa4d4c1559707492962504592b985634c939eaa
+#+macro: libgpg_error_ver 1.24
+#+macro: libgpg_error_date 2016-07-14
+#+macro: libgpg_error_size 765k
+#+macro: libgpg_error_sha1 c3e5bd0c3ddea647416b429cd8e2ec755bad9d9e
+#+macro: libgpg_error_sha2 9268e1cc487de5e6e4460fca612a06e4f383072ac43ae90603e5e46783d3e540
#
# LIBASSUAN
#
-#+macro: libassuan_ver 2.4.2
-#+macro: libassuan_date 2015-12-02
-#+macro: libassuan_size 574k
-#+macro: libassuan_sha1 ac1047f9764fd4a4db7dafe47640643164394db9
+#+macro: libassuan_ver 2.4.3
+#+macro: libassuan_date 2016-07-14
+#+macro: libassuan_size 546k
+#+macro: libassuan_sha1 27391cf4a820b5350ea789c30661830c9a271518
+#+macro: libassuan_sha2 22843a3bdb256f59be49842abf24da76700354293a066d82ade8134bb5aa2b71
#
-----------------------------------------------------------------------
Summary of changes:
web/faq/whats-new-in-2.1.org | 93 ++++++++++++++++++++++++++++++++++++--------
web/index.org | 11 ++++++
web/swdb.mac | 50 ++++++++++++------------
3 files changed, 112 insertions(+), 42 deletions(-)
hooks/post-receive
--
The GnuPG website and other docs
http://git.gnupg.org
More information about the Gnupg-commits
mailing list