Do not use set use_agent, but set gpg binary to gpg2

[mrtndwrd]

At least in my setup, use_agent does not have to be manually set to "true" to make this work, I think gpg2 uses it by default.. python-gnupg uses gpg1 by default though, which, to me, does not make sense. Therefore I changed it to gpg2. This is tested on Ubuntu 16.04, not on any other platform

[hsanson]

Thanks for the MR but I think I cannot accept this as it is now. This can potentially break the extension for users that do use the gpg binary (e.g. me) instead of the gpg2 binary.

When time allows I will implement a configuration page for the plugin to allow users select the binary they want to use and possibly other stuff like the password store location.

[mrtndwrd]

I get that. If you want I can add the gpgbinary to the python program as a command line argument. I don't have any experience with chrome extensions though, so I wouldn't know how to fix that part of the application

[hsanson]

The extension (javascript) invokes the nativePass application with a single argument that contains binary format (protobuf). There is no way to tell the extension to pass additional arguments (e.g. gpgbinary) so this won't help. Thanks for the offer anyway.

I need to first create a configuration dialog for the extension that allows users to select/set the full binary path and then modify all sections that call the native app (message_send) to include the binary path as argument.