Change:
sha256 = "0wszjpxfa0krr2zdx7a33vl1r86k74dpy5c940r6ww1zbgqzcibg"; }; <ins> postPatch = '' substituteInPlace browserpass.go                                            --replace /usr/local/bin/gpg ${gnupg}/bin/gpg ''; </ins> postInstall = '' host_file="$bin/bin/browserpass" mkdir -p "$bin/etc"

Discussion:
With , does not work properly. When clicking on the browserpass icon in firefox, browserpass states 'Error talking to browserpass' Install browserpass via Install firefox via Install browserpass browserplugin via firefox marketplace Click on browserpass icon in firefoxsystem: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs:
~Unfortunately I think this is unfixable at the moment~ (the issue is patched around in nixpkgs build of firefox). Firefox expects native messaging manifests to be found in (Chrome uses ). This means there's no way to expose manifest files on NixOS on the system level. You can work around it by linking the firefox manifest from into . Something like this should do it: Relevant Firefox bug:
This was fixed in by a Nixpkgs option. Maybe should set the correct Nixpkgs option by default{
I never managed to make it work either so thanks for the pointer. I believe home-manager installs it in ~/.mozilla so that could work too.
So this is fixable, the fix was not straightforward but it is going to be fixed in 18.03?
Yeah, disregard my comment above (nixpkgs patch around the firefox issue). If I understand correctly you want to do something like this in to make browserpass work now:
I'm experiencing this same issue with firefox 59.0.1. I have tried both firefox-bin and firefox. I'm mostly using firefox-bin because I like the Mozilla branding, but it doesn't matter that much really. I have in my configuration. I've used browserpass in firefox a long time ago (before 57 I believe) using home-manager and still have set in home-manager which successfully creates the symlink in . I've just started google-chrome up to test there and that seems to work. But that won't help me that much in firefox :smile: output from nix-info:
Ok,I've got it working and did some research. The first issue I've had which was really odd to me was that I had the wrong firefox extension, it has been working before. The only thing I can assume made it that way is that they released a separate extension when it became webextensions or something. But that doesn't make very much sense to me since the button was there in the browser.

So my first step to get this to work in firefox again was to remove the old one and install this one: (link is in README of browserpass github page). I've also not managed to get it to work (in firefox) with the service for browserpass (). But it works using the home-manager's option which symlinks the same json-file to the home-directory instead of the firefox store path.
So this is still broken. Using browserpass-ce I get the suggestions but when clicking on them, it only displays "Error: An unexpected error occurred". Will this be fixed?
This works for me with 59.0.1. IIUC, it won't work with .
Hmmh. Installed via . Using for browserpass.
Could you try repeating this with the browser console open? (<kbdCtrl</kbd-<kbdShift</kbd-<kbdJ</kbdto open the browser console.) That may give a more detailed error message.
Thats the output. looks interesting. How does that happen?
Do you have gpg in your system-packages or not? I'd say that it shouldn't be needed, but might be needed.
No, I don't have it explicitly installed, but I have
If I look in the browserpass source, I found this function: Which seems to be the one that failed. It's purpose seems to be to find a gpg binary. But it fails since it's not in your environment. If I look in our package for browserpass -- I don't see that we patch the path to the gpg binary, which means that it must exist in the system environment for browserpass to find it. A temporary fix for you would be to add to your system packages. But in reality browserpass should be patched with our path to gpg.
The temporary fix does work for me. Closing since you started a PR on this. Great thanks!