Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with keepassxc browser extension on QQBrowser (Chromium based) #4648

Closed
muyun12 opened this issue Apr 23, 2020 · 6 comments
Closed

Comments

@muyun12
Copy link

muyun12 commented Apr 23, 2020

After installing the keepassxc and enable browser integration, generate some .json files ,content like blow:

{
    "allowed_origins": [
        "chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/",
        "chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
    ],
    "description": "KeePassXC integration with native messaging support",
    "name": "org.keepassxc.keepassxc_browser",
    "path": "D:\\Program Files\\KeePassXC\\keepassxc-proxy.exe",
    "type": "stdio"
}

But after installing the keepassxc browser plugin, the id is 'hlkgcboejkmckpbcnebokepladlkdhdo',
this resulted in a failure to connect to KeePass.

How to solve this situation?

@droidmonkey
Copy link
Member

Confirm that you installed the official keepassxc extension from the chrome store.

@muyun12
Copy link
Author

muyun12 commented Apr 24, 2020

I downloaded and installed from ‘https://github.com/keepassxreboot/keepassxc-browser‘ and I can not access chrome store. Provide a method to manually enter id whether it is feasible to connect the KeePass, such as database setting interface.

@droidmonkey
Copy link
Member

Just edit the json file with your own ID.

@muyun12
Copy link
Author

muyun12 commented Apr 24, 2020

It does't work. Json file will be automatically modified after KeePassXC is restarted. I changed the source code and repackaged it to solve the problem and it work. Thanks!
I think the extension ID should support customization to deal with the problems I encounter. It is difficult for non professionals to modify the source code and package.

@droidmonkey
Copy link
Member

droidmonkey commented Apr 24, 2020

We don't recommend using niche browsers. There is strict control over the allowed extension id for good reason. It is an area with major security issues.

@muyun12
Copy link
Author

muyun12 commented Apr 28, 2020

OK,Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants