Re: Using 64-bit gpgme to communicate with 32-bit gpg on Windows ?

[Sébastien Hocquet]

Le 10/04/2015 13:17, Werner Koch a écrit :
> That is quite possible.  The helper is required due to the way Windows
> inherits handles.
>
> I can look at this next week
>
Thank you!

By the way, in case it proves useful for anyone, I've just posted the
scripts I use to build and test GPGME on various platforms:
https://github.com/shocquet/NGpgme/tree/master/gpgme

Have a nice week-end,

Sébastien

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

[Announce] GnuPG 2.1.3 released

[Werner Koch]

Hello!

The GnuPG Project is pleased to announce the availability of the
another release of GnuPG modern: Version 2.1.3.

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.  Since version 2 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 versions of GnuPG are actively maintained:

- GnuPG "modern" (2.1) is the latest development with a lot of new
  features.  This announcement is about the first release of this
  version.

- GnuPG "stable" (2.0) is the current stable version for general use.
  This is what most users are currently using.

- GnuPG "classic" (1.4) is the old standalone version which is most
  suitable for older or embedded platforms.

You may not install "modern" (2.1) and "stable" (2.0) at the same
time.  However, it is possible to install "classic" (1.4) along with
any of the other versions.


Noteworthy changes in version 2.1.3
===

 * gpg: LDAP keyservers are now supported by 2.1.

 * gpg: New option --with-icao-spelling.

 * gpg: New option --print-pka-records.  Changed the PKA method to use
   CERT records and hashed names.

 * gpg: New command --list-gcrypt-config.  New parameter "curve"
   for --list-config.

 * gpg: Print a NEWSIG status line like gpgsm always did.

 * gpg: Print MPI values with --list-packets and --verbose.

 * gpg: Write correct MPI lengths with ECC keys.

 * gpg: Skip legacy PGP-2 keys while searching.

 * gpg: Improved searching for mail addresses when using a keybox.

 * gpgsm: Changed default algos to AES-128 and SHA-256.

 * gpgtar: Fixed extracting files with sizes of a multiple of 512.

 * dirmngr: Fixed SNI handling for hkps pools.

 * dirmngr: extra-certs and trusted-certs are now always loaded from
   the sysconfig dir instead of the homedir.

 * Fixed possible problems due to compiler optimization, two minor
   regressions, and other bugs.

A detailed description of the changes found in the 2.1 versions can be
found at https://gnupg.org/faq/whats-new-in-2.1.html .


Getting the Software


Please follow the instructions found at https://gnupg.org/download/ or
read on:

GnuPG 2.1.3 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.

On ftp.gnupg.org you find these files:

 ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.3.tar.bz2  (4762k)
 ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.3.tar.bz2.sig

This is the GnuPG source code compressed using BZIP2 and its OpenPGP
signature.

An experimental Windows installer for this version will be released next
week.

This version fixes a lot of bugs found after the release of 2.1.2 but
there are still known bugs which we are working on.  Please check the
the bug tracker, https://wiki.gnupg.org, or mailing list archives for
known problems and workaround.


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

 gpg --verify gnupg-2.1.3.tar.bz2.sig gnupg-2.1.3.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 below 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.3.tar.bz2, you would run the command like this:

 sha1sum gnupg-2.1.3.tar.bz2

   and check that the output matches the next line:

091e69ec1ce3f0032e6b135e4da561e8d46d20a7  gnupg-2.1.3.tar.bz2


Release Signing Keys


To guarantee that a downloaded GnuPG version has not been tampered by
malicious enti

Build script problem with gnupg 2.1.3

[Mike Ingle]

I am building gnupg 2.1.3 to try out, and I ran into a bug in the build 
script.

If you run ./configure --help in libgcrypt-1.6.3, it says:

Optional Packages:
 --with-PACKAGE[=ARG]use PACKAGE [ARG=yes]
 --without-PACKAGE   do not use PACKAGE (same as --with-PACKAGE=no)
 --with-pic[=PKGS]   try to use only PIC/non-PIC objects [default=use
 both]
 --with-gnu-ld   assume the C compiler uses GNU ld [default=no]
 --with-sysroot=DIR Search for dependent libraries within DIR
   (or the compiler's sysroot if not specified).
 --with-egd-socket=NAME  Use NAME for the EGD socket)
 --with-capabilities Use linux capabilities [default=no]
 --with-libgpg-error-prefix=PFX
 prefix where GPG Error is installed (optional)

 --with-pth-prefix=PFX   prefix where GNU Pth is installed (optional)

However, the libgpg-error-prefix doesn't actually work. You have to use:
--with-gpg-error-prefix=

Mike

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