|Deletions are marked like this.||Additions are marked like this.|
|Line 22:||Line 22:|
|* [[X.509]] hints||* [[X.509]] hints (needed for S/~MIME and trusted root certs)|
|Line 66:||Line 66:|
Secure file and email exchange! Usable for everyone without licensing fees. Transparent with source code using Open Standards.
It's 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.
The next big user experience boost for email security would be the adoption of the STEED concept. Help us make it happen.
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!
- 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
Building GnuPG 2.1
This is a collection of links which may sometimes be useful
- Upstream-Tracker.org checks ABI/API changes for some libraries like gpgme, libgpg-error, libgcrypt. Note that tools can't necessary decide whether something is an ABI or API change. The output should be used as a hint to look whether there might be a problem. We are not aware of any broken API or ABI contracts for the listed libraries.
- Gpg4win in the press
- Future Development means for ImprovingSecurity
- starting a Roadmap
- building the installer Build
- Project Informsec2013 from April 2013 - September 2013, funded Gpg4win improvements from 2.1.1-beta1 to 2.2.1.