Message won't send if WebPG options are selected

[codyromano]

Hey, excellent work on this plugin. It's a great concept and you've executed it well. Having said that, I'm having a little issue with sending messages in Gmail. The message won't send if I choose to encrypt and/or sign it. It only sends if I choose not to use WebPG. Here's an example:

I'm using the Chrome 36 browser on Mac OSX. I first noticed the issue around 9 p.m. on Friday, July 25th. I'm using Plugin version: 0.7.0. and GnuPG version: 2.0.22. I know that I can send GPG messages to the same recipient using the native Mail app, so I don't think this is issue is related to keys or GPG itself.

Update: Tried this on another Macbook Pro and the behavior is the same.

[kylehuff]

@codyromano

Thank you for this very detailed and illustrative bug report! I apologize for the delay in getting back to you, my work schedule renders me, incapacitated, at times.

I see you included the plugin version in your report, but I need to know the extension version. This can be found in the "about" page of the WebPG options page (it should also be listed in the top right-hand corner of the options page).

The "plugin" is the binary component that interacts with GnuPG (which is a separate project all together), and the extension (or "add-on" in Mozilla lingo) is what provides the user interface to the browser.

Also, where was this version of WebPG retrieved from? (i.e. the Chrome webstore, manual installation from the github repo, side-loaded from webpg.org, etc).

[codyromano]

Hi Kyle, No worries. Thanks for your response.

The extension version is 0.9.4.

I downloaded WebPG on the project’s main Downloads page, using the link "Click here to begin installation: WebPG - webpg-chrome”

On Jul 27, 2014, at 9:19 AM, Kyle L. Huff notifications@github.com wrote:

@codyromano

Thank you for this very detailed and illustrative bug report! I apologize for the delay in getting back to you, my work schedule renders me, incapacitated, at times.

I see you included the plugin version in your report, but I need to know the extension version. This can be found in the "about" page of the WebPG options page (it should also be listed in the top right-hand corner of the options page).

The "plugin" is the binary component that interacts with GnuPG (which is a separate project all together), and the extension (or "add-on" in Mozilla lingo) is what provides the user interface to the browser.

Also, where was this version of WebPG retrieved from? (i.e. the Chrome webstore, manual installation from the github repo, side-loaded from webpg.org, etc).

—
Reply to this email directly or view it on GitHub.

[kylehuff]

Okay, that is the Chrome webstore distribution.

So, I can't reproduce the issue, but I have a hunch that you do not have a default key assigned, or WebPG is unable to identify which key is default.

In the WebPG Key Manager, in the "Private Keys" tab, are any of your keys listed as default? (the checkmark to the right of "Enabled" would be illuminated on the default key).

[codyromano]

Thanks for the suggestion. I checked the Private Keys tab and none of the keys were listed as default. I marked one of my keys as default, but the problem persisted. I tried deleted the extension and reinstall it, but no luck unfortunately.

On Jul 27, 2014, at 6:23 PM, Kyle L. Huff notifications@github.com wrote:

Okay, that is the Chrome webstore distribution.

So, I can't reproduce the issue, but I have a hunch that you do not have a default key assigned, or WebPG is unable to identify which key is default.

In the WebPG Key Manager, in the "Private Keys" tab, are any of your keys listed as default? (the checkmark to the right of "Enabled" would be illuminated on the default key).

—
Reply to this email directly or view it on GitHub.

[sbliven]

I have this issue as well. I'm using WebPG 0.9.4 on Chromium Version 39.0.2141.0 (f34d28c5bb38) (64-bit) on Mac OS 10.9.5.

Setting a default key did not solve the problem for me (and why isn't there a default upon installation?).

For encryption options I get the non-responsive behavior @codyromano described. However for signing, after clicking send the message displays "Bad passphrase". It does not prompt at all for a passphrase, nor do I remember saving one somewhere. So perhaps the failure to send is actually a silent failure to display the password prompt.

[kylehuff]

@sbliven

Setting a default key did not solve the problem for me (and why isn't there a default upon installation?)

The default key feature is not a construct of WebPG, it is provided by GnuPG. GnuPG (and likewise WebPG) have no idea what key you want default. Arguably, if you only have one key, it should probably be the default, but that is a matter for GnuPG to decide.

For encryption options I get the non-responsive behavior @codyromano described. However for signing, after clicking send the message displays "Bad passphrase".

This sounds like you do not have a valid key-agent running.

It does not prompt at all for a passphrase, nor do I remember saving one somewhere.

WebPG does not store passphrases (nor does it ever even see one); all passphrase requests are differed to the key-agent, and this is by design. Passphrase requests should never handled by the browser.

So perhaps the failure to send is actually a silent failure to display the password prompt.

You are probably correct, however fixing it will require a working key-agent, which is outside of the scope of WebPG. I would be more than happy to assist you in troubleshooting your key agent. I suggest dropping by the IRC channel #webpg on freenode either with an IRC client or from the WebPG contact page (https://webpg.org/?view=webchat). Please note that myself and the others who provide assistance there may be doing other things and not immediately respond.

[sbliven]

Ok, I installed gpg-agent and now I'm not getting the passphrase problem, but I'm still not getting any response. I'll lurk in IRC for a while and try to figure it out.