|
Size: 1230
Comment: Linking APIs
|
Size: 3362
Comment: added new link to WKD. Should be a top link, because it is a proposal for all OpenPGP applications.
|
| 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. | Wiki for [[http://gnupg.org|GnuPG]] and [[http://gpg4win.org|Gpg4win]]. Open for related Free Software initiatives. |
| 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). | **The content of this wiki may be different from the positions of the [[https://gnupg.org|GnuPG Project]].** |
| Line 9: | Line 9: |
| Its all about end-to-end security software where 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. |
**[[Gpg4win|Go to Gpg4win-Section]]** |
| Line 12: | Line 11: |
| 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. | **[[WKD|Web Key Directory Proposal 2016]]**, Email-Providers and Mail-application vendors can provide a much better OpenPGP user experience. |
| Line 14: | Line 13: |
| == GnuPG * PlatformNotes - what to be aware of when using or administrating ~GnuPG on different platforms. |
== GnuPG for Users * [[documentation|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) |
| Line 17: | Line 23: |
| * How to [[APIs|use GnuPG from your application]]. | * [[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 19: | Line 29: |
| == Ggp4win * [[Gpg4win/Wishlist|Wishlist]] * [[press|Gpg4win in the press]] * Project [[Informsec2013]] from April 2013 - September 2013, funded Gpg4win improvements from 2.1.1-beta1 to 2.2.1. |
== GnuPG for Developers |
| Line 24: | Line 31: |
| == Emails and Crypto | * How to [[APIs|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. ** [[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]]. 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. |
| Line 26: | Line 48: |
| * [[MailClients/Screenshots]] |
* DevelopingKleopatra * NTBTLS (Not too bad TLS) client library == Other OpenPGP implementations/initiatives * [[OtherFreeSoftwareOpenPGP]] * [[OtherFreeSoftwareInitiatives]] == Planning * [[Tasks]] * [[OpenPGPEmailSummits]] * [[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!