browser-extension icon indicating copy to clipboard operation
browser-extension copied to clipboard
verified publisher icon mullvad

Proxy for all sites breaks Kee Browser Extension

Open VIEWVIEWVIEW opened this issue 1 year ago • 5 comments

Kee is a browser extension for Firefox. It allows the user to autofill passwords using the credentials from KeePass 2 using an RPC which opens an RPC server on localhost.

When installing the Mullvad Browser Extension and enabling the "Proxy for All Websites" feature, the Kee Browser Extension stops working after a browser restart and can't connect to the KeePass RPC any more. This behaviour only started recently and wasn't the case a few weeks ago before the default proxy was replaced be the "Proxy for All Websites"-switch.

Repro

  1. Ensure KeePass and Kee extension are configured correctly and operational.
  2. Install Mullvad Browser Extension.
  3. Enable the "Proxy for All Websites" feature in the Mullvad extension settings
  4. Restart firefox.
  5. Watch how the connection between Kee and KeePass doesn't work anymore.
  6. It starts working again when disabling the "Proxy for All Websites" feature.

The only workaround is to disable the "Proxy for All Websites" switch, let Kee connect to KeePass, and then enable the "Proxy for All Websites" again.

As I said: this issue only appeared recently and didn't happen in the old versions of Mullvad's Browser Extension

System Info

  • Firefox 124.0
  • Windows 10 x64
  • KeePass 2 2.55
  • Kee 3.11.13 (Oct 18, 2023)
  • Mullvad Browser Extension 0.9.0
  • KeePassRPC 1.16.0

VIEWVIEWVIEW avatar Mar 21 '24 13:03 VIEWVIEWVIEW

This is most probably because we're not excluding properly all localhost requests, see #196

ruihildt avatar Mar 21 '24 14:03 ruihildt

This is most probably because we're not excluding properly all localhost requests, see #196

You mention in the reddit thread that you exclude localhost and 127.0.0.1 and ::1. However, the RPC server is opened on 127.0.0.1 (it's actually a websocket server), therefore it is supposed to work, or?

VIEWVIEWVIEW avatar Mar 21 '24 14:03 VIEWVIEWVIEW

I guess it should, but I don't know.

ruihildt avatar Mar 21 '24 15:03 ruihildt

I guess it should, but I don't know.

Who could know, or what could a way towards fixing this look like? I really like this extension and it would be too sad to not having this fixed :(

VIEWVIEWVIEW avatar Mar 22 '24 17:03 VIEWVIEWVIEW

I'll start by fixing #196.

In parallel, I recommend contacting the creator of this extension, as they probably know better what errors are showing up and what they mean.

ruihildt avatar Mar 22 '24 18:03 ruihildt