Pógódnośenja za KeePassXC-Browser
KeePassXC-Browser wót KeePassXC Team
Pógódnośenja wót Wužywaŕ Firefox 17086033
Z 1 z 5 pógódnośony
wót Wužywaŕ Firefox 17086033, prije 4 godineThis addon works by connecting to the KeepassXC program and filling login fields with the passwords from the Keepass vault.
It works extremely poorly for a number of reasons:
First: It does not reliably connect to the KeepassXC program. It will occasionally disconnect and require you to restart KeepassXC before connecting again.
Second: The password fill feature fails far more often than it works. I would estimate that I can only successfully fill password forms on 5 to 10% of the websites I visit.
Third: When the auto-fill feature does work, it is frequently followed by an erroneous "your password has changed" prompt asking if you want to create a new entry for the site you literally just filled in.
Fourth: The user interface is minimalist to a fault. You are given no indication as to why the program cannot or will not fill the password fields. Is it because it doesn't think I have a password for the domain? Has it lost the connection? Is there some invisible blocking me from clicking on the password icon? There is no way to tell, the addin simply doesn't respond.
I am using KeepassXC 2.6.6 and browser extension version 1.7.9.1
It works extremely poorly for a number of reasons:
First: It does not reliably connect to the KeepassXC program. It will occasionally disconnect and require you to restart KeepassXC before connecting again.
Second: The password fill feature fails far more often than it works. I would estimate that I can only successfully fill password forms on 5 to 10% of the websites I visit.
Third: When the auto-fill feature does work, it is frequently followed by an erroneous "your password has changed" prompt asking if you want to create a new entry for the site you literally just filled in.
Fourth: The user interface is minimalist to a fault. You are given no indication as to why the program cannot or will not fill the password fields. Is it because it doesn't think I have a password for the domain? Has it lost the connection? Is there some invisible blocking me from clicking on the password icon? There is no way to tell, the addin simply doesn't respond.
I am using KeepassXC 2.6.6 and browser extension version 1.7.9.1
Wótegrono wuwijarja
jo se napisał prije 4 godineThank you for the feedback. If any of these issues are not solved, please open a ticket at GitHub.
First: This sounds like the keepassxc-proxy that is transferring the messages between the extension and KeePassXC is shutdown. This might be due to anti-virus software or some other process that interferes with it. The next time this happens, check if the process is running.
Second: Please use as simple URL's as possible in your entries. If the site you're using is for example https://loginpage.example.com/login/something?yes=no, the best entry URL for this kind of page is https://loginpage.example.com/login/, https://loginpage.example.com (or just https://example.com).
Third: This means even after filling it doesn't regognize an entry from that page. Verify the page and entry URL again.
Fourth: Yes. It's very minimal. Notifications on why the filling doesn't work needs to be added so there's some indication to the user why nothing happens. If you've lost the connection totally, the icon should be gray with and X (or gray with a lock icon if database is closed).
First: This sounds like the keepassxc-proxy that is transferring the messages between the extension and KeePassXC is shutdown. This might be due to anti-virus software or some other process that interferes with it. The next time this happens, check if the process is running.
Second: Please use as simple URL's as possible in your entries. If the site you're using is for example https://loginpage.example.com/login/something?yes=no, the best entry URL for this kind of page is https://loginpage.example.com/login/, https://loginpage.example.com (or just https://example.com).
Third: This means even after filling it doesn't regognize an entry from that page. Verify the page and entry URL again.
Fourth: Yes. It's very minimal. Notifications on why the filling doesn't work needs to be added so there's some indication to the user why nothing happens. If you've lost the connection totally, the icon should be gray with and X (or gray with a lock icon if database is closed).
736 pógódnośenjow
- Z 4 z 5 pógódnośonywót Fokeu, prije 6 dana
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13156335, prije 6 danaWorks fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- Z 5 z 5 pógódnośonywót Cangrejo, prije mjesecBest password manager ever.
I know this depends of Keepassxc development, but it would be nice if card info can be stored. - Z 5 z 5 pógódnośonywót elsenfox, prije mjesec
- Z 2 z 5 pógódnośonywót Wužywaŕ Firefox 19733088, prije 2 mjesecaEigentlich 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!
- Z 1 z 5 pógódnośonywót John Hills, prije 2 mjesecaThe 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."
Wótegrono wuwijarja
jo se napisał prije 2 mjesecaGitHub 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. - Z 5 z 5 pógódnośonywót Lani, prije 2 mjesecaIt 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? - Z 1 z 5 pógódnośonywót Ethan, prije 2 mjesecait 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.
Wótegrono wuwijarja
jo se napisał prije 2 mjesecaFirst 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. - Z 5 z 5 pógódnośonywót A1, prije 2 mjeseca
- Z 5 z 5 pógódnośonywót ProgramminCat, prije 2 mjeseca
- Z 5 z 5 pógódnośonywót Xol, prije 3 mjeseca
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 16478816, prije 3 mjeseca
- Z 5 z 5 pógódnośonywót Ryan Steed, prije 3 mjeseca
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 19642928, prije 3 mjeseca
- Z 4 z 5 pógódnośonywót Enunciate_Veggie, prije 3 mjeseca
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13447327, prije 3 mjeseca
- Z 5 z 5 pógódnośonywót Thrillhouse, prije 4 mjeseca
- Z 4 z 5 pógódnośonywót Helkin, prije 4 mjesecaGreat 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 - Z 1 z 5 pógódnośonywót FartPie, prije 4 mjesecaCurrently 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.Wótegrono wuwijarja
jo se napisał prije 4 mjesecaDear 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. - Z 5 z 5 pógódnośonywót Davide, prije 4 mjeseca
- Z 5 z 5 pógódnośonywót ESM44, prije 5 mjeseci
- Z 5 z 5 pógódnośonywót Omar Kotb, prije 5 mjeseci