Package: webext-keepassxc-browser
Vesrion: 1.6.3+repack1-1
Severity: important

[ Perhaps this deserves to be serious? :) ]

Hi!

Thanks for packaging this, it's been very helpful! :)

While trying to use this extension with chromium, I was met with error
messages about not being able to connect to keepassxc. After some
digging I realized that the extension does not use the official
extension ID, so then keepassxc does not accept it as a valid one and
rejects the connection. I've temporarily worked around this by
checking the extension ID in the chromium settings, and adding it to:

  ~/.config/chromium/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json

but this can get overwritten by keepassxc. And I'm afraid the
extension ID might change from package build to build.

This is not a problem with firefox because that one uses a email ID.

I started searching for a way to make the extension identify itself
with the official ID, and from the manifest format it looks like the
"key" entry might do that, but it's not clear to me whether the ID can
be placed there directly, or the public key of the official extension
would be needed:

  <https://developer.chrome.com/extensions/manifest>
  <https://developer.chrome.com/apps/manifest/key>

If the public key for the official extension cannot be used here, perhaps
we'd need to create a Debian-specific one, and then make keepassxc accept
that one too. But this seems less than ideal I guess?

Thanks,
Guillem

Reply via email to