2000-10-27 14:55:24 +00:00
|
|
|
GPGME - GnuPG Made Easy
|
|
|
|
---------------------------
|
|
|
|
|
2015-04-13 13:43:13 +00:00
|
|
|
Copyright 2004, 2006, 2010, 2012, 2013, 2014, 2015 g10 Code GmbH
|
2004-09-30 02:37:13 +00:00
|
|
|
|
|
|
|
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
|
|
|
|
implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
|
|
|
|
PURPOSE.
|
|
|
|
|
|
|
|
|
|
|
|
Introduction
|
|
|
|
--------------
|
|
|
|
|
|
|
|
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 uses GnuPG and GpgSM as its backends to support OpenPGP and the
|
|
|
|
Cryptographic Message Syntax (CMS).
|
|
|
|
|
|
|
|
GPGME runs best on GNU/Linux or *BSD systems. Other Unices may
|
2013-02-26 16:28:04 +00:00
|
|
|
require small portability fixes, please send us your patches.
|
2004-09-30 02:37:13 +00:00
|
|
|
|
2013-02-26 16:28:04 +00:00
|
|
|
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.
|
2004-09-30 02:37:13 +00:00
|
|
|
|
|
|
|
|
|
|
|
Installation
|
|
|
|
--------------
|
|
|
|
|
|
|
|
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!
|
|
|
|
|
2013-12-27 15:08:20 +00:00
|
|
|
To build GPGME, you need to install libgpg-error (>= 1.11) and
|
2012-05-02 08:58:52 +00:00
|
|
|
Libassuan (>= 2.0.2).
|
2003-06-06 03:04:09 +00:00
|
|
|
|
2004-09-30 01:30:28 +00:00
|
|
|
For support of the OpenPGP protocol (default), you should use the
|
2012-05-02 08:58:52 +00:00
|
|
|
latest version of GnuPG (>= 1.4) , available at:
|
2014-05-21 07:08:42 +00:00
|
|
|
ftp://ftp.gnupg.org/gcrypt/gnupg/. For support of the CMS
|
|
|
|
(Cryptographic Message Syntax) protocol and lot of other features, you
|
2012-05-02 08:58:52 +00:00
|
|
|
need a GnuPG version >= 2.0.
|
2000-11-16 17:26:53 +00:00
|
|
|
|
2012-05-02 08:58:52 +00:00
|
|
|
For building the GIT version of GPGME please see the file README.GIT
|
2004-09-30 01:30:28 +00:00
|
|
|
for more information.
|
|
|
|
|
2004-09-30 02:37:13 +00:00
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
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 either of:
|
|
|
|
|
2012-03-27 19:10:00 +00:00
|
|
|
"pub 2048R/4F25E3B6 2011-01-12 Werner Koch (dist sig)"
|
2004-09-30 02:37:13 +00:00
|
|
|
"pub 1024D/87978569 1999-05-13
|
|
|
|
Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>
|
|
|
|
Marcus Brinkmann <mb@g10code.com>"
|
|
|
|
|
|
|
|
If you do not have this key, you can get it from any keyserver. You
|
|
|
|
have to make sure that this is really the key and not a faked one.
|
|
|
|
You can do this by comparing the output of:
|
|
|
|
|
2012-03-27 19:10:00 +00:00
|
|
|
$ gpg --fingerprint 0x4F25E3B6
|
2004-09-30 02:37:13 +00:00
|
|
|
|
|
|
|
with the fingerprint published elsewhere.
|
|
|
|
|
|
|
|
b) If you don't have any of the above programs, you have to verify
|
2005-01-12 10:28:42 +00:00
|
|
|
the SHA1 checksum:
|
2004-09-30 02:37:13 +00:00
|
|
|
|
2005-01-12 10:28:42 +00:00
|
|
|
$ sha1sum gpgme-x.y.z.tar.gz
|
2004-09-30 02:37:13 +00:00
|
|
|
|
|
|
|
This should yield an output _similar_ to this:
|
|
|
|
|
2005-01-12 10:28:42 +00:00
|
|
|
fd9351b26b3189c1d577f0970f9dcadc3412def1 gpgme-x.y.z.tar.gz
|
2004-09-30 02:37:13 +00:00
|
|
|
|
|
|
|
Now check that this checksum is _exactly_ the same as the one
|
|
|
|
published via the announcement list and probably via Usenet.
|
|
|
|
|
|
|
|
|
|
|
|
Documentation
|
|
|
|
---------------
|
|
|
|
|
2004-09-30 01:30:28 +00:00
|
|
|
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/gpg/ directory may also prove useful.
|
2000-11-16 17:26:53 +00:00
|
|
|
|
2001-11-23 01:12:04 +00:00
|
|
|
Please subscribe to the gnupg-devel@gnupg.org mailing list if you want
|
|
|
|
to do serious work.
|
2012-09-25 17:19:13 +00:00
|
|
|
|
|
|
|
For hacking on GPGME, please have a look at doc/HACKING.
|