Reviews for KeePassXC-Browser
KeePassXC-Browser by KeePassXC Team
Review by Firefox user 14403121
Rated 1 out of 5
by Firefox user 14403121, 6 years agoDoes not work reliable. Need to be more stable. (Firefox-Version)
Problem: The key between the KeePassXC-Browser Add-On and the KeepasXC database (stored in the root folder) to exchange the secret data is not the same. (key: the secret key the exchange data bewteen the add-on, proxy (optional) and KeePassXC database. I compare the first digits)
This issue leads to that point, that every time the user closes Firefox and start Firefox later (say: next day or so) he has to regenerate all the connection information and login with a new name. The connection is not persistent. It's like every time before you close firefox you remove the connection info from the KeePassXC-Browser Add-On.
Same happen if i enable or disable the "Use a Proxy application bewteen KeePassXS and brwoser extension" in the advanced settings tab from KeePass. So, i think, it is not a issue of the proxy.
System: Ubuntu 18.04 LTS, Firefox 63.0, KeePassXC 2.3.1, KeePassXC-Browser Version: 1.3.0
Same happens under Ubuntu 16.04 LTS with a manuall KeePassXC Installation - because KeePassXC is not part of the regular Ubunut 16.04 distribution.
Problem: The key between the KeePassXC-Browser Add-On and the KeepasXC database (stored in the root folder) to exchange the secret data is not the same. (key: the secret key the exchange data bewteen the add-on, proxy (optional) and KeePassXC database. I compare the first digits)
This issue leads to that point, that every time the user closes Firefox and start Firefox later (say: next day or so) he has to regenerate all the connection information and login with a new name. The connection is not persistent. It's like every time before you close firefox you remove the connection info from the KeePassXC-Browser Add-On.
Same happen if i enable or disable the "Use a Proxy application bewteen KeePassXS and brwoser extension" in the advanced settings tab from KeePass. So, i think, it is not a issue of the proxy.
System: Ubuntu 18.04 LTS, Firefox 63.0, KeePassXC 2.3.1, KeePassXC-Browser Version: 1.3.0
Same happens under Ubuntu 16.04 LTS with a manuall KeePassXC Installation - because KeePassXC is not part of the regular Ubunut 16.04 distribution.
Developer response
posted 6 years agoThank you for the review. Please ensure that you are not reusing the database identifier. It must be unique for each connection (actually we should prevent that from happening). You can try to delete the KeePassXC-Browser Settings entry from your database, and delete the connected keys from the extension too. Then make a reconnection with a new unique identifier.