|
Size: 3141
Comment:
|
Size: 2729
Comment: Structural improvement, the Gpg4win subsite needs to be more prominently placed
|
| 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! |
= GnuPG Wiki |
| Line 8: | Line 6: |
| GnuPG: | 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 |
| Line 10: | Line 9: |
| * 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. |
* 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. |
| Line 14: | Line 13: |
| 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. | 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. |
| Line 16: | Line 16: |
| = For Users | Help us to [[improveThis|improve]] this wiki! |
| Line 18: | Line 18: |
| **[[Gpg4win|Go to Gpg4win-Section]]** == GnuPG for Users * [[documentation]] |
|
| Line 31: | Line 36: |
| = For Developers | == GnuPG for Developers |
| Line 50: | Line 55: |
== Ggp4w {{image:gpg4win-logo-400px.png}} * [[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]] |
* DevelopingKleopatra |
| Line 70: | Line 66: |
| * [[GnuPGSummit]] | * [[OpenPGPEmailSummits]] |
GnuPG Wiki
This is the official Wiki for GnuPG, the GNU Privacy Guard, and all related Free Software initiatives like Gpg4win. Their aim is to produce software solutions to
- 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.
The next big user experience boost for email and file-transport security would be the adoption of the STEED concept.
Help us to improve this wiki!
GnuPG for Users
- documentation
- 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.