GnuPG Made Easy. NOTE: Maintainers are not tracking this mirror. Do not make pull requests here, nor comment any commits, submit them usual way to bug tracker (https://www.gnupg.org/documentation/bts.html) or to the mailing list (https://www.gnupg.org/documentation/mailing-lists.html).
Go to file
Marcus Brinkmann ed8c52941c 2010-11-19 Marcus Brinkmann <mb@g10code.com>
* engine-gpgconf.c (_gpgme_conf_opt_change): Support
	self-assignment.  Requested by Marc Mutz.
2010-11-19 16:06:43 +00:00
complus Fixes for building without gpgsm and for W32 2007-01-08 12:05:07 +00:00
contrib 2010-11-15 Marcus Brinkmann <mb@g10code.com> 2010-11-15 15:29:17 +00:00
doc Add option GPGME_EXPORT_MODE_MINIMAL 2010-02-16 20:07:03 +00:00
lang 2008-11-08 Moritz <moritz@gnu.org> 2008-11-23 18:09:57 +00:00
m4 Better detection of a missing libassuan 2010-05-07 23:22:38 +00:00
src 2010-11-19 Marcus Brinkmann <mb@g10code.com> 2010-11-19 16:06:43 +00:00
tests Prepare for a new protocol. 2009-11-03 20:27:35 +00:00
acinclude.m4 * acinclude.m4 (GNUPG_CHECK_VA_COPY): Assume no when cross-compiling. 2005-03-09 16:03:05 +00:00
AUTHORS Add new types to the gpgconf interface. 2008-06-19 17:37:31 +00:00
autogen.sh First take on changes to allow building with MSC for W32CE. 2010-11-02 16:27:46 +00:00
ChangeLog More include guards. 2010-11-03 09:56:27 +00:00
compile Added files usually installed bu automake. We want to keep them in the CVS 2004-01-12 13:49:11 +00:00
config.guess Update automake scripts. 2008-07-04 15:46:01 +00:00
config.sub Update automake scripts. 2008-07-04 15:46:01 +00:00
configure.ac More include guards. 2010-11-03 09:56:27 +00:00
COPYING Added files usually installed bu automake. We want to keep them in the CVS 2004-01-12 13:49:11 +00:00
COPYING.LESSER 2004-12-07 Marcus Brinkmann <marcus@g10code.de> 2004-12-07 21:13:39 +00:00
depcomp Update automake scripts. 2008-07-04 15:46:01 +00:00
gpgme.spec.in 2004-12-07 Marcus Brinkmann <marcus@g10code.de> 2004-12-07 21:13:39 +00:00
gpgme.txt Update the information before release, for what it's worth. 2004-09-30 01:44:17 +00:00
INSTALL Update automake scripts. 2008-07-04 15:46:01 +00:00
install-sh Update automake scripts. 2008-07-04 15:46:01 +00:00
ltmain.sh 2010-05-06 Marcus Brinkmann <marcus@g10code.de> 2010-05-06 14:49:43 +00:00
Makefile.am 2009-10-20 Marcus Brinkmann <marcus@g10code.de> 2009-10-20 15:39:15 +00:00
missing Update automake scripts. 2008-07-04 15:46:01 +00:00
mkinstalldirs Update automake scripts. 2008-07-04 15:46:01 +00:00
NEWS 2010-08-18 Marcus Brinkmann <marcus@g10code.de> 2010-08-18 14:14:27 +00:00
README 2010-05-06 Marcus Brinkmann <marcus@g10code.de> 2010-05-06 13:39:55 +00:00
README.SVN Fixed a W32bug in rungpg.c 2007-09-17 10:21:20 +00:00
THANKS More changes for W32CE with MSC. 2010-11-04 08:16:57 +00:00
TODO 2009-11-10 Marcus Brinkmann <marcus@g10code.de> 2009-11-10 09:07:19 +00:00

                  GPGME - GnuPG Made Easy
                ---------------------------

               Copyright 2004, 2006, 2010 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
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
require small portability fixes, send us your patches.

See the file COPYING.LESSER and each file for copyright and warranty
information.


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!

To build GPGME, you need to install libgpg-error.  You need at least
libgpg-error 1.8.

For support of the OpenPGP protocol (default), you should use the
latest version of GnuPG 1.2 or 1.4, available at:
ftp://ftp.gnupg.org/gcrypt/gnupg/

You need at least GnuPG 1.2.2.

If configure can't find the `gpg' binary in your path, you can specify
the location with the --with-gpg=/path/to/gpg argument to configure.

For support of the CMS (Cryptographic Message Syntax) protocol, you
need the latest CVS version of GnuPG 1.9, which is available in the
GnuPG repository:
http://www.gnupg.org/download/cvs_access.html
Use the tag `GNUPG-1-9-BRANCH'.  There are also snapshots available at:
ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/

You need at least GpgSM 1.9.6.

If configure can't find the `gpgsm' binary in your path, you can
specify the location with the --with-gpgsm=/path/to/gpgsm argument to
configure.

For building the CVS version of GPGME please see the file README.CVS
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

   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:

   "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@gnu.org>"
   "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:

	$ gpg --fingerprint 0x57548DCD

   with the fingerprint 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.


Documentation
---------------

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.

Please subscribe to the gnupg-devel@gnupg.org mailing list if you want
to do serious work.