|
Size: 3264
Comment:
|
Size: 2970
Comment: Improving front page, moving the about information to the bottom.
|
| 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 related Free Software initiatives like [[http://gpg4win.org|Gpg4win]]. Their aim is to produce software solutions to |
Official Wiki for [[http://gnupg.org|GnuPG]] and [[http://gpg4win.org|Gpg4win]]. Open for related Free Software initiatives. |
| Line 7: | Line 7: |
| * 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. |
**[[Gpg4win|Go to Gpg4win-Section]]** |
| Line 11: | Line 9: |
| 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. |
== GnuPG for Users |
| Line 14: | Line 11: |
| Help us to [[improveThis|improve]] this wiki! = For Users * [[documentation]] |
* [[documentation|Documentation Overview]] |
| Line 32: | Line 25: |
| = For Developers | == GnuPG for Developers |
| Line 51: | Line 44: |
= Gpg4win {{image:gpg4win-logo-400px.png}} * [[Gpg4win/Roadmap|Roadmap]] * [[Gpg4win/Wishlist|Wishlist]] * Future Development means for [[Gpg4win/ImprovingSecurity|ImprovingSecurity]] * Reseach future [[Gpg4win/Installer|Installer technologies]] * Contracts ** [[Informsec2013]] funded Gpg4win improvements from April 2013 - September 2013 (from 2.1.1-beta1 to 2.2.1). ** [[Gpg4all2015]] from October 2015 - ** [[Gpg4vsnfd2015]] started in October 2015 to prepare an evaluation for use with classified 'restricted' documents in Germany. * [[press|Gpg4win in the press]] * [[Gpg4win/build|Building the installer]] |
* DevelopingKleopatra |
| Line 77: | Line 56: |
== About this Wiki The aim of the initiatives for ~GnuPG and ~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! |
Official Wiki for GnuPG and Gpg4win. Open for related Free Software initiatives.
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.
- 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.
Other OpenPGP implementations/initiatives
Planning
About this Wiki
The aim of the initiatives for GnuPG and 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!