I think I installed it once, and then when my machine required rebuilding, I just couldn't bring myself to install it again.
I wish it weren't so, but a new website is not something that is going to speed the adoption of GnuPG.
I think I installed it once, and then when my machine required rebuilding, I just couldn't bring myself to install it again.
I wish it weren't so, but a new website is not something that is going to speed the adoption of GnuPG.
The integration with Emacs mail clients is fantastic too; just M-x mml-secure-sign or M-x mml-secure-encrypt when composing, and incoming messages with signatures are typically checked for you.
This totally changed the way I used GPG. (from "not at all" to "every day")
In all honesty, however, part of the "difficulty" of GPG is really by design. You need to be deliberate about signing and encrypting because security should be a careful and deliberate act. If you're hoping for the program to take care of it transparently, you're probably not being safe enough. At least Emacs requires you to go through an explicit process. As you have to do with everything in Emacs.
Why? You don't have to be 'deliberate' about encrypting when you're using SSH or HTTPS.
SSH is more in our control, but it's still trusting a third party (a server) and it still requires a deliberate act to set up and use (unlike HTTPS).
http://goteo.org/project/gnupg-new-website-and-infrastructure/needs
They are looking for funding to:- Release GnuPG 2.1 - Create a new web site
According to the descriptions, the new web site is not only about a new theme, but also about creating and collecting content that explains how to use GnuPG and encryption, in general.