gpgAuth :
Client Implementations :
Chrome / Chromium : Chrome Linux
- 1 : Introduction
- 2 : Server Implementations
- 2.1 : mod_python
- 2.2 : PHP
- 2.3 : Django
- 3 : Client Implementations
- 3.1 : Mozilla Firefox
- 3.2 : Safari
- 3.3 : Internet Explorer
- 3.4 : Chrome / Chromium
- 3.4.1 : Chrome Linux
- 3.4.2 : Chrome OSX
- 3.4.3 : Chrome Windows
- 4 : FAQ
- Examples/Screenshots (0)
- Files/Downloads (2)
Donate to this project:
- Dwolla
- Paypal
- BitCoin (digital money)
- Check/Money Order
Mailing Address: TBA
The gpgAuth implementation client for Chrome/Chromium on Linux is the same extension for Chrome/Chromium on other operating systems.
The (current) requirements are:
- A working key agent
- libgpgme11
- gnupg2
A working key agent is absolutely necessary, as, the web browser client should never be asking for the passphrase to unlock a private key - I have this belief for the following reasons
- The user should not be encouraged to type their passphrase into anything other than the key agent (ESPECIALLY NOT THE BROWSER)
- Passing around the passphrase within the browser is a dangerous proposition
libgpgme11 is currently required because the NPAPI plugin is linked against it; I hope to have it statically included eventually - but I am still working out license questions.
The gnupg2 package is required because it provides gpgconf - which is used to control aspects of gpg during operations such signing. (without gpgconf, the gpg configuration cannot be modified through libgpgme)
I am working on reducing those dependencies to only the key agent - hopefully for 1.0.3.4 of the client library.
