Відгуки для KeePassXC-Browser
KeePassXC-Browser автор KeePassXC Team
Відгук від Myster
Оцінка 2 з 5
від Myster, 6 років томуJust doesn't work.
Behaviour is so random. Extension works for some sites, and completely fails for others (about 70% of the websites I browse).
The most frustrating thing, is that this green icon appears in the login field, but nothing happens when you press it.
To be noted, this is consistent whichever browser I use (FF or Chrome) and whichever OS I run (Windows 10 or Linux Mint).
I gave a KeepassXC and the browser extension a try because it looked promising, and the KeepassXC GUI is nicer to plain Keepass, but it seems I have no other option than revert to Keepass + RPC pluging + Kee browser extension.
Sad.
Behaviour is so random. Extension works for some sites, and completely fails for others (about 70% of the websites I browse).
The most frustrating thing, is that this green icon appears in the login field, but nothing happens when you press it.
To be noted, this is consistent whichever browser I use (FF or Chrome) and whichever OS I run (Windows 10 or Linux Mint).
I gave a KeepassXC and the browser extension a try because it looked promising, and the KeepassXC GUI is nicer to plain Keepass, but it seems I have no other option than revert to Keepass + RPC pluging + Kee browser extension.
Sad.
Відповідь розробника
оприлюднено 6 років томуThe green icon appears if your database is unlocked. It doesn't tell if you have credentials for the site or not. The popup shows an icon with a questionmark if credentials are found, and the same feature will be implemented to the Username field icon later.
If you have troubles for getting your credentials to the site, please ensure your entry URL's are correct. Sometimes pages use iframes from other subdomains for the login fields, so the safest best is to use https://example.com instead of https://loginpage.example.com. When a subdomain is removed from the entry URL it works as a wildcard, meaning https://example.com will match https://*.example.com and so on.
If you have troubles for getting your credentials to the site, please ensure your entry URL's are correct. Sometimes pages use iframes from other subdomains for the login fields, so the safest best is to use https://example.com instead of https://loginpage.example.com. When a subdomain is removed from the entry URL it works as a wildcard, meaning https://example.com will match https://*.example.com and so on.
745 відгуків
- Оцінка 5 з 5від toorootoot, 3 години тому
- Оцінка 5 з 5від Mark Andrew Gerads, 14 днів тому
- Оцінка 5 з 5від SilverAmd, 19 днів тому
- Оцінка 5 з 5від Користувач Firefox 19902880, 21 день тому
- Оцінка 5 з 5від Craig, 22 дні тому
- Оцінка 5 з 5від Користувач Firefox 19882925, місяць тому
- Оцінка 5 з 5від Користувач Firefox 18863959, місяць тому
- Оцінка 1 з 5від Користувач Firefox 14868755, місяць томуNot able to add connected database. Nothing happens when clicking the Connect Database button. Bazzite 43 (linux) NVIDIA edition, Firefox 149, KeePassXC 2.7.12
- Оцінка 4 з 5від Saturnus, 2 місяці тому
- Оцінка 4 з 5від Fokeu, 2 місяці тому
- Оцінка 5 з 5від Користувач Firefox 13156335, 2 місяці томуWorks fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- Оцінка 5 з 5від Cangrejo, 3 місяці томуBest password manager ever.
I know this depends of Keepassxc development, but it would be nice if card info can be stored. - Оцінка 5 з 5від elsenfox, 3 місяці тому
- Оцінка 2 з 5від Користувач Firefox 19733088, 3 місяці томуEigentlich gut, aber umständlich, funktioniert bei vielen Websites einfach mal gar nicht, das Felderkennungs-Tool zum Zuweisen ebenfalls nicht und kostet daher viel Zeit und Nerven in der Benutzung. Daher kann ich ebenso schnell und gut aus KeepassXC kopieren und einfügen und brauche mich nicht mit diesem AddOn herumschlagen; leider!
- Оцінка 1 з 5від John Hills, 4 місяці томуThe addon randomly shows errors like "KeePassXC-Browser has encountered an error: Key exchange was not successful" which means absolutely nothing to the user and does not help solve the problem in any way. It is the same as showing a message "Error: There has been an error. You're unlucky, too bad for you."
Відповідь розробника
оприлюднено 4 місяці томуGitHub already has an issue about this. In short, there's no way to get details from the API why the key exchange / connection fails. I suggest you take a look at the most common error threads and our Troubleshooting Guide at GitHub. - Оцінка 5 з 5від Lani, 4 місяці томуIt seems that the path for native-messaging-hosts is hardcoded.
I want to move the file located at [~/.mozilla/native-messaging-hosts/org.keepassxc.keepassxc_browser.json] to [xdg-directory :: ~/.config/mozilla], but it fails.
help me? - Оцінка 1 з 5від Ethan, 4 місяці томуit doesn't work when the password is on another page after the email. it always puts the wrong password from another account without even asking which account. developers, add a dropdown to ask the user from which account to take the password, don't just put any random password from any random account in the database. changing any setting didn't fix this.
Відповідь розробника
оприлюднено 4 місяці томуFirst of all, this shouldn't happen. There's already a dropdown selector when filling usernames or password from multiple accounts. Selector from the popup works as well. There are some settings that try to fill the password automatically for the selected username. Disabling those should help. If not, please file an issue to GitHub, thanks. - Оцінка 5 з 5від A1, 4 місяці тому
- Оцінка 5 з 5від ProgramminCat, 4 місяці тому
- Оцінка 5 з 5від Xol, 5 місяців тому
- Оцінка 5 з 5від Користувач Firefox 16478816, 5 місяців тому
- Оцінка 5 з 5від Ryan Steed, 5 місяців тому
- Оцінка 5 з 5від Користувач Firefox 19642928, 5 місяців тому
- Оцінка 4 з 5від Enunciate_Veggie, 5 місяців тому