add link to ruby binding
|Deletions are marked like this.||Additions are marked like this.|
|Line 34:||Line 34:|
|* [[https://bitbucket.org/malb/pyme|pyme]] ~SWIG generated wrapper (continuation of the [[http://pyme.sourceforge.net/|old version]])|| * [[https://bitbucket.org/malb/pyme|pyme]] ~SWIG generated wrapper for python2 (continuation of the [[http://pyme.sourceforge.net/|old version]])
* [[http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=shortlog;h=refs/heads/pyme|pyme for python3]] ~SWIG generated wrapper for python3, port of pyme 0.9 (see gnupg-devel mailinglist 2015-05 and newer)
|Line 36:||Line 37:|
== Ruby wrappers ==
* [[https://github.com/ueno/ruby-gpgme|ruby-gpgme]] is a ruby wrapper, which can be installed with: gem install gpgme.
GPGME - an API to GnuPG
The recommended way to use the GnuPG crypto stack from your application is GPGME, which is written in C. Here is the online version of the manual (maybe out of date).
A number of binding for other programming languages/environments exist: Below is an incomplete list:
All / C
- gpgme (GPG Made Easy) is the official GnuPG API. It is implemented in C itself, but this is what you should use from your language as well.
- http://quickgit.kde.org/?p=kdepimlibs.git gpgme++ is a wrapper for gpgme in kdepimlibs
C# (c-sharp) wrappers
- gpgme-sharp in alpha for 32bit windows (as of 2014-09).
- GnuPG-for-Java is a Java wrapper for gpgme >=1.5 and GnuPG >=2.x
- GnuPG-for-Java is a Java wrapper for gpgme and GnuPG 1.x
- Gnu Privacy Guard is an Android app based GnuPG-for-Java and gpgme to provide a GnuPG engine in Android
- pyme SWIG generated wrapper for python2 (continuation of the old version)
- pyme for python3 SWIG generated wrapper for python3, port of pyme 0.9 (see gnupg-devel mailinglist 2015-05 and newer)
- https://launchpad.net/pygpgme manually written wrapper in C
- ruby-gpgme is a ruby wrapper, which can be installed with: gem install gpgme.
(not recommended) calling executables directly
A number of elder applications call GnuPG executables in a subprocess and interact with them via command line arguments and file-descriptors. This is less perferable to GPGME, because the command line arguments and text outputs are not an (official) API to GnuPG. While there is an effort made to keep them stable, using the official GPGME API can manage this more precisely and thus you end up with a more robust solution.