Finally got WebPG v0.9.4 to work both on FF under Windows, and Iceweasel under Linux.

[dirkmittler]

Yahoo!

This version of WebPG had not worked on two setups, for two completely different reasons:

Under Iceweasel / Linux, the version was 21.0 , but, I had erroneously entered a gpg v1 executable in the settings some time ago. Clearing that field, undid the damage, and the extension now works.

Under Firefox / Windows 7, my real problem was just too old a FF version, which was 19.0 at the time. So I hunkered down and updated to FF v30 . And wouldn't you know it, WebPG v0.9.4 works correctly there too, no longer displaying the two Send buttons, but the WebPG and the Send button.

Yaay!

[Edit] In principle, WebPG would even be stable enough to encrypt using GnuPG v1.x . But with WebPG v0.9.4 , it remembered the setting from v0.9.3 , to use /usr/bin/gpg , but to use /usr/bin/gpgconf , the latter of which was meant to be used with /usr/bin/gpg2 . This created a noticeable inconsistency within WebPG's Options panel, about which of my keys was enabled at any given time.

However, once I removed the entry for /usr/bin/gpg , WebPG's self-configuration correctly chose /usr/bin/gpg2 , and the behavior of the Options panel became correct.

More importantly, the Compose window now displayed a correct error message from WebPG, simply telling me that the public key I was encrypting to was unavailable (due to my own configuration mistake). This was the true reason fw WebPG 0.9.4 wasn't sending, using Iceweasel 21 and Linux. And at that point it became child's play for me, to go back into the Options panel, and just to enable that public key, after which this instance of WebPG also worked fine.