Recenzje dodatku KeePassXC-Browser
KeePassXC-Browser Autor: KeePassXC Team
Autor recenzji: Myster
Ocena: 2/5
Autor: Myster, 6 lat temuJust 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.
Odpowiedź autora
Data: 6 lat temuThe 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.
743 recenzje
- Ocena: 5/5Autor: SilverAmd, 19 godzin temu
- Ocena: 5/5Autor: Użytkownik Firefoksa 19902880, 3 dni temu
- Ocena: 5/5Autor: Craig, 4 dni temu
- Ocena: 5/5Autor: Użytkownik Firefoksa 19882925, 15 dni temu
- Ocena: 5/5Autor: Użytkownik Firefoksa 18863959, 24 dni temu
- Ocena: 1/5Autor: Użytkownik Firefoksa 14868755, miesiąc temuNot able to add connected database. Nothing happens when clicking the Connect Database button. Bazzite 43 (linux) NVIDIA edition, Firefox 149, KeePassXC 2.7.12
- Ocena: 4/5Autor: Saturnus, miesiąc temu
- Ocena: 4/5Autor: Fokeu, miesiąc temu
- Ocena: 5/5Autor: Użytkownik Firefoksa 13156335, miesiąc temuWorks fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- Ocena: 5/5Autor: Cangrejo, 2 miesiące temuBest password manager ever.
I know this depends of Keepassxc development, but it would be nice if card info can be stored. - Ocena: 5/5Autor: elsenfox, 3 miesiące temu
- Ocena: 2/5Autor: Użytkownik Firefoksa 19733088, 3 miesiące temuEigentlich 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!
- Ocena: 1/5Autor: John Hills, 3 miesiące temuThe 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."
Odpowiedź autora
Data: 3 miesiące temuGitHub 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. - Ocena: 5/5Autor: Lani, 3 miesiące temuIt 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? - Ocena: 1/5Autor: Ethan, 4 miesiące temuit 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.
Odpowiedź autora
Data: 4 miesiące temuFirst 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. - Ocena: 5/5Autor: A1, 4 miesiące temu
- Ocena: 5/5Autor: ProgramminCat, 4 miesiące temu
- Ocena: 5/5Autor: Xol, 4 miesiące temu
- Ocena: 5/5Autor: Użytkownik Firefoksa 16478816, 4 miesiące temu
- Ocena: 5/5Autor: Ryan Steed, 4 miesiące temu
- Ocena: 5/5Autor: Użytkownik Firefoksa 19642928, 4 miesiące temu
- Ocena: 4/5Autor: Enunciate_Veggie, 4 miesiące temu
- Ocena: 5/5Autor: Użytkownik Firefoksa 13447327, 5 miesięcy temu