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).
合計レビュー数: 690
- 5 段階中 5 の評価Firefox ユーザー 16613818 によるレビュー (5日前)
- 5 段階中 5 の評価Firefox ユーザー 18647422 によるレビュー (8日前)
- 5 段階中 3 の評価Firefox ユーザー 17426555 によるレビュー (9日前)Love the extension but it's useless to me until it works in flatpaks. Uninstalling until that's fixed.
- 5 段階中 5 の評価Firefox ユーザー 19026513 によるレビュー (22日前)
- 5 段階中 5 の評価Firefox ユーザー 14310880 によるレビュー (1ヶ月前)
- Fonctionne parfaitement pour moi sous W11/FF137.0.2, mais impossible de le mettre en oeuvre sous Plucky Puffin Kubuntu 25-04.
Je ne sais pas dans quel camp est la balle, mais ce serait bien que conjointement, la communauté Ubuntu, Mozzila et le développeur se donnent la main pour résoudre ce problème, qui semble connu...
Sans quoi, merci pour tout... - 5 段階中 5 の評価Firefox ユーザー 12700628 によるレビュー (2ヶ月前)
- The extension displays this error (On Firefox, Chrome, Brave..):
Error! Error: No login found. www.mon-compte.bouyguestelecom.fr
Normal the URL is this: www.bouyguestelecom.fr/mon-compte
How can this error be corrected?
---
"Use most simple form of the URL possible: bouyguestelecom.fr"
Even the simplest form doesn't work. - 5 段階中 5 の評価Firefox ユーザー 18904690 によるレビュー (3ヶ月前)
- 5 段階中 5 の評価Firefox ユーザー 18305365 によるレビュー (3ヶ月前)
- 5 段階中 5 の評価Firefox ユーザー 18896261 によるレビュー (3ヶ月前)
- 5 段階中 5 の評価Firefox ユーザー 18889164 によるレビュー (3ヶ月前)
- 5 段階中 5 の評価Firefox ユーザー 18877799 によるレビュー (3ヶ月前)
- 5 段階中 3 の評価Firefox ユーザー 18873576 によるレビュー (4ヶ月前)