|
Size: 2712
Comment: Add DevelopingKleopatra to the "For Developers" List
|
Size: 3362
Comment: writing, better lower case
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| = GnuPG Wiki | Wiki for [[http://gnupg.org|GnuPG]] and [[http://gpg4win.org|Gpg4win]]. Open for related Free Software initiatives. |
| Line 6: | Line 7: |
| 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 |
**The content of this wiki may be different from the positions of the [[https://gnupg.org|GnuPG Project]].** |
| Line 9: | Line 9: |
| * 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. |
**[[Gpg4win|Go to Gpg4win-Section]]** |
| Line 13: | Line 11: |
| 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. |
**[[WKD|Web Key Directory Proposal 2016]]**, email-providers and mail-application-vendors can provide a much better OpenPGP user experience. |
| Line 16: | Line 13: |
| Help us to [[improveThis|improve]] this wiki! | == GnuPG for Users |
| Line 18: | Line 15: |
| == For Users * [[documentation]] |
* [[documentation|Documentation Overview]] |
| Line 34: | Line 29: |
| == For Developers | == GnuPG for Developers |
| Line 36: | Line 31: |
| * How to [[APIs|use GnuPG from your application]]. | * How to [[APIs|use GnuPG from your application]] (~GnuPG's API) |
| Line 54: | Line 49: |
== Gpg4win see [[Gpg4win]] |
* NTBTLS (Not too bad TLS) client library |
| Line 71: | Line 61: |
| * [[https://gnupg.org/conf|OpenPGP.conf]], last conf was 8+9th of Sept, 2016. == About this Wiki The aim of the ~GnuPG Project and the initiative ~Gpg4win is to provide software solutions for everyone to * enable email and file 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. (Which is achieved by publishing them as [[https://fsfe.org/about/basics/freesoftware.en.html|Free Software]].) In 2015 a big challenge for a better user experience for **email and file-transport security** is certificate discovery and trust building. The [[https://g10code.com/steed.html|STEED]] concept proposes a solution. Help us to [[improveThis|improve]] this wiki! |
Wiki for GnuPG and Gpg4win. Open for related Free Software initiatives.
The content of this wiki may be different from the positions of the GnuPG Project.
Web Key Directory Proposal 2016, email-providers and mail-application-vendors can provide a much better OpenPGP user experience.
GnuPG for Users
- Documentation Overview
- 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
GnuPG for Developers
- How to use GnuPG from your application (GnuPG's API)
- 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.
- SignatureHandling
- DevelopingKleopatra
- NTBTLS (Not too bad TLS) client library
Other OpenPGP implementations/initiatives
Planning
- Tasks
- OpenPGPEmailSummits
- OpenPGP.conf, last conf was 8+9th of Sept, 2016.
About this Wiki
The aim of the GnuPG Project and the initiative Gpg4win is to provide software solutions for everyone to
- enable email and file 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. (Which is achieved by publishing them as Free Software.)
In 2015 a big challenge for a better user experience for email and file-transport security is certificate discovery and trust building. The STEED concept proposes a solution.
Help us to improve this wiki!