|
Size: 3299
Comment: gpg4win: contracts are now a sublist, renamed pages
|
Size: 2424
Comment: Moving disclaimers and about information to a new /about page.
|
| 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 |
//([[about|About this wiki]])// |
| Line 7: | Line 6: |
| * 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|-> Gpg4win-Section]]** |
| Line 11: | Line 8: |
| 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. |
**[[WKD| -> Web Key Directory]]**, which makes exchanging crypto mails much easier. |
| Line 14: | Line 10: |
| This Wiki is about helping users and contributors by providing a central place for [[documentation]], links to references and planning. We welcome your contribution! |
|
| Line 17: | Line 11: |
| = For Users | == GnuPG for Users |
| Line 19: | Line 13: |
| * [[documentation|Documentation Overview]] | |
| Line 31: | Line 26: |
| * [[AgentForwarding|How to use local secrets on a remote machine]] | |
| Line 32: | Line 28: |
| = For Developers | == GnuPG for Developers |
| Line 34: | Line 30: |
| * How to [[APIs|use GnuPG from your application]]. | * How to [[APIs|use GnuPG from your application]] (~GnuPG's API) |
| Line 51: | Line 47: |
---- = Gpg4win {{image:gpg4win-logo-400px.png}} * [[Gpg4win/Roadmap|Roadmap]] * [[Gpg4win/Wishlist|Wishlist]] * Future Development means for [[Gpg4win/ImprovingSecurity|ImprovingSecurity]] * 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 * NTBTLS (Not too bad TLS) client library |
| Line 76: | Line 59: |
| * [[GnuPGSummit]] | * [[OpenPGPEmailSummits]] * [[https://gnupg.org/conf|OpenPGP.conf]], last conf was 8+9th of Sept, 2016. |
-> Web Key Directory, which makes exchanging crypto mails much easier.
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
- How to use local secrets on a remote machine
GnuPG for Developers
- 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
Other OpenPGP implementations/initiatives
Planning
- Tasks
- OpenPGPEmailSummits
- OpenPGP.conf, last conf was 8+9th of Sept, 2016.