|
Size: 2897
Comment: Added notable events section with some "news".
|
Size: 3212
Comment: move elder events to subpage. + 2.3.0 release
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| **[[WKD| -> Web Key Directory]]**, which makes exchanging crypto mails much easier. | **[[WKD| -> Web Key Directory and Service]]**, which makes exchanging crypto mails much easier. |
| Line 11: | Line 11: |
| * 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]] |
* 2021-04-08: [[https://lists.gnupg.org/pipermail/gnupg-announce/2021q2/000458.html|GnuPG 2.3.0 released]], a major release with new crypto algorithm defaults and faster pubkey storage. * 2020-01-07: [[https://gnupg.com/|GnuPG.com]] starts offering paid support for Gpg4win that is approved for EU RE~STR~ICT~ED communication. (Gnu~PG.com is a brand of g10code the main developer of Gnu~PG and Gpg~4win.) * 2019-04-30: [[https://www.gpg4win.org/statement-spoofing.html|About detecting spoofed email signatures]] a writeup by Gnu~PG/Gpg4win |
| Line 15: | Line 16: |
| * 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.) | (NotableEventsHistory) |
| Line 23: | 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 29: | Line 30: |
| * [[Tools]] that may help running or administrating GnuPG or Gpg4win | |
| Line 36: | Line 38: |
| * [[BestUxPractices|Suggestions for common UX practices]] | |
| Line 55: | Line 58: |
| * OtherResearch |
-> Web Key Directory and Service, which makes exchanging crypto mails much easier.
Notable Events
- 2021-04-08: GnuPG 2.3.0 released, a major release with new crypto algorithm defaults and faster pubkey storage.
- 2020-01-07: GnuPG.com starts offering paid support for Gpg4win that is approved for EU RESTRICTED communication. (GnuPG.com is a brand of g10code the main developer of GnuPG and Gpg4win.)
- 2019-04-30: About detecting spoofed email signatures a writeup by GnuPG/Gpg4win
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
- Suggestions for common UX practices
- 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
- OtherResearch
Other OpenPGP implementations/initiatives
Planning
- Tasks
- OpenPGPEmailSummits
- OpenPGP.conf, last conf was 8+9th of Sept, 2016.