gopass-jsonapi
gopass-jsonapi copied to clipboard
Brave configuration on Windows 11 not working.
Summary
Configuring gopass-jsonapi for Brave on Windows is not working, but it works using the Chromium configuration.
Steps To Reproduce
- Install
gopassusing scoop. - Install
gopass-jsonapiusing scoop. - Add the Gopass Bridge extension to Brave.
- Run
gopass-jsonapi configureand select Brave as the browser.
Expected Behavior
The configuration for Brave should work with the Brave browser.
Environment
- OS Name: Microsoft Windows 11 Pro
- OS Version: 10.0.22631 N/A Build 22631
- Brave Version: 1.70.117 Chromium: 129.0.6668.59 (Official Build) (64-bit)
- gopass Version: 1.15.14 go1.22.5
- gopass-jsonapi Version: 1.15.13
- Installation method: scoop
- Gopass Bridge Version: 0.9.0
Additional Context
The Brave configuration doesn't work for gopass-jsonapi, but the Chromium configuration works perfectly for Brave browser.
We are using a different registry path for brave on Windows, but I have no idea if that's correct. This is way out of my home turf, I'm neither using Windows nor Brave.
This will need help from someone that's more familiar with those.
Exactly, the registry path where Brave Browser searches for NativeMessagingHosts on Windows is:
With a local install for the NativeMessagingHosts
Computer\HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.justwatch.gopass