Naturally we’ll also need to adjust the Flatpak permissions so KeePassXC can write to this path.įlatpak override -user -filesystem=~/.var/app//.mozilla/native-messaging-hosts Īt this point Firefox knows about the native messaging host but it won’t be able to run it. ~/.var/app//.mozilla/native-messaging-hosts/ is the path inside Firefox’ home where the defintion file will be written. So, don’t do this if you don’t keep your Firefox updated or visit particularly dodgy websites.įor the purposes of this post I’m assuming Firefox and KeePassXC are installed as Flatpaks in user scope.įirst order of business is setting up KeePassXC so it writes its definition file in a place where Firefox can read it. This enables the use of native messaging even without portal integration, albeit also without sane degrees of sandboxing.įirst off, please understand that this undermines the sandbox on a fairly fundamental level. To celebrate its anniversary I thought I’d write down how to drill a native-messaging sized hole into the sandbox. Perhaps it shouldn’t come as a surprise that native-messaging sandboxing support for Flatpak has been in development for over a year. But application sandboxing, so an application cannot do anything it wants, is a challenge – even more so when you have two applications that need to talk to each other. keepass.js:1192 message: (.)get message: ƒ ()arguments: (.)caller: (.)length: 0name: ""_proto_: ƒ ()apply: ƒ apply()arguments: (.)bind: ƒ bind()call: ƒ call()caller: (.)constructor: ƒ Function()length: 0name: ""toString: ƒ toString()Symbol(Symbol.hasInstance): ƒ ()get arguments: ƒ ()set arguments: ƒ ()get caller: ƒ ()set caller: ƒ ()_proto_: Object]: ]: Scopes]: ScopesNo properties_proto_: constructor: ƒ ()_proto_: Object keepass.js:1078 Error 9: Key exchange was not successful.Flatpaks are amazing and all that. keepass.js:993 Connecting to native messaging host _browser keepass.js:969 Failed to connect: Specified native messaging host not found. Check that browser integration is enabled in KeePassXC settings. keepass.js:1192 Objectmessage: (.)get message: ƒ ()arguments: (.)caller: (.)length: 0name: ""_proto_: ƒ ()apply: ƒ apply()arguments: (.)bind: ƒ bind()call: ƒ call()caller: (.)constructor: ƒ Function()length: 0name: ""toString: ƒ toString()Symbol(Symbol.hasInstance): ƒ ()get arguments: ƒ ()set arguments: ƒ ()get caller: ƒ ()set caller: ƒ ()_proto_: Object]: ]: ScopesNo properties]: ScopesNo properties_proto_: Object :1 Returning a Promise is the preferred way to send a reply from an onMessage/onMessageExternal listener, as the sendResponse will be removed from the specs (See ) Error at B (chrome-extension://oboonakemofpalcgghocfoadofidjkkk/:1:8152) at chrome-extension://oboonakemofpalcgghocfoadofidjkkk/background/event.js:108:9 B :1 keepass.js:1078 Error 5: Cannot connect to KeePassXC. See related report on keepassxc-browser github: Ĭonnecting to native messaging host _browser keepass.js:969 Failed to connect: Specified native messaging host not found. No, extension works as expected on latest Chrome Is the issue reproducible on the latest version of Chrome?.Does the issue resolve itself when disabling Brave Rewards?.Does the issue resolve itself when disabling Brave Shields?.Can you reproduce this issue with the nightly channel?.Can you reproduce this issue with the dev channel?.Can you reproduce this issue with the beta channel?.Can you reproduce this issue with the current release?.Expected result: Reproduces how often:Ĭonsistant Brave version (brave://version info) Version/Channel Information: Brave Try to connect to KeePassXC through the extension.Enable browser integration for brave in KeePassXC (creates Brave-Browser/NativeMessagingHosts/_browser.json - I copied manually for Brave-Browser-Dev).I have confirmed the extension works in Chrome. KeePassXC-Browser chrome extension doesn’t work in Brave or Brave-dev on MacOS.
0 Comments
Leave a Reply. |