wiki:gnupg

GnuPG

  1. GnuPG
    1. Installation
    2. Building Instructions
    3. History
    4. Binary Download
        1. Prerequisites
        2. GNUPG
    5. Reporting Bugs
    6. Credits

GnuPG is the GNU project's complete and free implementation of the OpenPGP standard as defined by RFC4880. !GnuPG allows to encrypt and sign your data and communication, features a versatile key management system as well as access modules for all kinds of public key directories. GnuPG, also known as GPG, is a command line tool with features for easy integration with other applications. A wealth of frontend applications and libraries are available.

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.

Further information can be found ​here

Installation

Preliminary, as provided by Tobias Huerlimann.

GnuPG has been configured to assume that a unixish file hierarchy exists, where it looks for its files. The environment variable UNIXROOT is used to determine in which directory that hierarchy is located. To install GnuPG you just have to extract the binary archive in the directory that UNIXROOT points to. More information about that file hierarchy and the env var UNIXROOT can be found at the UnixOS2 site.

GnuPG also needs the environment varibale HOME, which determines where GnuPG saves its keyrings. And at least one of the two possible PRNG (Pseudo Random Number Generators), rndos2.dll or RexxEGD, has to be installed.

The following environment variables are used by GnuPG:

  • HOME HOME points to the user's home directory. GnuPG stores the personal options and keys in the subdirectory ".gnupg". If you do not have a home dir, you may choose C: for example:

SET HOME=C:

  • UNIXROOT The env var UNIXROOT should point to the directory, in which a unixish filesystem hierarchy exists. Example: set UNIXROOT to G: and gpg.exe will be located in G:\usr\bin

SET UNIXROOT=G:

  • LANG LANG should already exist at most OS/2 installations because it is also used be OS/2 itself.

It is used to determine the language GnuPG will use. Example: if you want GnuPG to 'speak' italian, you set:

SET LANG=it

Here's a summary of the directories that are used by GnuPG:

  • %HOME%/.gnupg/ If this directory does not exist, it will be created the first time GnuPG starts. Then GnuPG tries to create the personal configuration file "gpg.conf" by copying %UNIXROOT%/usr/share/gnupg/options.skel. %HOME%/.gnupg/ is also used to story the created and imported keys.
  • %UNIXROOT%/usr/lib/gnupg/ In this directory GnuPG looks for the random number generator "rndos2.dll" and plug-ins (i.e.: the IDEA plug-in).
  • %UNIXROOT%/usr/share/gnupg/ In this directory GnuPG looks for the file "options.skel", which is used as a template for %HOME%/.gnupg/gpg.conf.
  • %UNIXROOT%/usr/share/locale/ GnuPG expects the locale files (for NLS) in that directory. The files are in der LC_MESSGAES/<language> subdirectory. <language> is determined by the LANG env var.

In case you really do not like the idea of UNIXROOT and you rather like the OS/2 way: Create a directory for GnuPG, for example C:\Progs\GnuPG and copy the following files in that directory:

  • usr/bin/gpg.exe
  • usr/bin/gpgv.exe
  • usr/bin/gpgsplit.exe
  • usr/lib/gnupg/rndos2.dll
  • usr/share/book/gpg.inf
  • usr/share/gnupg/FAQ
  • Optional: plug-in DLLs

Not using a unixish file hierarchy imposes some minor limitations. For example, NLS requires such a hierarchy. In any case you should set the HOME variable.

Building Instructions

History

Binary Download

Prerequisites

GCC 4 Core Libraries​WPIGCC 4 runtime libraries

GNUPG

GnuPG 1.4.9​ZIP1.4.9 build

Reporting Bugs

Reporting bugs and requesting new features is done through the ticket system. You can view existing tickets, add comments to them and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for this task already created.

Anonymous access to the ticket system has been restricted due to multiple attacks of stupid spammers we've been suffering from lately. In order to create a new ticket or comment the existing one, you need to login with your Netlabs login id. If you do not have a login id, you can request one at ​http://www.netlabs.org/en/site/member/member.xml. We are sorry for inconvenience, but at the present time this is the only way to avoid extremely annoying spam.

Credits

  • Tobias Huerlimann
  • Herwig Bauernfeind
  • Silvan Scherrer
  • all the ppl working on GNUPG
  • netlabs.org (hosting & support)
Last modified 8 years ago Last modified on Jun 26, 2016, 12:26:10 PM
Note: See TracWiki for help on using the wiki.