Hi Guillem, thank you for the verbose and helpful report, I appreciate it! :)
I followed your pointer to the 'key' in the manifest of the extension, which - ideally - seems to be generated once, i.e., when an extension is uploaded to the Chromium extensions repository for the first time. Once generated it should not change anymore, if I understood it correctly. I documented for future me and other developers in debian/README.source how to obtain that key for the extension and added it in the package to manifest.json. I tried out with a clean Chromium and KeePassXC installation and could make the extension identify itself to KeePassXC with a permitted ID, add credentials for web sites in a KeePassXC database and make the extension receive stored credentials. An upload is pending! In case it turns out that key changes frequently, we need to think of a different solution again :) Thanks and cheers, Bruno
signature.asc
Description: This is a digitally signed message part
