Skip to content
C C++ TeX Shell Python JavaScript Other
Branch: master
Clone or download

Latest commit

NIIBE Yutaka
NIIBE Yutaka tests: Add ECC key generation for tests/gpgsm.
* tests/gpgsm/t-genkey.c (check_result): New.

Signed-off-by: NIIBE Yutaka <>
Latest commit 3658e2d Mar 27, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux doc: use https:// for Oct 18, 2018
conf Release 1.12.0 Oct 8, 2018
doc core: New context flags "include-key-block" and "auto-key-import". Mar 17, 2020
lang python: fix minor typo in howto Mar 3, 2020
m4 python: Also detect python 3.9. Feb 14, 2020
src build: Fix library dependency. Mar 27, 2020
tests tests: Add ECC key generation for tests/gpgsm. Mar 27, 2020
.gitignore build: Let configure create the VERSION file. Oct 10, 2018
AUTHORS Add SPDX identifiers to most source files Nov 16, 2018
COPYING Added files usually installed bu automake. We want to keep them in th… Jan 12, 2004
COPYING.LESSER 2004-12-07 Marcus Brinkmann <> Dec 7, 2004
ChangeLog Generate the ChangeLog from commit logs. Dec 2, 2011
ChangeLog-2011 Generate the ChangeLog from commit logs. Dec 2, 2011
INSTALL Update automake scripts. Jul 4, 2008 Add SPDX identifiers to most source files Nov 16, 2018
NEWS qt: Change logging category Feb 19, 2020
README doc: Update copyright years and change two URLs. Apr 18, 2018
README.GIT Release 1.3.2. May 2, 2012
THANKS move some file encodings to UTF-8 Sep 23, 2016
TODO spelling: fix misspellings Nov 8, 2018
acinclude.m4 Spelling fixes for comments and doc Dec 8, 2017
autogen.rc build: Remove --with-*-prefix, which is no need any more. Dec 4, 2018 build: Let configure create the VERSION file. Oct 10, 2018 python: Also detect python 3.9. Feb 14, 2020 doc: convert more links to equivalent https:// URLs Oct 18, 2018
gpgme.txt doc: convert more links to equivalent https:// URLs Oct 18, 2018
missing Update automake scripts. Jul 4, 2008


                       GPGME - GnuPG Made Easy

Copyright 2001-2018 g10 Code GmbH

This file is free software; as a special exception the author gives
unlimited permission to copy and/or distribute it, with or without
modifications, as long as this notice is preserved.

This file is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY, to the extent permitted by law; without even the


GnuPG Made Easy (GPGME) is a C language library that allows to add
support for cryptography to a program.  It is designed to make access
to public key crypto engines like GnuPG or GpgSM easier for
applications.  GPGME provides a high-level crypto API for encryption,
decryption, signing, signature verification and key management.

GPGME comes with language bindings for Common Lisp, C++, QT, Python2,
and Python 3.

GPGME uses GnuPG as its backend to support OpenPGP and the
Cryptographic Message Syntax (CMS).

See the files COPYING, COPYING.LESSER, and each file for copyright and
warranty information.  The file AUTHORS has a list of authors and
useful web and mail addresses.


See the file INSTALL for generic installation instructions.

Check that you have unmodified sources.  See below on how to do this.
Don't skip it - this is an important step!

To build GPGME, you need to install libgpg-error (>= 1.24) and
Libassuan (>= 2.4.2).

For support of the OpenPGP and the CMS protocols, you should use the
latest version of GnuPG (>= 2.1.18) , available at:

For building the Git version of GPGME please see the file README.GIT
for more information.

How to Verify the Source

In order to check that the version of GPGME which you are going to
install is an original and unmodified one, you can do it in one of the
following ways:

a) If you have a trusted Version of GnuPG installed, you can simply check
   the supplied signature:

	$ gpg --verify gpgme-x.y.z.tar.gz.sig gpgme-x.y.z.tar.gz

   This checks that the detached signature gpgme-x.y.z.tar.gz.sig is
   indeed a a signature of gpgme-x.y.z.tar.gz.  The key used to create
   this signature is at least one of:

     rsa2048 2011-01-12 [expires: 2019-12-31]
     Key fingerprint = D869 2123 C406 5DEA 5E0F  3AB5 249B 39D2 4F25 E3B6
     Werner Koch (dist sig)

     rsa2048 2014-10-29 [expires: 2019-12-31]
     Key fingerprint = 46CC 7308 65BB 5C78 EBAB  ADCF 0437 6F3E E085 6959
     David Shaw (GnuPG Release Signing Key) <dshaw 'at'>

     rsa2048 2014-10-29 [expires: 2020-10-30]
     Key fingerprint = 031E C253 6E58 0D8E A286  A9F2 2071 B08A 33BD 3F06
     NIIBE Yutaka (GnuPG Release Key) <gniibe 'at'>

     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)

   The keys are available at <>
   and in released GnuPG tarballs in the file g10/distsigkey.gpg .
   You have to make sure that these are really the desired keys and
   not faked one.  You should do this by comparing the fingerprints
   with the fingerprints published elsewhere.

b) If you don't have any of the above programs, you have to verify
   the SHA1 checksum:

	$ sha1sum gpgme-x.y.z.tar.gz

   This should yield an output _similar_ to this:

   fd9351b26b3189c1d577f0970f9dcadc3412def1  gpgme-x.y.z.tar.gz

   Now check that this checksum is _exactly_ the same as the one
   published via the announcement list and probably via Usenet.


For information how to use the library you can read the info manual,
which is also a reference book, in the doc/ directory.  The programs
in the tests/ directory may also prove useful.

Please subscribe to the mailing list if you want
to do serious work.

For hacking on GPGME, please have a look at doc/HACKING.
You can’t perform that action at this time.