|
Size: 2810
Comment: Improve text.
|
Size: 2896
Comment: formatto
|
| 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! |
//([[about|About this wiki]])// |
| Line 8: | Line 6: |
| GnuPG: | **[[Gpg4win|-> Gpg4win-Section]]** |
| Line 10: | Line 8: |
| * 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. |
**[[WKD| -> Web Key Directory]]**, which makes exchanging crypto mails much easier. |
| Line 14: | Line 10: |
| 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. | == Notable Events * Gpg4win 3.0 upcoming, [[https://wiki.gnupg.org/Gpg4win/Testversions|try the latest release candidate]], see [[Gpg4win/Roadmap|roadmap]]. * GnuPG 2.2 upcoming (end of August or early September 2017?) [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000412.html|GnuPG 2.1.23 is a release candidate for 2.2]] |
| Line 16: | Line 15: |
| == Documentation | * 31.12.2017: End of Life for ~GnuPG 2.0.x. (So you really want to take ~GnuPG and Gpg4win release candidates for a spin.) |
| Line 18: | Line 17: |
| * LargeKeys? * TroubleShooting |
== GnuPG for Users |
| Line 21: | Line 19: |
| == GnuPG |
* [[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. |
| Line 26: | Line 27: |
| * [[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]] * [[AgentForwarding|How to use local secrets on a remote machine]] |
| Line 28: | Line 34: |
| === For Software-Developers | == GnuPG for Developers |
| Line 30: | Line 36: |
| * How to [[APIs|use GnuPG from your application]]. | * How to [[APIs|use GnuPG from your application]] (~GnuPG's API) |
| Line 32: | Line 38: |
==== 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 52: |
| == Ggp4win {{image:gpg4win-logo-400px.png}} |
* SignatureHandling * DevelopingKleopatra * NTBTLS (Not too bad TLS) client library |
| Line 56: | Line 56: |
| * [[Gpg4win/Roadmap|Roadmap]] * [[Gpg4win/Wishlist|Wishlist]] * 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). * [[press|Gpg4win in the press]] * Building the installer [[Gpg4win/build|Build]] |
|
| Line 63: | Line 57: |
| == Emails and Crypto * SignatureHandling * [[MailClients/Screenshots]] == Applications using GnuPG * [[Applications]] == Other OpenPGP implementations/initatives |
== Other OpenPGP implementations/initiatives |
| Line 80: | Line 65: |
| * [[GnuPGSummit]] | * [[OpenPGPEmailSummits]] * [[https://gnupg.org/conf|OpenPGP.conf]], last conf was 8+9th of Sept, 2016. |
-> Web Key Directory, which makes exchanging crypto mails much easier.
Notable Events
- Gpg4win 3.0 upcoming, try the latest release candidate, see roadmap.
- GnuPG 2.2 upcoming (end of August or early September 2017?) GnuPG 2.1.23 is a release candidate for 2.2
- 31.12.2017: End of Life for GnuPG 2.0.x. (So you really want to take GnuPG and Gpg4win release candidates for a spin.)
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
- How to use local secrets on a remote machine
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.