Отзывы на «KeePassXC-Browser»
KeePassXC-Browser от KeePassXC Team
Отзывы ha3flt
Оценено на 3 из 5
от ha3flt, 3 года назадIt would be fair to mention everywhere the well-known problem with snaps on Ubuntu that dramatically cripples the usability of this otherwise great software. Ubuntu is just the largest Linux distribution by far, and you've lost it...
As I said some years ago, you need an alternative way of communication. Shouldn't be so hard, Mozilla Docs says you can use sockets to communicate with local applications (by Native messaging). It's presumably just plain TCP/IP. Even password managers are mentioned as examples...
Time has come - already in 2021 but I postponed the upgrade so far -, and there is no apt-based version of FireFox as a second choice anymore in Ubuntu, only the Snap Store-based, so we are doomed. I will not go backward installing a browser from a place out of the Ubuntu's own ecosystem. Thank you.
---
My response to your response:
Thank you, but an alternative means an alternative. If not the Native Messaging then an encrypted file or similar would have been developed as a way of communication. We talk about years... No way that a FireFox extension can't and couldn't communicate with the outer world.
But as I'm reading here, see the link below that is really easy to find, no doubt, the problem not handling the Native Messaging correctly is in the browsers themselves, and it is already _solved_ after some years in FireFox (in 105..108 betas so far), KeePassXC is working (!) in the tests, I'm about to try it soon. So you are also not informed well enough for some reason...
https://forum.snapcraft.io/t/call-for-testing-native-messaging-support-in-the-firefox-snap/31055/36
It is only in the Beta channel until the next version of FireFox, probably since it is a fresh development from this summer, but it is OK to me because there is a snap of every FireFox beta as well in Ubuntu, and I can install it in parallel to the non-beta version for now if I want.
As I told you, Ubuntu decided sometimes earlier to go with only the snap version of browsers and even if I'm not hundred percent sure it is the best way to go forward, I will not install the less safe and unsupported apt version of browsers again.
As I said some years ago, you need an alternative way of communication. Shouldn't be so hard, Mozilla Docs says you can use sockets to communicate with local applications (by Native messaging). It's presumably just plain TCP/IP. Even password managers are mentioned as examples...
Time has come - already in 2021 but I postponed the upgrade so far -, and there is no apt-based version of FireFox as a second choice anymore in Ubuntu, only the Snap Store-based, so we are doomed. I will not go backward installing a browser from a place out of the Ubuntu's own ecosystem. Thank you.
---
My response to your response:
Thank you, but an alternative means an alternative. If not the Native Messaging then an encrypted file or similar would have been developed as a way of communication. We talk about years... No way that a FireFox extension can't and couldn't communicate with the outer world.
But as I'm reading here, see the link below that is really easy to find, no doubt, the problem not handling the Native Messaging correctly is in the browsers themselves, and it is already _solved_ after some years in FireFox (in 105..108 betas so far), KeePassXC is working (!) in the tests, I'm about to try it soon. So you are also not informed well enough for some reason...
https://forum.snapcraft.io/t/call-for-testing-native-messaging-support-in-the-firefox-snap/31055/36
It is only in the Beta channel until the next version of FireFox, probably since it is a fresh development from this summer, but it is OK to me because there is a snap of every FireFox beta as well in Ubuntu, and I can install it in parallel to the non-beta version for now if I want.
As I told you, Ubuntu decided sometimes earlier to go with only the snap version of browsers and even if I'm not hundred percent sure it is the best way to go forward, I will not install the less safe and unsupported apt version of browsers again.
Ответ разработчика
размещено 3 года назадThe problem here is with Ubuntu Snaps, not with our extension. And the problem is.. with the Native Messaging support. Other extensions are affected too. At this point Ubuntu 22.10 should already support our extension with Firefox as Snap. You can find the info easily. It's also possible to install apt version of Firefox.
We have been using Native Messaging with the extension since the development started in 2016-2017.
We have been using Native Messaging with the extension since the development started in 2016-2017.
735 отзывов
- Оценено на 5 из 5от Cangrejo, 5 дней назад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, 11 дней назад
- Оценено на 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, 20 дней назад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."
Ответ разработчика
размещено 20 дней назад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 месяца назад