KeePassXC-Browser에 대한 리뷰
KeePassXC-Browser 제작자: KeePassXC Team
ha3flt 님의 리뷰
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점 만점에 2점Firefox 사용자 19733088 님, 18일 전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!
- 5점 만점에 1점John Hills 님, 24일 전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."
개발자 답글
24일 전에 게시됨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. - 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점ProgramminCat 님, 2달 전
- 5점 만점에 5점Firefox 사용자 16478816 님, 2달 전
- 5점 만점에 5점Ryan Steed 님, 2달 전
- 5점 만점에 5점Firefox 사용자 19642928 님, 2달 전
- 5점 만점에 4점Enunciate_Veggie 님, 2달 전
- 5점 만점에 5점Firefox 사용자 13447327 님, 3달 전
- 5점 만점에 5점Thrillhouse 님, 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점Firefox 사용자 18499562 님, 4달 전