Відгуки для KeePassXC-Browser
KeePassXC-Browser автор KeePassXC Team
Відгук від Gongloss
Оцінка 3 з 5
від Gongloss, 2 роки томуBasically broken, like, apparently, all third-party password extensions.
Often doesn't find passwords for sites. Tells you every single time that you've updated the password and asks if you want to resave it, so you have no way to tell if the password has actually changed. It always says it has, whether it has or it hasn't.
Can't find TOTP codes even when they're in Keepass, you have to go copy them by hand.
All-around seems like a half-finished, "beta" release that is almost ready for use, but not quite.
It is extremely nerve-wracking to constantly be told the password has changed, and have to stop and think about whether it has and whether you want to save it, every single time you log into a site. Worse, you can only see this before you have logged in, before you know if the login was any good... it disappears as soon as you're in.
So, basically, it keeps you on your toes, always keeps you guessing and uncertain about what's going on... exactly what you DON'T EVER WANT A PASSWORD MANAGER TO DO.
Extremely disappointing.
EDIT: Response to the developer's comment below: The user guide, which is one mammoth long page from a page 2 or 3 levels deep on the website, contains one instance each of the phrases "new password" and "banner", neither telling me anything about how to fix this. I searched for the word "changed" too, that doesn't appear anywhere in the document at all.
Also, when you do need to use that banner, the buttons don't do anything. Click them, they sit there. Did they work? Did they not? Did anything get saved? No way to know.
I truly hate to criticize a FOSS project but this is really just awful design, to the point I don't trust this thing. If I don't know when passwords are new or not, or whether it's saving them or not, and I have to scour a huge 12,000 word single-page wall of text that doesn't turn up the information I need even when I search it for the specific terms the developer told the manual would instruct me on, so I can't find the new password banner settings by searching for "new password" or "banner" then, sorry, I have to nope out on it. I'm just not reading a 12,000 word manual to figure out how to use a password manager.
Just for fun, I printed the gargantuan "manual" page to a PDF. It's a single page that's 49 pages long when printed. That's what I'm expected to have read just to figure out how to get a password manager to work. That's not a user manual, it's a novella.
I scrolled slowly through the eldritch document's 78 different screenshots to see if there was one of the banner in question, to maybe tip me off where its behavior is documented. If there is one, I could not find it.
I did find the section on the browser integration plugin and read it through carefully, twice. It says nothing about that banner, or how to understand it, or get it to work in a way that seems to make sense. I'll limp along with copying and pasting codes from KeepassXC for TOTP since there's no way I'm going back to Authy or using Google Auth, but for passwords, I've had to go back to the limitations of just using Firefox's built-in password manager. I'd hoped for a better solution than that, but... :-\
Often doesn't find passwords for sites. Tells you every single time that you've updated the password and asks if you want to resave it, so you have no way to tell if the password has actually changed. It always says it has, whether it has or it hasn't.
Can't find TOTP codes even when they're in Keepass, you have to go copy them by hand.
All-around seems like a half-finished, "beta" release that is almost ready for use, but not quite.
It is extremely nerve-wracking to constantly be told the password has changed, and have to stop and think about whether it has and whether you want to save it, every single time you log into a site. Worse, you can only see this before you have logged in, before you know if the login was any good... it disappears as soon as you're in.
So, basically, it keeps you on your toes, always keeps you guessing and uncertain about what's going on... exactly what you DON'T EVER WANT A PASSWORD MANAGER TO DO.
Extremely disappointing.
EDIT: Response to the developer's comment below: The user guide, which is one mammoth long page from a page 2 or 3 levels deep on the website, contains one instance each of the phrases "new password" and "banner", neither telling me anything about how to fix this. I searched for the word "changed" too, that doesn't appear anywhere in the document at all.
Also, when you do need to use that banner, the buttons don't do anything. Click them, they sit there. Did they work? Did they not? Did anything get saved? No way to know.
I truly hate to criticize a FOSS project but this is really just awful design, to the point I don't trust this thing. If I don't know when passwords are new or not, or whether it's saving them or not, and I have to scour a huge 12,000 word single-page wall of text that doesn't turn up the information I need even when I search it for the specific terms the developer told the manual would instruct me on, so I can't find the new password banner settings by searching for "new password" or "banner" then, sorry, I have to nope out on it. I'm just not reading a 12,000 word manual to figure out how to use a password manager.
Just for fun, I printed the gargantuan "manual" page to a PDF. It's a single page that's 49 pages long when printed. That's what I'm expected to have read just to figure out how to get a password manager to work. That's not a user manual, it's a novella.
I scrolled slowly through the eldritch document's 78 different screenshots to see if there was one of the banner in question, to maybe tip me off where its behavior is documented. If there is one, I could not find it.
I did find the section on the browser integration plugin and read it through carefully, twice. It says nothing about that banner, or how to understand it, or get it to work in a way that seems to make sense. I'll limp along with copying and pasting codes from KeepassXC for TOTP since there's no way I'm going back to Authy or using Google Auth, but for passwords, I've had to go back to the limitations of just using Firefox's built-in password manager. I'd hoped for a better solution than that, but... :-\
Відповідь розробника
оприлюднено 2 роки томуIf a password is always offered to a site, or it doesn't find your passwords, your entry URL is probably incorrect. Use the simplest possible form of the URL, for example https://example.com.
Users can modify the settings how the new password created banner is displayed. Reading the User Guide is highly recommended.
Users can modify the settings how the new password created banner is displayed. Reading the User Guide is highly recommended.
735 відгуків
- Оцінка 5 з 5від Cangrejo, 6 днів тому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, 12 днів тому
- Оцінка 2 з 5від Користувач Firefox 19733088, 14 днів тому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, 21 день тому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."
Відповідь розробника
оприлюднено 21 день тому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, місяць тому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, місяць тому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.
Відповідь розробника
оприлюднено місяць тому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, місяць тому
- Оцінка 5 з 5від ProgramminCat, місяць тому
- Оцінка 5 з 5від Xol, 2 місяці тому
- Оцінка 5 з 5від Користувач Firefox 16478816, 2 місяці тому
- Оцінка 5 з 5від Ryan Steed, 2 місяці тому
- Оцінка 5 з 5від Користувач Firefox 19642928, 2 місяці тому
- Оцінка 4 з 5від Enunciate_Veggie, 2 місяці тому
- Оцінка 5 з 5від Користувач Firefox 13447327, 2 місяці тому
- Оцінка 5 з 5від Thrillhouse, 3 місяці тому
- Оцінка 4 з 5від Helkin, 3 місяці томуGreat extension, love this on my Fedora 43 computer.
I would have love to have this work on Bazitte with it’s firefox in a flatpak - Оцінка 1 з 5від FartPie, 3 місяці томуCurrently completely broken with more restrictive privacy configurations due to a bug (#2672) that was reported over two months ago and patched over a month ago - and still not released.
I would have thought show stopping bugs would be worth a point release, but apparently not.Відповідь розробника
оприлюднено 3 місяці томуDear FartPie (love the nick btw), we've been collecting a bunch of various fixes and new features for the release, and it will be published soon. The bug you mentioned was not really high-priority, and not affecting many people so it didn't require a separate hotfix release. - Оцінка 5 з 5від Davide, 3 місяці тому
- Оцінка 5 з 5від ESM44, 4 місяці тому
- Оцінка 5 з 5від Omar Kotb, 4 місяці тому
- Оцінка 5 з 5від Користувач Firefox 18499562, 4 місяці тому