|
Size: 181
Comment: hosted info (for legal purposes, too), and example for ACLs, creole formatting and language declarations
|
Size: 3264
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #acl TrustedEditorGroup:read,write,delete,revert All:read | |
| Line 5: | Line 4: |
| TODO | 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 7: | Line 7: |
| ---- This site is hosted by [[http://www.intevation.de/|Intevation GmbH]]. |
* 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 [[https://g10code.com/steed.html|STEED]] concept. Help us to [[improveThis|improve]] this wiki! = 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 [[https://en.wikipedia.org/wiki/OpenLDAP|OpenLDAP]] as a keyserver. * Hints for use with [[NFS]] = For Developers * How to [[APIs|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. ** [[Build2.1_Unix|Building for Unix]] ** [[Build2.1_Windows|Building for Windows]] ** [[https://github.com/guardianproject/gnupg-for-android#build-setup|Building for Android]] * API checker: [[http://upstream-tracker.org/|Upstream-Tracker.org]] checks ABI/API changes for some libraries like [[http://upstream-tracker.org/versions/gpgme.html|gpgme]], [[http://upstream-tracker.org/versions/libgpg-error.html|libgpg-error]], [[http://upstream-tracker.org/versions/libgcrypt.html|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 = 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]] == Other OpenPGP implementations/initiatives * [[OtherFreeSoftwareOpenPGP]] * [[OtherFreeSoftwareInitiatives]] == Planning * [[Tasks]] * [[OpenPGPEmailSummits]] |
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!
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
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.
Gpg4win
- Roadmap
- Wishlist
- Future Development means for ImprovingSecurity
- Reseach future 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.
- Gpg4win in the press
- Building the installer