|
Size: 2810
Comment: Improve text.
|
Size: 3174
Comment: added link to Gpg4all
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| This is the official Wiki for [[http://gnupg.org|GnuPG]], the GNU Privacy Guard, and all ~GnuPG related Free Software initiatives, e.g., [[http://gpg4win.org|Gpg4win]] (~GnuPG for windows). The aim of this Wiki is to help users and contributors by providing a central place for [[documentation]], links to references and planning. We welcome your contribution! |
This is the official Wiki for [[http://gnupg.org|GnuPG]], the GNU Privacy Guard, and all related Free Software initiatives like [[http://gpg4win.org|Gpg4win]]. Their aim is to produce software solutions to |
| Line 8: | Line 7: |
| GnuPG: | * enable end-to-end security, **offering protection against being listened to by servers or transport systems**. * use openly researched crypto algorithms. * allow the implementations to be independently audited. |
| Line 10: | Line 11: |
| * enables end-to-end security without **the user having to trust a third party server or transport system.** * uses openly researched crypto algorithms. * is free software and, as such, the implementation can be independently audited. |
The next big user experience boost for **email and file-transport security** would be the adoption of the [[https://g10code.com/steed.html|STEED]] concept. |
| Line 14: | Line 14: |
| The next big user experience boost for email security would be the adoption of the [[https://g10code.com/steed.html|STEED]] concept. Help us make it happen. | This Wiki is about helping users and contributors by providing a central place for [[documentation]], links to references and planning. We welcome your contribution! |
| Line 16: | Line 17: |
| == Documentation | = For Users |
| Line 18: | Line 19: |
| * LargeKeys? * TroubleShooting == GnuPG |
* LargeKeys: How many bits are enough? * WebOfTrust: Understanding the web of trust * GnomeKeyring: What to do when Gnome Keyring Hijacks your GPG Agent * TroubleShooting: What to do when something doesn't work. |
| Line 26: | Line 26: |
| * [[Wishlist]] | * [[Wishlist]] Where to submit feature requests * [[Applications]] using GnuPG * [[MailClients/Screenshots]] * LDAPKeyserver: How to configure [[https://en.wikipedia.org/wiki/OpenLDAP|OpenLDAP]] as a keyserver. * Hints for use with [[NFS]] |
| Line 28: | Line 32: |
| === For Software-Developers | = For Developers |
| Line 32: | Line 36: |
==== Building GnuPG 2.1 GnuPG 2.1 is the latest GnuPG version but as with all 2.x versions it has several dependencies, which make building it a bit more difficult. Here are some notes. * [[Build2.1_Unix|Building for Unix]] * [[Build2.1_Windows|Building for Windows]] ==== Various links This is a collection of links: * [[http://upstream-tracker.org/|Upstream-Tracker.org]] checks ABI/API changes for some libraries like [[http://upstream-tracker.org/versions/gpgme.html|gpgme]], [[http://upstream-tracker.org/versions/libgpg-error.html|libgpg-error]], [[http://upstream-tracker.org/versions/libgcrypt.html|libgcrypt]]. |
* Building GnuPG 2.1: GnuPG 2.1 is the latest GnuPG version but as with all 2.x versions it has several dependencies, which make building it a bit more difficult. Here are some notes. ** [[Build2.1_Unix|Building for Unix]] ** [[Build2.1_Windows|Building for Windows]] ** [[https://github.com/guardianproject/gnupg-for-android#build-setup|Building for Android]] * API checker: [[http://upstream-tracker.org/|Upstream-Tracker.org]] checks ABI/API changes for some libraries like [[http://upstream-tracker.org/versions/gpgme.html|gpgme]], [[http://upstream-tracker.org/versions/libgpg-error.html|libgpg-error]], [[http://upstream-tracker.org/versions/libgcrypt.html|libgcrypt]]. |
| Line 53: | Line 50: |
| == Ggp4win | * SignatureHandling ---- = Gpg4win |
| Line 60: | Line 61: |
| * Contract [[Gpg4all]] from October 2015 - | |
| Line 61: | Line 63: |
| * Building the installer [[Gpg4win/build|Build]] | * [[Gpg4win/build|Building the installer]] |
| Line 63: | Line 65: |
| == Emails and Crypto | |
| Line 65: | Line 66: |
| * SignatureHandling * [[MailClients/Screenshots]] == Applications using GnuPG * [[Applications]] == Other OpenPGP implementations/initatives |
== Other OpenPGP implementations/initiatives |
This is the official Wiki for GnuPG, the GNU Privacy Guard, and all related Free Software initiatives like Gpg4win. Their aim is to produce software solutions to
- enable end-to-end security, offering protection against being listened to by servers or transport systems.
- use openly researched crypto algorithms.
- allow the implementations to be independently audited.
The next big user experience boost for email and file-transport security would be the adoption of the STEED concept.
This Wiki is about helping users and contributors by providing a central place for documentation, links to references and planning. We welcome your contribution!
For Users
- LargeKeys: How many bits are enough?
- WebOfTrust: Understanding the web of trust
- GnomeKeyring: What to do when Gnome Keyring Hijacks your GPG Agent
- TroubleShooting: What to do when something doesn't work.
- PlatformNotes - what to be aware of when using or administrating GnuPG on different platforms.
- X.509 hints (needed for S/MIME and trusted root certs)
- SmartCard hints
- Wishlist Where to submit feature requests
- Applications using GnuPG
- MailClients/Screenshots
- LDAPKeyserver: How to configure OpenLDAP as a keyserver.
- Hints for use with NFS
For Developers
- How to use GnuPG from your application.
- BuildingFromGIT
- Building GnuPG 2.1: GnuPG 2.1 is the latest GnuPG version but as with all 2.x versions it has several dependencies, which make building it a bit more difficult. Here are some notes.
- API checker: Upstream-Tracker.org checks ABI/API changes for some libraries like gpgme, libgpg-error, libgcrypt.
Note that the tools can't necessary decide whether something is an ABI or API change. The output should be used as a hint to look for whether there might be a problem. We are not aware of any broken API or ABI contracts for the listed libraries.
Gpg4win
- Roadmap
- Wishlist
- Future Development means for ImprovingSecurity
- Project Informsec2013 funded Gpg4win improvements from April 2013 - September 2013 (from 2.1.1-beta1 to 2.2.1).
- Contract Gpg4all from October 2015 -
- Gpg4win in the press
- Building the installer