Your message dated Sat, 06 Jun 2020 06:18:28 +0000 with message-id <e1jhsa0-000cjs...@fasolo.debian.org> and subject line Bug#962246: fixed in keepassxc-browser 1.6.3+repack1-2 has caused the Debian Bug report #962246, regarding webext-keepassxc-browser: Cannot connect to keepassxc from chromium to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Source: keepassxc-browser Source-Version: 1.6.3+repack1-2 Done: Bruno Kleinert <fu...@debian.org> We believe that the bug you reported is fixed in the latest version of keepassxc-browser, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bruno Kleinert <fu...@debian.org> (supplier of updated keepassxc-browser package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jun 2020 07:36:23 +0200 Source: keepassxc-browser Architecture: source Version: 1.6.3+repack1-2 Distribution: unstable Urgency: medium Maintainer: Bruno Kleinert <fu...@debian.org> Changed-By: Bruno Kleinert <fu...@debian.org> Closes: 962246 Changes: keepassxc-browser (1.6.3+repack1-2) unstable; urgency=medium . * Fixed 'Cannot connect to keepassxc from chromium'. Added key 'key' to keepassxc-browser/manifest.json to make the extension identify itself from within the Chromium browser to KeePassXC with a permitted identifier. Documented in debian/README.source how to obtain they key. (Closes: #962246) Checksums-Sha1: d042809a3bb64fa9a7208143d9127eed024e16bf 1975 keepassxc-browser_1.6.3+repack1-2.dsc 9dd8672df3e6e0fb270f33a03d4a681b212a9137 14544 keepassxc-browser_1.6.3+repack1-2.debian.tar.xz 5434416f1c6f99fae72c97cdbbc7e21fb0e11cb5 5573 keepassxc-browser_1.6.3+repack1-2_source.buildinfo Checksums-Sha256: 25d453e224b71b795025d80c944cc13f90c88b0368c0f21b89611069063e7bcc 1975 keepassxc-browser_1.6.3+repack1-2.dsc 79c87d88481f2f324996f82499fc2afeece2dfc8ab03157853aaa5d73f37268e 14544 keepassxc-browser_1.6.3+repack1-2.debian.tar.xz 7bb11fe40769e4d7863b19b4717dcaf8e68d0dcae15a650722a4d6180bf6d2f1 5573 keepassxc-browser_1.6.3+repack1-2_source.buildinfo Files: 2f79327f2370be65001fdca5cfe792bd 1975 web optional keepassxc-browser_1.6.3+repack1-2.dsc 860e61d763015b3d3227e6fe3c9c928f 14544 web optional keepassxc-browser_1.6.3+repack1-2.debian.tar.xz 224d63551fd3f5b3c5e24b21afa1856a 5573 web optional keepassxc-browser_1.6.3+repack1-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEEbNBoYg3hPRuThXIzSwBpzPZSeEcFAl7bLCURHGZ1ZGRsQGRl Ymlhbi5vcmcACgkQSwBpzPZSeEfzJQ//WdqcuSa7WXXQXcnnIFNe0hpN0X1PJz0b xQlKvzbe+6vmNGVn4qlidE5SAPIQQwf0hU29H3LqKlFX7BKOEAFKmZybr9W6mUtL 0Tyj363S2JprqYSmEzIo0EEEi1iP9faQmMAUWSDwJ+fwl5RvjKe/hgqcNKR+VB6O w0bU6DITbf94iy8DOrVnctNyN3GCDJrWdZhdEsK/Fb2VkeGIYiy4/iCvE7H1xqDQ RzuNfVtd7l54HTlik5tH5nOKD+SKozTz1kXuNwkKzbrb8YjIgVbEhhUMLlC9HoZV aEf5Bb7BnGqkGKxS8fWCRQa4EDv0cZaQde3ea64UcbSBerQ+0z3NNMsrqfsPhFCP IPdIrKkGgEHgh45+xkQb6eZrIowO7np10/fH25a3EjbTNgcqzhlOEZGjYxsqgzQa NWP+PPE5EkmXKfcMBuy/pXEcfQa5M5JHFNmKKRBDEvMVSWoC+y2UWEQXQ8Aumb6A 8yjND1jipq+OO7GDFwuygQFJp3zSU/ya/eCOltvW+APZcpgtyls6XPG4I6qOhLJT 1gTiUsVuKe8VeJ1chCLKIjce6O4zscidC6nVz/Gxyf9VICAI3s01EjdRu6e7ThtK C6PxMN9kD1+YaPka5gGfYNnHXlZdYNCL4fOYn7ACkA0rmluGw3WK9ZbuvPomOR+H iLuR5Fuu0BA= =jm2C -----END PGP SIGNATURE-----
--- End Message ---
