Skip to content
This repository has been archived by the owner on May 27, 2019. It is now read-only.

Missing prompt for GPG key (?) #265

Closed
comatory opened this issue Jun 12, 2018 · 15 comments
Closed

Missing prompt for GPG key (?) #265

comatory opened this issue Jun 12, 2018 · 15 comments

Comments

@comatory
Copy link

comatory commented Jun 12, 2018

General information

  • Operating system + version: Mac OS High Sierra
  • Browser + version: Chrome 66
  • Information about the host app:
    • How did you install it?
      • Installed via brew
    • If installed an official release, put a version:
      • 2.0.21
  • Information about the browser extension:
    • How did you install it?
      • Chrome webstore
    • Browserpass extension version as reported by your browser:
      • 2.0.21

Exact steps to reproduce the problem

  1. Do not use pass for some time
  2. After some time, decrypting passwords require my GPG key password
  3. When trying to use browserpass extension, it reports:
exit status 2 gpg: no secret key found

What should happen?

I'm not sure if this is correct behaviour but maybe a password prompt should popup asking for my GPG password.

What happened instead?

Displayed error.

@maximbaz
Copy link
Member

Hi, this should work, but it seems you are using a very old version of the host app - please install the latest version and let me know if you still have the issue.

@comatory
Copy link
Author

Oh I see. I will try to update then.

@comatory
Copy link
Author

OK so by the host app you probably mean browserpass host app, not pass itself, right?

@maximbaz
Copy link
Member

Correct, download here.

browserpass doesn't use pass at all by the way, only gpg to decrypt files 🙂

@comatory
Copy link
Author

comatory commented Jun 12, 2018

So in that I case I went here and downloaded latest release.

@maximbaz
Copy link
Member

Yep, that's the one. Make sure to remove the old binary, there was a case when someone had two binaries installed and the old one took precedence.

@comatory
Copy link
Author

comatory commented Jun 12, 2018

Well that's the version I actually installed it with so I have no other binaries. It does not seem to work. How would I check (just in case) I have two binaries of the host app?

@maximbaz
Copy link
Member

The file /etc/opt/chrome/native-messaging-hosts or $HOME/.config/google-chrome/NativeMessagingHosts should have a full path to browserpass binary (you likely only have one of these files), copy the full path and execute /full/path/to/browserpass -v - should print the version 2.0.21.

@comatory
Copy link
Author

OK so I located file com.dannyvankooten.browserpass.json at /Users/$USER_NAME/Library/Application Support/Google/Chrome/NativeMessagingHosts. I looked into it, it looks like this:

{
  "name": "com.dannyvankooten.browserpass",
  "description": "Browserpass binary for the Chrome extension",
  "path": "/Users/<user_name>/Documents/browserpass-darwinx64/browserpass-darwinx64",
  "type": "stdio",
  "allowed_origins": [
    "chrome-extension://naepdomgkenhinolocfifgehidddafch/",
    "chrome-extension://klfoddkbhleoaabpmiigbmpbjfljimgb/"
  ]
}

when I use the path like this /Users/<username>/Documents/browserpass-darwinx64/browserpass-darwinx64 -v it gives me: Browserpass host app version: 2.0.21

Btw I'm using Chrome with two user profiles. Both of them have browserpass extension.

@maximbaz
Copy link
Member

Awesome, so what's the current status, is everything good, is everything the same as before upgrading, is it worse? 🙂

@comatory
Copy link
Author

It's still the same. I get the same message. When I unlock password using pass then it works fine.

@comatory
Copy link
Author

Could this be caused by some kind of settings on the GPG key itself? I just don't get any prompt to unlock the GPG key from the extension itself.

@maximbaz
Copy link
Member

I have a suspicion that you are experiencing some kind of variation of #13, try these steps from FAQ: https://github.com/browserpass/browserpass#does-not-work-on-macos-native-host-has-exited

@comatory
Copy link
Author

OK I followed FAQ and it is fixed now. I had to create ~/.gnupg/gpg.conf and ~/.gnupg/gpg-agent.conf files though but it's all good now it seems. Thanks.

@maximbaz
Copy link
Member

Awesome!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants