- 5 段階中 5 の評価Ardb によるレビュー (9ヶ月前)My previous opinion was wrong. I realized that sometimes it collides with browser's native password management. And of course the extension is very sensitive to url format, including correct protocol (https vs http) which is actually a virtue! After a bit of struggle I must say that this extension performs very well (on Debian)
I'm leaving my old opinion, maybe it will help someone:
Does not fill username nor password on almost all sites (keepass icons on user/pass fields is sometimes grayed out, sometimes not but it doesn't matter. Firefox or Chrome? Doesn't matter. Fill option doesn't work, keyboard shortcut doesn't work when database is connected (but password generator works!). No KeepassXC option in right-click menu. Surprisingly it works correctly for github (the only working site I found in my basket) which ensures me that I perfectly know what I'm doing.Probably the OS keyboard shortcuts collide with the ones in the extension's. You can modify the shortcuts from your browser. If the filling does not work, the issue seems that you are using incorrect URL's in your entries. You must define them with the simplest form possible. For example a page with URL https://www.example.com/login_page/ works great with entry URL defined as https://example.com. That works as a wildcard for https://*.example.com/*.
For Debian it's recommended to use the PPA or AppImage because the default repository often offers an old KeePassXC version.
- 5 段階中 3 の評価ha3flt によるレビュー (9ヶ月前)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...
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.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.
- 5 段階中 3 の評価aa357 によるレビュー (9ヶ月前)Can you please tell me how to make it apply passwords to both password fields? Currently when I click on generate password on a password field it applies a password only on that field and when I click on generate password on the second field it a different password. Also when pressing on the add-on it just says "redetect password fields" which is why I have to do each field like described above.