info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Gnupg-announce Digest, Vol 67, Issue 1
1 view
Skip to first unread message
Anonymous
Aug 27, 2021, 12:51:48 PM8/27/21
to
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.gnupg.org/mailman/listinfo/gnupg-announce
or, via email, send a message with subject or body 'help' to
gnupg-annou...@gnupg.org
You can reach the person managing the list at
gnupg-anno...@gnupg.org
Today's Topics:
1. GnuPG 2.2.29 (LTS) released (Werner Koch)
2. GnuPG 2.3.2 released (Werner Koch)
3. GnuPG 2.2.30 (LTS) released (Werner Koch)
----------------------------------------------------------------------
Message: 1
Date: Sun, 04 Jul 2021 17:43:46 +0200
From: Werner Koch <w...@gnupg.org>
To: gnupg-a...@gnupg.org
Cc: info...@gnu.org
Subject: [Announce] GnuPG 2.2.29 (LTS) released
Message-ID: <87tulaa...@wheatstone.g10code.de>
Content-Type: text/plain; charset="us-ascii"
Hello!
We are pleased to announce the availability of a new GnuPG LTS
release:
version 2.2.29. This release fixes a few minor regression recently
introduced with 2.2.28 and changes the default OpenPGP keyserver.
What is GnuPG
=============
The GNU Privacy Guard (GnuPG, GPG) is a complete and free
implementation
of the OpenPGP and S/MIME standards.
GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public
key
directories. GnuPG itself is a command line tool with features for
easy
integration with other applications. The separate library GPGME
provides
a uniform API to use the GnuPG engine by software written in common
programming languages. A wealth of frontend applications and
libraries
making use of GnuPG are available. As an universal crypto engine
GnuPG
provides support for S/MIME and Secure Shell in addition to OpenPGP.
GnuPG is Free Software (meaning that it respects your freedom). It
can
be freely used, modified and distributed under the terms of the GNU
General Public License.
Noteworthy changes in version 2.2.29 (2021-07-04)
=================================================
* Fix regression in 2.2.28 for Yubikey NEO. [#5487]
* Change the default keyserver to keyserver.ubuntu.com. This is a
temporary change due to the shutdown of the SKS keyserver pools.
[47c4e3e00a]
* gpg: Let --fetch-key return an exit code on failure. [#5376]
* dirmngr: Fix regression in KS_GET for mail address pattern.
[#5497]
* Add fallback in case the Windows console can't cope with Unicode.
[#5491]
* Improve initialization of SPR532 in the CCID driver and make the
driver more robust. [#5297,b90c55fa66db]
* Make test suite work in presence of a broken Libgcrypt
installation. [#5502]
* Make configure option --disable-ldap work again.
Release-info: https://dev.gnupg.org/T5498
Getting the Software
====================
Please follow the instructions found at <https://gnupg.org/download/> or
read on:
GnuPG 2.2.29 may be downloaded from one of the GnuPG mirror sites or
direct from its primary FTP server. The list of mirrors can be found
at
<https://gnupg.org/download/mirrors.html>. Note that GnuPG is not
available at ftp.gnu.org.
The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.29.tar.bz2 (7046k)
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.29.tar.bz2.sig
An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here:
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.29_20210704.exe
(4381k)
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.29_20210704.exe.sig
The source used to build the Windows installer can be found in the
same
directory with a ".tar.xz" suffix.
A new version of Gpg4win will probably not be published. Users
affected
by one of the fixed bugs may instead install this version on top of
Gpg4win 3.1.16.
Checking the Integrity
======================
In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:
* If you already have a version of GnuPG installed, you can simply
verify the supplied signature. For example to verify the signature
of the file gnupg-2.2.29.tar.bz2 you would use this command:
gpg --verify gnupg-2.2.29.tar.bz2.sig gnupg-2.2.29.tar.bz2
This checks whether the signature file matches the source file.
You should see a message indicating that the signature is good and
made by one or more of the release signing keys. Make sure that
this is a valid key, either by matching the shown fingerprint
against a trustworthy list of valid release signing keys or by
checking that the key has been signed by trustworthy other keys.
See the end of this mail for information on the signing keys.
* If you are not able to use an existing version of GnuPG, you have
to verify the SHA-1 checksum. On Unix systems the command to do
this is either "sha1sum" or "shasum". Assuming you downloaded the
file gnupg-2.2.29.tar.bz2, you run the command like this:
sha1sum gnupg-2.2.29.tar.bz2
and check that the output matches the next line:
55393b89cfe520087f4fe55ade2d573e245af58b gnupg-2.2.29.tar.bz2
12ac77a653bfd36a836e7ccd1de95e08a81c9f6d gnupg-w32-
2.2.29_20210704.tar.xz
5ca4348a20b52250d7ff962667d47f5da65ca679 gnupg-w32-
2.2.29_20210704.exe
Internationalization
====================
This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian,
Japanese, Norwegian, Polish, Russian, and Ukrainian being almost
completely translated.
Documentation and Support
=========================
The file gnupg.info has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details available only in thee manual. The manual is also available
online at
https://gnupg.org/documentation/manuals/gnupg/
or can be downloaded as PDF at
https://gnupg.org/documentation/manuals/gnupg.pdf .
You may also want to search the GnuPG mailing list archives or ask on
the gnupg-users mailing list for advise on how to solve problems.
Most
of the new features are around for several years and thus enough
public
experience is available. https://wiki.gnupg.org has user contributed
information around GnuPG and relate software.
In case of build problems specific to this release please first check
https://dev.gnupg.org/T5498 for updated information.
Please consult the archive of the gnupg-users mailing list before
reporting a bug: https://gnupg.org/documentation/mailing-lists.html.
We suggest to send bug reports for a new release to this list in favor
of filing a bug at https://bugs.gnupg.org. If you need commercial
support go to https://gnupg.com or https://gnupg.org/service.html.
If you are a developer and you need a certain feature for your
project,
please do not hesitate to bring it to the gnupg-devel mailing list for
discussion.
Thanks
======
Since 2001 maintenance and development of GnuPG is done by g10 Code
GmbH
and still mostly financed by donations. Three full-time employed
developers as well as two contractors exclusively work on GnuPG and
closely related software like Libgcrypt, GPGME and Gpg4win.
We like to thank all the nice people who are helping the GnuPG
project,
be it testing, coding, translating, suggesting, auditing,
administering
the servers, spreading the word, or answering questions on the mailing
lists.
Many thanks to our numerous financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good and secure shape and to address all the small and larger requests
made by our users. Thanks.
Happy hacking,
Your GnuPG hackers
p.s.
This is an announcement only mailing list. Please send replies only
to
the gnupg-users'at'gnupg.org mailing list.
p.p.s
List of Release Signing Keys:
To guarantee that a downloaded GnuPG version has not been tampered by
malicious entities we provide signature files for all tarballs and
binary versions. The keys are also signed by the long term keys of
their respective owners. Current releases are signed by one or more
of these four keys:
ed25519 2020-08-24 [expires: 2030-06-30]
Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA
Werner Koch (dist signing 2020)
rsa3072 2017-03-17 [expires: 2027-03-15]
Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28
Andre Heinecke (Release Signing Key)
rsa2048 2011-01-12 [expires: 2021-12-31]
Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
Werner Koch (dist sig)
The keys are available at https://gnupg.org/signature_key.html and
in any recently released GnuPG tarball in the file g10/distsigkey.gpg
.
Note that this mail has been signed by a different key.
--
"If privacy is outlawed, only outlaws will have privacy."
- PRZ 1991
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-announce/attachments/20210704/1585b982/attachment-0001.sig>
------------------------------
Message: 2
Date: Tue, 24 Aug 2021 19:51:51 +0200
From: Werner Koch <w...@gnupg.org>
To: gnupg-a...@gnupg.org
Cc: info...@gnu.org
Subject: [Announce] GnuPG 2.3.2 released
Message-ID: <87eeais...@wheatstone.g10code.de>
Content-Type: text/plain; charset="us-ascii"
Hello!
We are pleased to announce the availability of a new GnuPG release:
version 2.3.2. This is the third release in the new 2.3 series which
fixes a couple of bugs and adds a few new things. See below for
details.
What is GnuPG
=============
The GNU Privacy Guard (GnuPG, GPG) is a complete and free
implementation
of the OpenPGP and S/MIME standards.
GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public
key
directories. GnuPG itself is a command line tool with features for
easy
integration with other applications. The separate library GPGME
provides
a uniform API to use the GnuPG engine by software written in common
programming languages. A wealth of frontend applications and
libraries
making use of GnuPG are available. As an universal crypto engine
GnuPG
provides support for S/MIME and Secure Shell in addition to OpenPGP.
GnuPG is Free Software (meaning that it respects your freedom). It
can
be freely used, modified and distributed under the terms of the GNU
General Public License.
Three different series of GnuPG are actively maintained:
- Version 2.3 is the latest development series with a lot of new
features. This announcement is about the latest release of this
series.
- Version 2.2 is our LTS (long term support) version and guaranteed to
be maintained at least until the end of 2024.
See https://gnupg.org/download/index.html#end-of-life
- Version 1.4 is maintained to allow decryption of very old data which
is, for security reasons, not anymore possible with other GnuPG
versions.
Noteworthy changes in version 2.3.2
===================================
* gpg: Allow fingerprint based lookup with --locate-external-key.
[ec36eca08c]
* gpg: Allow decryption w/o public key but with correct card
inserted. [50293ec2eb]
* gpg: Auto import keys specified with --trusted-keys. [100037ac0f]
* gpg: Do not use import-clean for LDAP keyserver imports. [#5387]
* gpg: Fix mailbox based search via AKL keyserver method.
[4fcfac6feb]
* gpg: Fix memory corruption with --clearsign introduced with 2.3.1.
[#5430]
* gpg: Use a more descriptive prompt for symmetric decryption.
[6dfae2f402]
* gpg: Improve speed of secret key listing. [40da61b89b]
* gpg: Support keygrip search with traditional keyring. [#5469]
* gpg: Let --fetch-key return an exit code on failure. [#5376]
* gpg: Emit the NO_SECKEY status again for decryption. [#5562]
* gpgsm: Support decryption of password based encryption (pwri).
[eeb65d3bbd]
* gpgsm: Support AES-GCM decryption. [4980fb3c6d]
* gpgsm: Let --dump-cert --show-cert also print an OpenPGP
fingerprint. [52bbdc731f]
* gpgsm: Fix finding of issuer in use-keyboxd mode. [6b76693ff5]
* gpgsm: New option --ldapserver as an alias for --keyserver.
[89df86157e]
* agent: Use SHA-256 for SSH fingerprint by default. [#5434]
* agent: Fix calling handle_pincache_put. [#5436]
* agent: Fix importing protected secret key. [#5122]
* agent: Fix a regression in agent_get_shadow_info_type. [#5393]
* agent: Add translatable text for Caps Lock hint. [#4950]
* agent: New option --pinentry-formatted-passphrase. [#5517]
* agent: Add checkpin inquiry for pinentry. [#5517,#5532]
* agent: New option --check-sym-passphrase-pattern. [#5517]
* agent: Use the sysconfdir for a pattern file.
* agent: Make QT_QPA_PLATFORMTHEME=qt5ct work for the pinentry.
[1305baf099]
* dirmngr: LDAP search by a mailbox now ignores revoked keys.
[1406f551f1]
* dirmngr: For KS_SEARCH return the fingerprint also with LDAP.
[#5441]
* dirmngr: Allow for non-URL specified ldap keyservers.
[#5405,#5452]
* dirmngr: New option --ldapserver. [52cf32ce2f]
* dirmngr: Fix regression in KS_GET for mail address pattern.
[#5497]
* card: New option --shadow for the list command. [2fce99d73a]
* tests: Make sure the built keyboxd is used. [#5406]
* scd: Fix computing shared secrets for 512 bit curves.
[9e24f2a45c]
* scd: Fix unblock PIN by a Reset Code with KDF. [#5413]
* scd: Fix PC/SC removed card problem. [8d81fd7c01]
* scd: Recover the partial match for PORTSTR for PC/SC.
[53bdc6288f]
* scd: Make sure to release the PC/SC context. [#5416]
* scd: Fix zero-byte handling in ECC. [#5163]
* scd: Fix serial number detection for Yubikey 5. [#5442]
* scd: Add basic support for AET JCOP cards. [544ec7872a]
* scd: Detect external interference when --pcsc-shared is in use.
[#5484]
* scd: Fix access to the list of cards. [#5524]
* gpgconf: Do not list a disabled tpm2d. [#5408]
* gpgconf: Make runtime changes with different homedir work.
[31c0aa2ff3]
* keyboxd: Fix searching for exact mail adddress. [f79e9540ca]
* keyboxd: Fix searching with multiple patterns. [101ba4f18a]
* gpgtar: Fix file size computation under Windows. [14e36bdbe1]
* tools: Extend gpg-check-pattern. [73c03e0232]
* wkd: Fix client issue with leading or trailing spaces in
user-ids. [b4345f7521]
* Under Windows add a fallback in case the console can't cope with
Unicode. [#5491]
* Under Windows use LOCAL_APPDATA for the socket directory. [#5537]
* Pass XDG_SESSION_TYPE and QT_QPA_PLATFORM envvars to Pinentry.
[#3659]
* Change the default keyserver to keyserver.ubuntu.com. This is a
temporary change due to the shutdown of the SKS keyserver pools.
[55b5928099]
Release-info: https://dev.gnupg.org/T5405
Getting the Software
====================
Please follow the instructions found at <https://gnupg.org/download/> or
read on:
GnuPG may be downloaded from one of the GnuPG mirror sites or direct
from its primary FTP server. The list of mirrors can be found at
<https://gnupg.org/download/mirrors.html>. Note that GnuPG is not
available at ftp.gnu.org.
The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.3.2.tar.bz2 (7411k)
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.3.2.tar.bz2.sig
An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here:
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.3.2_20210824.exe
(4586k)
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.3.2_20210824.exe.sig
The source used to build the Windows installer can be found in the
same
directory with a ".tar.xz" suffix.
If you want to use this GnuPG versions with Gpg4win simply install it
on
on top of Gpg4win 3.1.16.
Checking the Integrity
======================
In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:
* If you already have a version of GnuPG installed, you can simply
verify the supplied signature. For example to verify the signature
of the file gnupg-2.3.2.tar.bz2 you would use this command:
gpg --verify gnupg-2.3.2.tar.bz2.sig gnupg-2.3.2.tar.bz2
This checks whether the signature file matches the source file.
You should see a message indicating that the signature is good and
made by one or more of the release signing keys. Make sure that
this is a valid key, either by matching the shown fingerprint
against a trustworthy list of valid release signing keys or by
checking that the key has been signed by trustworthy other keys.
See the end of this mail for information on the signing keys.
* If you are not able to use an existing version of GnuPG, you have
to verify the SHA-1 checksum. On Unix systems the command to do
this is either "sha1sum" or "shasum". Assuming you downloaded the
file gnupg-2.3.2.tar.bz2, you run the command like this:
sha1sum gnupg-2.3.2.tar.bz2
and check that the output matches the next line:
f0f44b29e3702d3be1b25c964dfc2aaefe70e2fc gnupg-2.3.2.tar.bz2
7c8ff377310f9781b89efb06222e7e74a19ed477 gnupg-w32-
2.3.2_20210824.tar.xz
f6c1591e06ee2801961e216f44bc67243e87576f gnupg-w32-2.3.2_20210824.exe
Internationalization
====================
This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian,
Japanese, Norwegian, Polish, Russian, and Ukrainian being almost
completely translated.
Documentation and Support
=========================
The file gnupg.info has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details available only in the manual. The manual is also available
online at
https://gnupg.org/documentation/manuals/gnupg/
or can be downloaded as PDF at
https://gnupg.org/documentation/manuals/gnupg.pdf
You may also want to search the GnuPG mailing list archives or ask on
the gnupg-users mailing list for advise on how to solve problems.
Most
of the new features are around for several years and thus enough
public
experience is available. https://wiki.gnupg.org has user contributed
information around GnuPG and relate software.
In case of build problems specific to this release please first check
https://dev.gnupg.org/T5405 for updated information.
Please consult the archive of the gnupg-users mailing list before
reporting a bug: https://gnupg.org/documentation/mailing-lists.html.
We suggest to send bug reports for a new release to this list in favor
of filing a bug at https://bugs.gnupg.org. If you need commercial
support go to https://gnupg.com or https://gnupg.org/service.html.
If you are a developer and you need a certain feature for your
project,
please do not hesitate to bring it to the gnupg-devel mailing list for
discussion.
Thanks
======
Since 2001 maintenance and development of GnuPG is done by g10 Code
GmbH
and still mostly financed by donations. Three full-time employed
developers as well as two contractors exclusively work on GnuPG and
closely related software like Libgcrypt, GPGME and Gpg4win.
We like to thank all the nice people who are helping the GnuPG
project,
be it testing, coding, translating, suggesting, auditing,
administering
the servers, spreading the word, or answering questions on the mailing
lists.
The financial support of the governmental CERT of Luxembourg
(GOVCERT.LU) allowed us to develop new and improved features for
smartcards (Yubikey, PIV and Scute) as well as various usability
features. Thanks.
Many thanks also to all other financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good and secure shape and to address all the small and larger requests
made by our users.
Happy hacking,
Your GnuPG hackers
p.s.
This is an announcement only mailing list. Please send replies only
to
the gnupg-users at gnupg.org mailing list.
p.p.s
List of Release Signing Keys:
To guarantee that a downloaded GnuPG version has not been tampered by
malicious entities we provide signature files for all tarballs and
binary versions. The keys are also signed by the long term keys of
their respective owners. Current releases are signed by one or more
of these four keys:
ed25519 2020-08-24 [expires: 2030-06-30]
Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA
Werner Koch (dist signing 2020)
rsa3072 2017-03-17 [expires: 2027-03-15]
Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28
Andre Heinecke (Release Signing Key)
rsa2048 2011-01-12 [expires: 2021-12-31]
Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
Werner Koch (dist sig)
The keys are available at https://gnupg.org/signature_key.html and
in any recently released GnuPG tarball in the file g10/distsigkey.gpg
.
Note that this mail has been signed by a different key.
--
Please read
Nils Melzer: Der Fall Julian Assange
It is really important to know the background of the Assange case to
understand the massive perils to free journalism. The book is right
now only available in German: https://dev.gnupg.org/u/melzerassang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-announce/attachments/20210824/b7d21edb/attachment-0001.sig>
------------------------------
Message: 3
Date: Fri, 27 Aug 2021 15:08:19 +0200
From: Werner Koch <w...@gnupg.org>
To: gnupg-a...@gnupg.org
Subject: [Announce] GnuPG 2.2.30 (LTS) released
Message-ID: <87mtp3q...@wheatstone.g10code.de>
Content-Type: text/plain; charset="us-ascii"
Hello!
We are pleased to announce the availability of a new GnuPG LTS
release:
version 2.2.30. This release fixes a few minor bugs and improves the
usability of symmetric-only encryption. The LTS (long term support)
series of GnuPG is guaranteed to be maintained at least until the end
of 2024. See https://gnupg.org/download/index.html#end-of-life
What is GnuPG
=============
The GNU Privacy Guard (GnuPG, GPG) is a complete and free
implementation
of the OpenPGP and S/MIME standards.
GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public
key
directories. GnuPG itself is a command line tool with features for
easy
integration with other applications. The separate library GPGME
provides
a uniform API to use the GnuPG engine by software written in common
programming languages. A wealth of frontend applications and
libraries
making use of GnuPG are available. As an universal crypto engine
GnuPG
provides support for S/MIME and Secure Shell in addition to OpenPGP.
GnuPG is Free Software (meaning that it respects your freedom). It
can
be freely used, modified and distributed under the terms of the GNU
General Public License.
Noteworthy changes in version 2.2.30 (2021-08-26)
=================================================
* gpg: Extended gpg-check-pattern to support accept rules,
conjunctions, and case-sensitive matching. [5ca15e58b2]
* agent: New option --pinentry-formatted-passphrase. [#5553]
* agent: New option --check-sym-passphrase-pattern. [#5517]
* agent: Use the sysconfdir for the pattern files. [5ed8e598fa]
* agent: Add "checkpin" inquiry for use by pinentry. [#5532]
* wkd: Fix client issue with leading or trailing spaces in
user-ids. [576e429d41]
* Pass XDG_SESSION_TYPE and QT_QPA_PLATFORM envvars to Pinentry.
[#3659]
* Under Windows use LOCAL_APPDATA for the socket directory. [#5537]
Release-info: https://dev.gnupg.org/T5519
Getting the Software
====================
Please follow the instructions found at <https://gnupg.org/download/> or
read on:
GnuPG 2.2.30 may be downloaded from one of the GnuPG mirror sites or
direct from its primary FTP server. The list of mirrors can be found
at
<https://gnupg.org/download/mirrors.html>. Note that GnuPG is not
available at ftp.gnu.org.
The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.30.tar.bz2 (7046k)
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.30.tar.bz2.sig
An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here:
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.30_20210826.exe
(4393k)
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.30_20210826.exe.sig
The source used to build the Windows installer can be found in the
same
directory with a ".tar.xz" suffix.
A new version of Gpg4win will probably not be published. Users
affected
by one of the fixed bugs may instead install this version on top of
Gpg4win 3.1.16.
Checking the Integrity
======================
In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:
* If you already have a version of GnuPG installed, you can simply
verify the supplied signature. For example to verify the signature
of the file gnupg-2.2.30.tar.bz2 you would use this command:
gpg --verify gnupg-2.2.30.tar.bz2.sig gnupg-2.2.30.tar.bz2
This checks whether the signature file matches the source file.
You should see a message indicating that the signature is good and
made by one or more of the release signing keys. Make sure that
this is a valid key, either by matching the shown fingerprint
against a trustworthy list of valid release signing keys or by
checking that the key has been signed by trustworthy other keys.
See the end of this mail for information on the signing keys.
* If you are not able to use an existing version of GnuPG, you have
to verify the SHA-1 checksum. On Unix systems the command to do
this is either "sha1sum" or "shasum". Assuming you downloaded the
file gnupg-2.2.30.tar.bz2, you run the command like this:
sha1sum gnupg-2.2.30.tar.bz2
and check that the output matches the next line:
bf9908b1a36b2bd1a4b9f0890198e8fb2d77a91c gnupg-2.2.30.tar.bz2
2de8c54af9387c1068cba06ef23ac197dac8ced0 gnupg-w32-
2.2.30_20210826.tar.xz
f576c2b194c609bfd0386569ef3b51dd2eb38a12 gnupg-w32-
2.2.30_20210826.exe
Internationalization
====================
This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian,
Japanese, Norwegian, Polish, Russian, and Ukrainian being almost
completely translated.
Documentation and Support
=========================
The file gnupg.info has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details available only in thee manual. The manual is also available
online at
https://gnupg.org/documentation/manuals/gnupg/
or can be downloaded as PDF at
https://gnupg.org/documentation/manuals/gnupg.pdf .
You may also want to search the GnuPG mailing list archives or ask on
the gnupg-users mailing list for advise on how to solve problems.
Most
of the new features are around for several years and thus enough
public
experience is available. https://wiki.gnupg.org has user contributed
information around GnuPG and relate software.
In case of build problems specific to this release please first check
https://dev.gnupg.org/T5519 for updated information.
Please consult the archive of the gnupg-users mailing list before
reporting a bug: https://gnupg.org/documentation/mailing-lists.html.
We suggest to send bug reports for a new release to this list in favor
of filing a bug at https://bugs.gnupg.org. If you need commercial
support go to https://gnupg.com or https://gnupg.org/service.html.
If you are a developer and you need a certain feature for your
project,
please do not hesitate to bring it to the gnupg-devel mailing list for
discussion.
Thanks
======
Since 2001 maintenance and development of GnuPG is done by g10 Code
GmbH
and still mostly financed by donations. Three full-time employed
developers as well as two contractors exclusively work on GnuPG and
closely related software like Libgcrypt, GPGME and Gpg4win.
We like to thank all the nice people who are helping the GnuPG
project,
be it testing, coding, translating, suggesting, auditing,
administering
the servers, spreading the word, or answering questions on the mailing
lists.
Many thanks to our numerous financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good and secure shape and to address all the small and larger requests
made by our users. Thanks.
Happy hacking,
Your GnuPG hackers
p.s.
This is an announcement only mailing list. Please send replies only
to
the gnupg-users'at'gnupg.org mailing list.
List of Release Signing Keys:
To guarantee that a downloaded GnuPG version has not been tampered by
malicious entities we provide signature files for all tarballs and
binary versions. The keys are also signed by the long term keys of
their respective owners. Current releases are signed by one or more
of these four keys:
ed25519 2020-08-24 [expires: 2030-06-30]
Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA
Werner Koch (dist signing 2020)
rsa3072 2017-03-17 [expires: 2027-03-15]
Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28
Andre Heinecke (Release Signing Key)
rsa2048 2011-01-12 [expires: 2021-12-31]
Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
Werner Koch (dist sig)
The keys are available at https://gnupg.org/signature_key.html and
in any recently released GnuPG tarball in the file g10/distsigkey.gpg
.
Note that this mail has been signed by a different key.
--
Please read
Nils Melzer: Der Fall Julian Assange
It is really important to know the background of the Assange case to
understand the massive perils to free journalism. The book is right
now only available in German: https://dev.gnupg.org/u/melzerassang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-announce/attachments/20210827/92b21111/attachment.sig>
------------------------------
Subject: Digest Footer
_______________________________________________
Gnupg-announce mailing list
Gnupg-a...@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-announce
------------------------------
End of Gnupg-announce Digest, Vol 67, Issue 1
*********************************************
http://lists.gnupg.org/mailman/listinfo/gnupg-announce
or, via email, send a message with subject or body 'help' to
gnupg-annou...@gnupg.org
You can reach the person managing the list at
gnupg-anno...@gnupg.org
Today's Topics:
1. GnuPG 2.2.29 (LTS) released (Werner Koch)
2. GnuPG 2.3.2 released (Werner Koch)
3. GnuPG 2.2.30 (LTS) released (Werner Koch)
----------------------------------------------------------------------
Message: 1
Date: Sun, 04 Jul 2021 17:43:46 +0200
From: Werner Koch <w...@gnupg.org>
To: gnupg-a...@gnupg.org
Cc: info...@gnu.org
Subject: [Announce] GnuPG 2.2.29 (LTS) released
Message-ID: <87tulaa...@wheatstone.g10code.de>
Content-Type: text/plain; charset="us-ascii"
Hello!
We are pleased to announce the availability of a new GnuPG LTS
release:
version 2.2.29. This release fixes a few minor regression recently
introduced with 2.2.28 and changes the default OpenPGP keyserver.
What is GnuPG
=============
The GNU Privacy Guard (GnuPG, GPG) is a complete and free
implementation
of the OpenPGP and S/MIME standards.
GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public
key
directories. GnuPG itself is a command line tool with features for
easy
integration with other applications. The separate library GPGME
provides
a uniform API to use the GnuPG engine by software written in common
programming languages. A wealth of frontend applications and
libraries
making use of GnuPG are available. As an universal crypto engine
GnuPG
provides support for S/MIME and Secure Shell in addition to OpenPGP.
GnuPG is Free Software (meaning that it respects your freedom). It
can
be freely used, modified and distributed under the terms of the GNU
General Public License.
Noteworthy changes in version 2.2.29 (2021-07-04)
=================================================
* Fix regression in 2.2.28 for Yubikey NEO. [#5487]
* Change the default keyserver to keyserver.ubuntu.com. This is a
temporary change due to the shutdown of the SKS keyserver pools.
[47c4e3e00a]
* gpg: Let --fetch-key return an exit code on failure. [#5376]
* dirmngr: Fix regression in KS_GET for mail address pattern.
[#5497]
* Add fallback in case the Windows console can't cope with Unicode.
[#5491]
* Improve initialization of SPR532 in the CCID driver and make the
driver more robust. [#5297,b90c55fa66db]
* Make test suite work in presence of a broken Libgcrypt
installation. [#5502]
* Make configure option --disable-ldap work again.
Release-info: https://dev.gnupg.org/T5498
Getting the Software
====================
Please follow the instructions found at <https://gnupg.org/download/> or
read on:
GnuPG 2.2.29 may be downloaded from one of the GnuPG mirror sites or
direct from its primary FTP server. The list of mirrors can be found
at
<https://gnupg.org/download/mirrors.html>. Note that GnuPG is not
available at ftp.gnu.org.
The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.29.tar.bz2 (7046k)
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.29.tar.bz2.sig
An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here:
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.29_20210704.exe
(4381k)
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.29_20210704.exe.sig
The source used to build the Windows installer can be found in the
same
directory with a ".tar.xz" suffix.
A new version of Gpg4win will probably not be published. Users
affected
by one of the fixed bugs may instead install this version on top of
Gpg4win 3.1.16.
Checking the Integrity
======================
In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:
* If you already have a version of GnuPG installed, you can simply
verify the supplied signature. For example to verify the signature
of the file gnupg-2.2.29.tar.bz2 you would use this command:
gpg --verify gnupg-2.2.29.tar.bz2.sig gnupg-2.2.29.tar.bz2
This checks whether the signature file matches the source file.
You should see a message indicating that the signature is good and
made by one or more of the release signing keys. Make sure that
this is a valid key, either by matching the shown fingerprint
against a trustworthy list of valid release signing keys or by
checking that the key has been signed by trustworthy other keys.
See the end of this mail for information on the signing keys.
* If you are not able to use an existing version of GnuPG, you have
to verify the SHA-1 checksum. On Unix systems the command to do
this is either "sha1sum" or "shasum". Assuming you downloaded the
file gnupg-2.2.29.tar.bz2, you run the command like this:
sha1sum gnupg-2.2.29.tar.bz2
and check that the output matches the next line:
55393b89cfe520087f4fe55ade2d573e245af58b gnupg-2.2.29.tar.bz2
12ac77a653bfd36a836e7ccd1de95e08a81c9f6d gnupg-w32-
2.2.29_20210704.tar.xz
5ca4348a20b52250d7ff962667d47f5da65ca679 gnupg-w32-
2.2.29_20210704.exe
Internationalization
====================
This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian,
Japanese, Norwegian, Polish, Russian, and Ukrainian being almost
completely translated.
Documentation and Support
=========================
The file gnupg.info has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details available only in thee manual. The manual is also available
online at
https://gnupg.org/documentation/manuals/gnupg/
or can be downloaded as PDF at
https://gnupg.org/documentation/manuals/gnupg.pdf .
You may also want to search the GnuPG mailing list archives or ask on
the gnupg-users mailing list for advise on how to solve problems.
Most
of the new features are around for several years and thus enough
public
experience is available. https://wiki.gnupg.org has user contributed
information around GnuPG and relate software.
In case of build problems specific to this release please first check
https://dev.gnupg.org/T5498 for updated information.
Please consult the archive of the gnupg-users mailing list before
reporting a bug: https://gnupg.org/documentation/mailing-lists.html.
We suggest to send bug reports for a new release to this list in favor
of filing a bug at https://bugs.gnupg.org. If you need commercial
support go to https://gnupg.com or https://gnupg.org/service.html.
If you are a developer and you need a certain feature for your
project,
please do not hesitate to bring it to the gnupg-devel mailing list for
discussion.
Thanks
======
Since 2001 maintenance and development of GnuPG is done by g10 Code
GmbH
and still mostly financed by donations. Three full-time employed
developers as well as two contractors exclusively work on GnuPG and
closely related software like Libgcrypt, GPGME and Gpg4win.
We like to thank all the nice people who are helping the GnuPG
project,
be it testing, coding, translating, suggesting, auditing,
administering
the servers, spreading the word, or answering questions on the mailing
lists.
Many thanks to our numerous financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good and secure shape and to address all the small and larger requests
made by our users. Thanks.
Happy hacking,
Your GnuPG hackers
p.s.
This is an announcement only mailing list. Please send replies only
to
the gnupg-users'at'gnupg.org mailing list.
p.p.s
List of Release Signing Keys:
To guarantee that a downloaded GnuPG version has not been tampered by
malicious entities we provide signature files for all tarballs and
binary versions. The keys are also signed by the long term keys of
their respective owners. Current releases are signed by one or more
of these four keys:
ed25519 2020-08-24 [expires: 2030-06-30]
Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA
Werner Koch (dist signing 2020)
rsa3072 2017-03-17 [expires: 2027-03-15]
Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28
Andre Heinecke (Release Signing Key)
rsa2048 2011-01-12 [expires: 2021-12-31]
Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
Werner Koch (dist sig)
The keys are available at https://gnupg.org/signature_key.html and
in any recently released GnuPG tarball in the file g10/distsigkey.gpg
.
Note that this mail has been signed by a different key.
--
"If privacy is outlawed, only outlaws will have privacy."
- PRZ 1991
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-announce/attachments/20210704/1585b982/attachment-0001.sig>
------------------------------
Message: 2
Date: Tue, 24 Aug 2021 19:51:51 +0200
From: Werner Koch <w...@gnupg.org>
To: gnupg-a...@gnupg.org
Cc: info...@gnu.org
Subject: [Announce] GnuPG 2.3.2 released
Message-ID: <87eeais...@wheatstone.g10code.de>
Content-Type: text/plain; charset="us-ascii"
Hello!
We are pleased to announce the availability of a new GnuPG release:
version 2.3.2. This is the third release in the new 2.3 series which
fixes a couple of bugs and adds a few new things. See below for
details.
What is GnuPG
=============
The GNU Privacy Guard (GnuPG, GPG) is a complete and free
implementation
of the OpenPGP and S/MIME standards.
GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public
key
directories. GnuPG itself is a command line tool with features for
easy
integration with other applications. The separate library GPGME
provides
a uniform API to use the GnuPG engine by software written in common
programming languages. A wealth of frontend applications and
libraries
making use of GnuPG are available. As an universal crypto engine
GnuPG
provides support for S/MIME and Secure Shell in addition to OpenPGP.
GnuPG is Free Software (meaning that it respects your freedom). It
can
be freely used, modified and distributed under the terms of the GNU
General Public License.
Three different series of GnuPG are actively maintained:
- Version 2.3 is the latest development series with a lot of new
features. This announcement is about the latest release of this
series.
- Version 2.2 is our LTS (long term support) version and guaranteed to
be maintained at least until the end of 2024.
See https://gnupg.org/download/index.html#end-of-life
- Version 1.4 is maintained to allow decryption of very old data which
is, for security reasons, not anymore possible with other GnuPG
versions.
Noteworthy changes in version 2.3.2
===================================
* gpg: Allow fingerprint based lookup with --locate-external-key.
[ec36eca08c]
* gpg: Allow decryption w/o public key but with correct card
inserted. [50293ec2eb]
* gpg: Auto import keys specified with --trusted-keys. [100037ac0f]
* gpg: Do not use import-clean for LDAP keyserver imports. [#5387]
* gpg: Fix mailbox based search via AKL keyserver method.
[4fcfac6feb]
* gpg: Fix memory corruption with --clearsign introduced with 2.3.1.
[#5430]
* gpg: Use a more descriptive prompt for symmetric decryption.
[6dfae2f402]
* gpg: Improve speed of secret key listing. [40da61b89b]
* gpg: Support keygrip search with traditional keyring. [#5469]
* gpg: Let --fetch-key return an exit code on failure. [#5376]
* gpg: Emit the NO_SECKEY status again for decryption. [#5562]
* gpgsm: Support decryption of password based encryption (pwri).
[eeb65d3bbd]
* gpgsm: Support AES-GCM decryption. [4980fb3c6d]
* gpgsm: Let --dump-cert --show-cert also print an OpenPGP
fingerprint. [52bbdc731f]
* gpgsm: Fix finding of issuer in use-keyboxd mode. [6b76693ff5]
* gpgsm: New option --ldapserver as an alias for --keyserver.
[89df86157e]
* agent: Use SHA-256 for SSH fingerprint by default. [#5434]
* agent: Fix calling handle_pincache_put. [#5436]
* agent: Fix importing protected secret key. [#5122]
* agent: Fix a regression in agent_get_shadow_info_type. [#5393]
* agent: Add translatable text for Caps Lock hint. [#4950]
* agent: New option --pinentry-formatted-passphrase. [#5517]
* agent: Add checkpin inquiry for pinentry. [#5517,#5532]
* agent: New option --check-sym-passphrase-pattern. [#5517]
* agent: Use the sysconfdir for a pattern file.
* agent: Make QT_QPA_PLATFORMTHEME=qt5ct work for the pinentry.
[1305baf099]
* dirmngr: LDAP search by a mailbox now ignores revoked keys.
[1406f551f1]
* dirmngr: For KS_SEARCH return the fingerprint also with LDAP.
[#5441]
* dirmngr: Allow for non-URL specified ldap keyservers.
[#5405,#5452]
* dirmngr: New option --ldapserver. [52cf32ce2f]
* dirmngr: Fix regression in KS_GET for mail address pattern.
[#5497]
* card: New option --shadow for the list command. [2fce99d73a]
* tests: Make sure the built keyboxd is used. [#5406]
* scd: Fix computing shared secrets for 512 bit curves.
[9e24f2a45c]
* scd: Fix unblock PIN by a Reset Code with KDF. [#5413]
* scd: Fix PC/SC removed card problem. [8d81fd7c01]
* scd: Recover the partial match for PORTSTR for PC/SC.
[53bdc6288f]
* scd: Make sure to release the PC/SC context. [#5416]
* scd: Fix zero-byte handling in ECC. [#5163]
* scd: Fix serial number detection for Yubikey 5. [#5442]
* scd: Add basic support for AET JCOP cards. [544ec7872a]
* scd: Detect external interference when --pcsc-shared is in use.
[#5484]
* scd: Fix access to the list of cards. [#5524]
* gpgconf: Do not list a disabled tpm2d. [#5408]
* gpgconf: Make runtime changes with different homedir work.
[31c0aa2ff3]
* keyboxd: Fix searching for exact mail adddress. [f79e9540ca]
* keyboxd: Fix searching with multiple patterns. [101ba4f18a]
* gpgtar: Fix file size computation under Windows. [14e36bdbe1]
* tools: Extend gpg-check-pattern. [73c03e0232]
* wkd: Fix client issue with leading or trailing spaces in
user-ids. [b4345f7521]
* Under Windows add a fallback in case the console can't cope with
Unicode. [#5491]
* Under Windows use LOCAL_APPDATA for the socket directory. [#5537]
* Pass XDG_SESSION_TYPE and QT_QPA_PLATFORM envvars to Pinentry.
[#3659]
* Change the default keyserver to keyserver.ubuntu.com. This is a
temporary change due to the shutdown of the SKS keyserver pools.
[55b5928099]
Release-info: https://dev.gnupg.org/T5405
Getting the Software
====================
Please follow the instructions found at <https://gnupg.org/download/> or
read on:
GnuPG may be downloaded from one of the GnuPG mirror sites or direct
from its primary FTP server. The list of mirrors can be found at
<https://gnupg.org/download/mirrors.html>. Note that GnuPG is not
available at ftp.gnu.org.
The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.3.2.tar.bz2 (7411k)
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.3.2.tar.bz2.sig
An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here:
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.3.2_20210824.exe
(4586k)
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.3.2_20210824.exe.sig
The source used to build the Windows installer can be found in the
same
directory with a ".tar.xz" suffix.
If you want to use this GnuPG versions with Gpg4win simply install it
on
on top of Gpg4win 3.1.16.
Checking the Integrity
======================
In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:
* If you already have a version of GnuPG installed, you can simply
verify the supplied signature. For example to verify the signature
of the file gnupg-2.3.2.tar.bz2 you would use this command:
gpg --verify gnupg-2.3.2.tar.bz2.sig gnupg-2.3.2.tar.bz2
This checks whether the signature file matches the source file.
You should see a message indicating that the signature is good and
made by one or more of the release signing keys. Make sure that
this is a valid key, either by matching the shown fingerprint
against a trustworthy list of valid release signing keys or by
checking that the key has been signed by trustworthy other keys.
See the end of this mail for information on the signing keys.
* If you are not able to use an existing version of GnuPG, you have
to verify the SHA-1 checksum. On Unix systems the command to do
this is either "sha1sum" or "shasum". Assuming you downloaded the
file gnupg-2.3.2.tar.bz2, you run the command like this:
sha1sum gnupg-2.3.2.tar.bz2
and check that the output matches the next line:
f0f44b29e3702d3be1b25c964dfc2aaefe70e2fc gnupg-2.3.2.tar.bz2
7c8ff377310f9781b89efb06222e7e74a19ed477 gnupg-w32-
2.3.2_20210824.tar.xz
f6c1591e06ee2801961e216f44bc67243e87576f gnupg-w32-2.3.2_20210824.exe
Internationalization
====================
This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian,
Japanese, Norwegian, Polish, Russian, and Ukrainian being almost
completely translated.
Documentation and Support
=========================
The file gnupg.info has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details available only in the manual. The manual is also available
online at
https://gnupg.org/documentation/manuals/gnupg/
or can be downloaded as PDF at
https://gnupg.org/documentation/manuals/gnupg.pdf
You may also want to search the GnuPG mailing list archives or ask on
the gnupg-users mailing list for advise on how to solve problems.
Most
of the new features are around for several years and thus enough
public
experience is available. https://wiki.gnupg.org has user contributed
information around GnuPG and relate software.
In case of build problems specific to this release please first check
https://dev.gnupg.org/T5405 for updated information.
Please consult the archive of the gnupg-users mailing list before
reporting a bug: https://gnupg.org/documentation/mailing-lists.html.
We suggest to send bug reports for a new release to this list in favor
of filing a bug at https://bugs.gnupg.org. If you need commercial
support go to https://gnupg.com or https://gnupg.org/service.html.
If you are a developer and you need a certain feature for your
project,
please do not hesitate to bring it to the gnupg-devel mailing list for
discussion.
Thanks
======
Since 2001 maintenance and development of GnuPG is done by g10 Code
GmbH
and still mostly financed by donations. Three full-time employed
developers as well as two contractors exclusively work on GnuPG and
closely related software like Libgcrypt, GPGME and Gpg4win.
We like to thank all the nice people who are helping the GnuPG
project,
be it testing, coding, translating, suggesting, auditing,
administering
the servers, spreading the word, or answering questions on the mailing
lists.
The financial support of the governmental CERT of Luxembourg
(GOVCERT.LU) allowed us to develop new and improved features for
smartcards (Yubikey, PIV and Scute) as well as various usability
features. Thanks.
Many thanks also to all other financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good and secure shape and to address all the small and larger requests
made by our users.
Happy hacking,
Your GnuPG hackers
p.s.
This is an announcement only mailing list. Please send replies only
to
the gnupg-users at gnupg.org mailing list.
p.p.s
List of Release Signing Keys:
To guarantee that a downloaded GnuPG version has not been tampered by
malicious entities we provide signature files for all tarballs and
binary versions. The keys are also signed by the long term keys of
their respective owners. Current releases are signed by one or more
of these four keys:
ed25519 2020-08-24 [expires: 2030-06-30]
Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA
Werner Koch (dist signing 2020)
rsa3072 2017-03-17 [expires: 2027-03-15]
Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28
Andre Heinecke (Release Signing Key)
rsa2048 2011-01-12 [expires: 2021-12-31]
Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
Werner Koch (dist sig)
The keys are available at https://gnupg.org/signature_key.html and
in any recently released GnuPG tarball in the file g10/distsigkey.gpg
.
Note that this mail has been signed by a different key.
--
Please read
Nils Melzer: Der Fall Julian Assange
It is really important to know the background of the Assange case to
understand the massive perils to free journalism. The book is right
now only available in German: https://dev.gnupg.org/u/melzerassang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-announce/attachments/20210824/b7d21edb/attachment-0001.sig>
------------------------------
Message: 3
Date: Fri, 27 Aug 2021 15:08:19 +0200
From: Werner Koch <w...@gnupg.org>
To: gnupg-a...@gnupg.org
Subject: [Announce] GnuPG 2.2.30 (LTS) released
Message-ID: <87mtp3q...@wheatstone.g10code.de>
Content-Type: text/plain; charset="us-ascii"
Hello!
We are pleased to announce the availability of a new GnuPG LTS
release:
version 2.2.30. This release fixes a few minor bugs and improves the
usability of symmetric-only encryption. The LTS (long term support)
series of GnuPG is guaranteed to be maintained at least until the end
of 2024. See https://gnupg.org/download/index.html#end-of-life
What is GnuPG
=============
The GNU Privacy Guard (GnuPG, GPG) is a complete and free
implementation
of the OpenPGP and S/MIME standards.
GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public
key
directories. GnuPG itself is a command line tool with features for
easy
integration with other applications. The separate library GPGME
provides
a uniform API to use the GnuPG engine by software written in common
programming languages. A wealth of frontend applications and
libraries
making use of GnuPG are available. As an universal crypto engine
GnuPG
provides support for S/MIME and Secure Shell in addition to OpenPGP.
GnuPG is Free Software (meaning that it respects your freedom). It
can
be freely used, modified and distributed under the terms of the GNU
General Public License.
Noteworthy changes in version 2.2.30 (2021-08-26)
=================================================
* gpg: Extended gpg-check-pattern to support accept rules,
conjunctions, and case-sensitive matching. [5ca15e58b2]
* agent: New option --pinentry-formatted-passphrase. [#5553]
* agent: New option --check-sym-passphrase-pattern. [#5517]
* agent: Use the sysconfdir for the pattern files. [5ed8e598fa]
* agent: Add "checkpin" inquiry for use by pinentry. [#5532]
* wkd: Fix client issue with leading or trailing spaces in
user-ids. [576e429d41]
* Pass XDG_SESSION_TYPE and QT_QPA_PLATFORM envvars to Pinentry.
[#3659]
* Under Windows use LOCAL_APPDATA for the socket directory. [#5537]
Release-info: https://dev.gnupg.org/T5519
Getting the Software
====================
Please follow the instructions found at <https://gnupg.org/download/> or
read on:
GnuPG 2.2.30 may be downloaded from one of the GnuPG mirror sites or
direct from its primary FTP server. The list of mirrors can be found
at
<https://gnupg.org/download/mirrors.html>. Note that GnuPG is not
available at ftp.gnu.org.
The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.30.tar.bz2 (7046k)
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.30.tar.bz2.sig
An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here:
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.30_20210826.exe
(4393k)
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.30_20210826.exe.sig
The source used to build the Windows installer can be found in the
same
directory with a ".tar.xz" suffix.
A new version of Gpg4win will probably not be published. Users
affected
by one of the fixed bugs may instead install this version on top of
Gpg4win 3.1.16.
Checking the Integrity
======================
In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:
* If you already have a version of GnuPG installed, you can simply
verify the supplied signature. For example to verify the signature
of the file gnupg-2.2.30.tar.bz2 you would use this command:
gpg --verify gnupg-2.2.30.tar.bz2.sig gnupg-2.2.30.tar.bz2
This checks whether the signature file matches the source file.
You should see a message indicating that the signature is good and
made by one or more of the release signing keys. Make sure that
this is a valid key, either by matching the shown fingerprint
against a trustworthy list of valid release signing keys or by
checking that the key has been signed by trustworthy other keys.
See the end of this mail for information on the signing keys.
* If you are not able to use an existing version of GnuPG, you have
to verify the SHA-1 checksum. On Unix systems the command to do
this is either "sha1sum" or "shasum". Assuming you downloaded the
file gnupg-2.2.30.tar.bz2, you run the command like this:
sha1sum gnupg-2.2.30.tar.bz2
and check that the output matches the next line:
bf9908b1a36b2bd1a4b9f0890198e8fb2d77a91c gnupg-2.2.30.tar.bz2
2de8c54af9387c1068cba06ef23ac197dac8ced0 gnupg-w32-
2.2.30_20210826.tar.xz
f576c2b194c609bfd0386569ef3b51dd2eb38a12 gnupg-w32-
2.2.30_20210826.exe
Internationalization
====================
This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian,
Japanese, Norwegian, Polish, Russian, and Ukrainian being almost
completely translated.
Documentation and Support
=========================
The file gnupg.info has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details available only in thee manual. The manual is also available
online at
https://gnupg.org/documentation/manuals/gnupg/
or can be downloaded as PDF at
https://gnupg.org/documentation/manuals/gnupg.pdf .
You may also want to search the GnuPG mailing list archives or ask on
the gnupg-users mailing list for advise on how to solve problems.
Most
of the new features are around for several years and thus enough
public
experience is available. https://wiki.gnupg.org has user contributed
information around GnuPG and relate software.
In case of build problems specific to this release please first check
https://dev.gnupg.org/T5519 for updated information.
Please consult the archive of the gnupg-users mailing list before
reporting a bug: https://gnupg.org/documentation/mailing-lists.html.
We suggest to send bug reports for a new release to this list in favor
of filing a bug at https://bugs.gnupg.org. If you need commercial
support go to https://gnupg.com or https://gnupg.org/service.html.
If you are a developer and you need a certain feature for your
project,
please do not hesitate to bring it to the gnupg-devel mailing list for
discussion.
Thanks
======
Since 2001 maintenance and development of GnuPG is done by g10 Code
GmbH
and still mostly financed by donations. Three full-time employed
developers as well as two contractors exclusively work on GnuPG and
closely related software like Libgcrypt, GPGME and Gpg4win.
We like to thank all the nice people who are helping the GnuPG
project,
be it testing, coding, translating, suggesting, auditing,
administering
the servers, spreading the word, or answering questions on the mailing
lists.
Many thanks to our numerous financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good and secure shape and to address all the small and larger requests
made by our users. Thanks.
Happy hacking,
Your GnuPG hackers
p.s.
This is an announcement only mailing list. Please send replies only
to
the gnupg-users'at'gnupg.org mailing list.
List of Release Signing Keys:
To guarantee that a downloaded GnuPG version has not been tampered by
malicious entities we provide signature files for all tarballs and
binary versions. The keys are also signed by the long term keys of
their respective owners. Current releases are signed by one or more
of these four keys:
ed25519 2020-08-24 [expires: 2030-06-30]
Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA
Werner Koch (dist signing 2020)
rsa3072 2017-03-17 [expires: 2027-03-15]
Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28
Andre Heinecke (Release Signing Key)
rsa2048 2011-01-12 [expires: 2021-12-31]
Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
Werner Koch (dist sig)
The keys are available at https://gnupg.org/signature_key.html and
in any recently released GnuPG tarball in the file g10/distsigkey.gpg
.
Note that this mail has been signed by a different key.
--
Please read
Nils Melzer: Der Fall Julian Assange
It is really important to know the background of the Assange case to
understand the massive perils to free journalism. The book is right
now only available in German: https://dev.gnupg.org/u/melzerassang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-announce/attachments/20210827/92b21111/attachment.sig>
------------------------------
Subject: Digest Footer
_______________________________________________
Gnupg-announce mailing list
Gnupg-a...@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-announce
------------------------------
End of Gnupg-announce Digest, Vol 67, Issue 1
*********************************************
0 new messages