|
Size: 2729
Comment: Structural improvement, the Gpg4win subsite needs to be more prominently placed
|
Size: 3026
Comment: adds qualifier for TroubleShooting
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| = GnuPG Wiki | //([[about|About this wiki]])// |
| Line 6: | Line 6: |
| 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 |
**[[Gpg4win|-> Gpg4win-Section]]** |
| Line 9: | Line 8: |
| * 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. |
**[[WKD| -> Web Key Directory and Service]]**, which makes exchanging crypto mails much easier. |
| Line 13: | Line 10: |
| 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. |
== Notable Events * 2017-12-31: End of Life for ~GnuPG 2.0.x. (So you really want to take ~GnuPG 2.2 or Gpg4win 3.0 for a spin.) * 2017-09-21: [[https://www.gpg4win.org/version3.html|Gpg4win 3.0 released]], includes MIME capable Outlook-Add-in, GnuPG 2.2, [[WKD]]-requests and update notifications. * 2017-08-28: [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000413.html|GnuPG 2.2 released]], comes with ECC and does "web key directory" requests by default. |
| Line 16: | Line 17: |
| Help us to [[improveThis|improve]] this wiki! **[[Gpg4win|Go to Gpg4win-Section]]** |
|
| Line 22: | Line 20: |
| * [[documentation]] | * [[documentation|Documentation Overview]] |
| Line 26: | Line 24: |
| * TroubleShooting: What to do when something doesn't work. | * TroubleShooting: What to do when something doesn't work (mainly on Windows for Gpg4win) |
| Line 32: | Line 30: |
| * [[Tools]] that may help running or administrating GnuPG or Gpg4win | |
| Line 35: | Line 34: |
| * [[AgentForwarding|How to use local secrets on a remote machine]] | |
| Line 38: | Line 38: |
| * How to [[APIs|use GnuPG from your application]]. | * How to [[APIs|use GnuPG from your application]] (~GnuPG's API) |
| Line 56: | Line 56: |
| * NTBTLS (Not too bad TLS) client library | |
| Line 67: | Line 68: |
| * [[https://gnupg.org/conf|OpenPGP.conf]], last conf was 8+9th of Sept, 2016. |
-> Web Key Directory and Service, which makes exchanging crypto mails much easier.
Notable Events
- 2017-12-31: End of Life for GnuPG 2.0.x. (So you really want to take GnuPG 2.2 or Gpg4win 3.0 for a spin.)
- 2017-09-21: Gpg4win 3.0 released, includes MIME capable Outlook-Add-in, GnuPG 2.2, WKD-requests and update notifications.
- 2017-08-28: GnuPG 2.2 released, comes with ECC and does "web key directory" requests by default.
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 (mainly on Windows for Gpg4win)
- 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
- Tools that may help running or administrating GnuPG or Gpg4win
- 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.