Re: [Announce] GnuPG 2.1.23 released

2017-08-10 Thread Filipp Gunbin
Sorry for this, these are my local problems with toolchain (binutils vs
macOS command line tools).

Filipp.

On 10/08/2017 17:22 +0300, Filipp Gunbin wrote:

> Compilation fails on macOS:
>
> ..
> Undefined symbols for architecture x86_64:
>   "_compare_filenames", referenced from:
>
> Should I provide more info?

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: [Announce] GnuPG 2.1.23 released

2017-08-10 Thread Filipp Gunbin
Hi, thanks for the release!

Compilation fails on macOS:

..
checking build system type... x86_64-apple-darwin16.6.0
checking host system type... x86_64-apple-darwin16.6.0
..
..
gcc -I/usr/local/include -I/usr/local/include -I/usr/local/include -O3 -Wall 
-Wcast-align -Wshadow -Wstrict-prototypes -Wformat -Wno-format-y2k 
-Wformat-security -W -Wno-sign-compare -Wno-missing-field-initializers 
-Wdeclaration-after-statement -Wlogical-op -Wvla -Wno-pointer-sign 
-Wpointer-arith  -g -O2   -o t-stringhelp t-stringhelp.o  libcommon.a 
-L/usr/local/lib -lgcrypt -lgpg-error -lassuan -L/usr/local/lib -lgpg-error 
-L/usr/local/lib -lgpg-error -L/usr/local/lib -lintl -liconv -lc -Wl,-framework 
-Wl,CoreFoundation -liconv 
ld: warning: ignoring file libcommon.a, file was built for archive which is not 
the architecture being linked (x86_64): libcommon.a
Undefined symbols for architecture x86_64:
  "_compare_filenames", referenced from:
  _main in t-stringhelp.o
  "_compare_version_strings", referenced from:
  _test_compare_version_strings in t-stringhelp.o
.. more similar errors..

Should I provide more info?

Filipp

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: [Announce] GnuPG 2.1.23 released

2017-08-10 Thread Werner Koch
On Thu, 10 Aug 2017 10:25, ine...@gnu.org said:

> I submitted a Russian update on 2017-08-05 to gnupg-i...@gnupg.org,
> but it looks like it was ignored; did I do anything wrong?

My fault sorry.  I should really merge my translations@ and gnupg-i18n@
folders to have only one place to check.

Pushed to master and will thus be part of 2.2.0.

Thanks.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpFxiO96Dv_z.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: [Announce] GnuPG 2.1.23 released

2017-08-10 Thread Ineiev
Hello,

On Wed, Aug 09, 2017 at 05:12:58PM +0200, Werner Koch wrote:
> Internationalization
> 
>
> This version of GnuPG has support for 26 languages with Chinese, Czech,
> French, German, Japanese, Norwegian, Russian, and Ukrainian being almost
> completely translated.  We are now in string freeze for 2.2 and updated
> translations are very welcome.

I submitted a Russian update on 2017-08-05 to gnupg-i...@gnupg.org,
but it looks like it was ignored; did I do anything wrong?


signature.asc
Description: Digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


it's a 2.2.0 release candidate (Re: [Announce] GnuPG 2.1.23 released)

2017-08-09 Thread Bernhard Reiter
(sic!)

> GnuPG: version 2.1.23.  See below for a list of new features and bug
> fixes.  This a release candidate for 2.2.0.

Congratulations GnuPG-Dev-Team!

Bernhard
ps.: With Intevation I'm consider myself part of the extended Dev-Team.

-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


signature.asc
Description: This is a digitally signed message part.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


[Announce] GnuPG 2.1.23 released

2017-08-09 Thread Werner Koch
Hello!

The GnuPG team is pleased to announce the availability of a new release
of GnuPG: version 2.1.23.  See below for a list of new features and bug
fixes.  This a release candidate for 2.2.0.


About GnuPG
=

The GNU Privacy Guard (GnuPG) is a complete and free implementation
of the OpenPGP standard which is commonly abbreviated as PGP.

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.  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.1.23


  * gpg: "gpg" is now installed as "gpg" and not anymore as "gpg2".
If needed, the new configure option --enable-gpg-is-gpg2 can be
used to revert this.

  * gpg: Options --auto-key-retrieve and --auto-key-locate "local,wkd"
are now used by default.  Note: this enables keyserver and Web Key
Directory operators to notice when a signature from a locally
non-available key is being verified for the first time or when
you intend to encrypt to a mail address without having the key
locally.  This new behaviour will eventually make key discovery
much easier and mostly automatic.  Disable this by adding
  no-auto-key-retrieve
  auto-key-locate local
to your gpg.conf.

  * agent: Option --no-grab is now the default.  The new option --grab
allows to revert this.

  * gpg: New import option "show-only".

  * gpg: New option --disable-dirmngr to entirely disable network
access for gpg.

  * gpg,gpgsm: Tweaked DE-VS compliance behaviour.

  * New configure flag --enable-all-tests to run more extensive tests
during "make check".

  * gpgsm: The keygrip is now always printed in colon mode as
documented in the man page.

  * Fixed connection timeout problem under Windows.


A detailed description of the changes found in this 2.1 branch can be
found at .


Getting the Software


Please follow the instructions found at  or
read on:

GnuPG 2.1.23 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
.  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.1.23.tar.bz2 (6374k)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.1.23.tar.bz2.sig

or via FTP:

 ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.23.tar.bz2
 ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.23.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.1.23_20170809.exe (3794k)
 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.23_20170809.exe.sig

or via FTP:

 ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.23_20170809.exe
 ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.23_20170809.exe.sig

The source used to build the Windows installer can be found in the same
directory with a ".tar.xz" suffix.  The Windows installer comes with
TOFU support, many translations, support for Tor, and support for HKPS
and the Web Key Directory.


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.1.23.tar.bz2 you would use this command:

 gpg --verify gnupg-2.1.23.tar.bz2.sig gnupg-2.1.23.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.1.23.tar.bz2, you run the command like this:

 sha1sum gnupg-2.1.23