KeePassXC-Browser에 대한 리뷰
KeePassXC-Browser 제작자: KeePassXC Team
aWalker 님의 리뷰
It's really a convenience to use this add-on with KeePassXC. But, there been an issue that has been raised several months back :
In my case
Firefox 83
KeePassXC-Browser 1.7.3
Ubuntu 20.04 LTS
`keepassxc-proxy` makes tcp connections to remote servers over internet & transfers data(with 36+ KB/s speed) without user permission under Linux root privileges.
tcp 0 0 192.168.42.245:52470 117.18.237.29:80 ESTABLISHED 20559/keepassxc-pro
tcp 0 392 192.168.42.245:34738 209.216.230.240:443 ESTABLISHED 20225/keepassxc-pro
tcp 1 0 192.168.42.245:49194 172.67.146.206:443 CLOSE_WAIT 20225/keepassxc-pro
tcp 1 0 192.168.42.245:53060 104.20.214.50:443 CLOSE_WAIT 20225/keepassxc-pro
tcp 1 0 192.168.42.245:60362 172.67.153.104:443 CLOSE_WAIT 20225/keepassxc-pro
tcp 25 0 192.168.42.245:39074 151.101.113.137:443 CLOSE_WAIT 20225/keepassxc-pro
tcp 7890 0 192.168.42.245:34738 209.216.230.240:443 CLOSE_WAIT 20225/keepassxc-pro
simple ip2location domain :
104.20.214.50 .... CloudFlare Inc.
117.18.237.29 .... edgecast.com
151.101.113.137 .. fastly.com
172.67.146.206 ... CloudFlare Inc.
172.67.153.104 ... CloudFlare Inc.
209.216.230.240 .. M5 Computer Security
I tried several times, had to lock password-DB out of fear.
This bug/issue is not addressed by Firefox, claim KeePassXC team on their issue-tracker-logs.
I'm in a limbo, is Firefox breaching user privacy without their knowledge; what data is being transferred to remote servers by keepassxc-proxy?
Should I abandon Firefox; isn't it the most secure (or configurable) browser out there?
Should I change passwords of hundreds of accounts now?
I'm using AutoTyping where ever it's possible & often wished they had auto-type separately for Username & Password; you know for pages like firefox or google account logins.
cheers
In my case
Firefox 83
KeePassXC-Browser 1.7.3
Ubuntu 20.04 LTS
`keepassxc-proxy` makes tcp connections to remote servers over internet & transfers data(with 36+ KB/s speed) without user permission under Linux root privileges.
tcp 0 0 192.168.42.245:52470 117.18.237.29:80 ESTABLISHED 20559/keepassxc-pro
tcp 0 392 192.168.42.245:34738 209.216.230.240:443 ESTABLISHED 20225/keepassxc-pro
tcp 1 0 192.168.42.245:49194 172.67.146.206:443 CLOSE_WAIT 20225/keepassxc-pro
tcp 1 0 192.168.42.245:53060 104.20.214.50:443 CLOSE_WAIT 20225/keepassxc-pro
tcp 1 0 192.168.42.245:60362 172.67.153.104:443 CLOSE_WAIT 20225/keepassxc-pro
tcp 25 0 192.168.42.245:39074 151.101.113.137:443 CLOSE_WAIT 20225/keepassxc-pro
tcp 7890 0 192.168.42.245:34738 209.216.230.240:443 CLOSE_WAIT 20225/keepassxc-pro
simple ip2location domain :
104.20.214.50 .... CloudFlare Inc.
117.18.237.29 .... edgecast.com
151.101.113.137 .. fastly.com
172.67.146.206 ... CloudFlare Inc.
172.67.153.104 ... CloudFlare Inc.
209.216.230.240 .. M5 Computer Security
I tried several times, had to lock password-DB out of fear.
This bug/issue is not addressed by Firefox, claim KeePassXC team on their issue-tracker-logs.
I'm in a limbo, is Firefox breaching user privacy without their knowledge; what data is being transferred to remote servers by keepassxc-proxy?
Should I abandon Firefox; isn't it the most secure (or configurable) browser out there?
Should I change passwords of hundreds of accounts now?
I'm using AutoTyping where ever it's possible & often wished they had auto-type separately for Username & Password; you know for pages like firefox or google account logins.
cheers
개발자 답글
5년 전에 게시됨This is not the first time the issues rises its head from the depths.
Here's the KeePassXC-Browser issue: https://github.com/keepassxreboot/keepassxc-browser/issues/100
And here's the Mozilla one: https://bugzilla.mozilla.org/show_bug.cgi?id=1463873
Again: this is a Firefox bug. If you look the connections keepassxc-proxy makes with Chromium-based browsers, you'll see none.
And to clarify: keepassxc-proxy does not make any connections. These are file descriptors that are leaking from the parent process (Firefox).
Here's the KeePassXC-Browser issue: https://github.com/keepassxreboot/keepassxc-browser/issues/100
And here's the Mozilla one: https://bugzilla.mozilla.org/show_bug.cgi?id=1463873
Again: this is a Firefox bug. If you look the connections keepassxc-proxy makes with Chromium-based browsers, you'll see none.
And to clarify: keepassxc-proxy does not make any connections. These are file descriptors that are leaking from the parent process (Firefox).
리뷰 744개
- 5점 만점에 5점Mark Andrew Gerads 님, 10일 전
- 5점 만점에 5점Firefox 사용자 19902880 님, 17일 전
- 5점 만점에 5점Firefox 사용자 19882925 님, 한 달 전
- 5점 만점에 5점Firefox 사용자 18863959 님, 한 달 전
- 5점 만점에 1점Firefox 사용자 14868755 님, 한 달 전Not able to add connected database. Nothing happens when clicking the Connect Database button. Bazzite 43 (linux) NVIDIA edition, Firefox 149, KeePassXC 2.7.12
- 5점 만점에 5점Firefox 사용자 13156335 님, 2달 전Works fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- 5점 만점에 2점Firefox 사용자 19733088 님, 3달 전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 님, 3달 전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."
개발자 답글
3달 전에 게시됨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.
개발자 답글
4달 전에 게시됨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 님, 4달 전
- 5점 만점에 5점Firefox 사용자 16478816 님, 5달 전
- 5점 만점에 5점Ryan Steed 님, 5달 전
- 5점 만점에 5점Firefox 사용자 19642928 님, 5달 전
- 5점 만점에 4점Enunciate_Veggie 님, 5달 전
- 5점 만점에 5점Firefox 사용자 13447327 님, 5달 전