|
Size: 1381
Comment: subpage for Other FreeSoftware OpenPGP implementations
|
Size: 3128
Comment: Rewrote the introduction paragraph, to be slightly shorter and to be more clear about what end-to-end security aims to offer.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #acl TrustedEditorGroup:read,write,delete,revert All:read | |
| Line 5: | Line 4: |
| Secure file and email exchange! Usable for everyone without licensing fees. Transparent with source code using Open Standards. | 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 7: | Line 7: |
| This is the wiki of [[http://gnupg.org|GnuPG]] and all ~GnuPG related Free Software initiatives, e.g. [[http://gpg4win.org|Gpg4win]] (~GnuPG for windows). | * 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, by being Free Software. |
| Line 9: | Line 11: |
| Its all about end-to-end security software **you do not have to trust a (third party) server** or transport system. It uses openly researched crypto algorithms. The implementations can be independently verified. |
The next big user experience boost for email security would be the adoption of the [[https://g10code.com/steed.html|STEED]] concept. |
| Line 13: | Line 13: |
| 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 15: | Line 16: |
| == GnuPG * PlatformNotes - what to be aware of when using or administrating ~GnuPG on different platforms. * [[X.509]] hints |
= 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) |
| Line 19: | Line 25: |
| === for Software-Developers | * [[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]] = For Developers |
| Line 21: | Line 34: |
| * BuildingFromGIT | * 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. ** [[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 23: | Line 44: |
| == Ggp4win | 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. * SignatureHandling ---- = Gpg4win {{image:gpg4win-logo-400px.png}} * [[Gpg4win/Roadmap|Roadmap]] |
| Line 25: | Line 58: |
| * Future Development means for [[Gpg4win/ImprovingSecurity|ImprovingSecurity]] * Project [[Informsec2013]] funded Gpg4win improvements from April 2013 - September 2013 (from 2.1.1-beta1 to 2.2.1). |
|
| Line 26: | Line 61: |
| * Project [[Informsec2013]] from April 2013 - September 2013, funded Gpg4win improvements from 2.1.1-beta1 to 2.2.1. | * [[Gpg4win/build|Building the installer]] |
| Line 28: | Line 63: |
| == Emails and Crypto * SignatureHandling * [[MailClients/Screenshots]] |
|
| Line 32: | Line 64: |
| == Other OpenPGP implementations/initatives | == Other OpenPGP implementations/initiatives |
| Line 34: | Line 67: |
| * [[OtherFreeSoftwareInitiatives]] == Planning * [[Tasks]] * [[GnuPGSummit]] |
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, by being Free Software.
The next big user experience boost for email 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).
- Gpg4win in the press
- Building the installer