RequestPolicy / requestpolicy

RequestPolicy is a Firefox extension that gives you control over cross-site requests. --- Be sure to look at the dev-1.0 branch as that's where all of the interesting work is happening. See also: https://www.requestpolicy.com/1.0.html
https://www.requestpolicy.com/
107 stars 17 forks source link

RequestPolicy 1.0.0b3 and KeeFox 1.3.1 conflict #427

Open Hanatarou opened 10 years ago

Hanatarou commented 10 years ago

Hello folks,

I would like to report that there is a conflict between RequestPolicy 1.0.0b3 and KeeFox 1.3.1 that prevents KeeFox 1.3.1 from communicating with KeePass password database.

I have updated my KeeFox add-on to version 1.3.1 and after that I am experiencing difficulties to connect to KeePass database using Palemoon version 24.4.1 (x86). I am using KeePass version 2.25 and my OS is Windows 7 x64.

I keep receiving the following message: "KeeFox can not connect to KeePass. A firewall is probably blocking communication on TCP port 12546."

I have disabled one by one my add-ons and found out that the problematic one is RequestPolicy 1.0.0b3. It's blocking KeeFox 1.3.1 from communicating and just after I disable RequestPolicy 1.0.0b3 KeeFox 1.3.1 started working as expected.

I hope it helps debugging the issue.

Best regards,

Hanatarou

luckyrat commented 10 years ago

I'm the main KeeFox developer so I can be fairly confident that the underlying problem relates to #377 because KeeFox uses Web sockets to communicate with a localhost server.

All addons that use web sockets outside of the context of a specific web page will use the Firefox hidden window to initiate the web socket connection (alternative approaches might work but will leak memory or crash). I'm not certain but it seems likely that this hidden window contains an "about:blank" page, hence the link to #377.

Let me know if you want help testing any candidate fix.

Wassss commented 10 years ago

Hello, Same problem here with RequestPolicy 1.0.0b3 and KeeFox 1.3.1. Obliged to disable blocking each time i open firefox to allow KeeFox connection to keepass DB , then re enable blocking. Allowing 127.0.0.1 as destination did solve the problem for me.

regards

spjuliman commented 10 years ago

Hi, as I do not understand geek speak, I do not understand what the guys above are talking about "disable blocking" and "RequestPolicy 1.0.0b3" ... no idea what this means. What is clear to me that KeyFox and KeyPass are quite messed up, and that there is no decent help available (the trouble-shooter tutorial pulls you in a loop of pages with one referencing the other without providing a solution to the TCP port 12546 problem).

Needless to say, I have the same problem as mentioned above with the "KeeFox can not connect to KeePass. A firewall is probably blocking communication on TCP port 12546" message. I have tried to update KeyPass, following the proposed upgrade procedure with the .exe file without uninstalling the old KeyPass. Now I have 2 keypass folders in the Program Files (x86) directory? KeyPass shows a version 2.20.1 (although I installed the newest upgrade KeePass 1.27?), and in a small box the KeePassLibC 1.24. KeyFox on Firefox v18 shows the latest version 1.4.2. I am able to "Launch KeePass" with the KeyFox toolbar button in Firefox, but the button then stays in "Launch KeePass" mode the popup bar appears on top of each webpage saying "you are not logged in to your password database" ... which is not true, I AM LOGGED IN!

Any help greatly appreciated.

luckyrat commented 10 years ago

Please start by uninstalling all versions of KeePass. Note that you may need to do this from your Control panel / Add/Remove programs menu and if you still have KeePass folders left lying around in your Program Files folder, you've probably installed the "Portable" version which does not come with an uninstaller so you can just delete those files.

Once it's all gone, download KeePass 2.27 setup exe and install it on your computer. Then try KeeFox, following the setup instructions if they appear.

Also, please consider upgrading Firefox - that's a very old unsupported and insecure version that might cause problems.

Let us know what happens once you have just one KeePass version installed.

It sounds like your problem does not relate to "RequestPolicy". Do you have that addon installed?

spjuliman commented 10 years ago

Hi,

Thanks! ... but it is not working. I have:

1) uninstalled all versions of keepass and removed all keepass folders from the program folder 2) uninstalled keefox in firefox 3) reinstalled keepass 2.27 (professional version) 4) reinstalled keefox 1.4.2

but the symptoms stay the same:

1) I get the Setup KeeFox page in FF (orange page) 2) ... then immedately the "open database" long in to KeePass window (Master Key) 3) in the browser: "KeeFox can not connect to KeePass. A firewall is probably blocking communication on TCP port 12546"

BTW, it has worked before with Firefox 18, the upgrade of keefox screwed it up. I do not want to move to a newer version of Firefox, because TabGroupsManager will not work with newer versions - an essential tool for my daily work.

Thanks for your help

On 10/07/2014 15:08, luckyrat wrote:

Please start by uninstalling all versions of KeePass. Note that you may need to do this from your Control panel / Add/Remove programs menu and if you still have KeePass folders left lying around in your Program Files folder, you've probably installed the "Portable" version which does not come with an uninstaller so you can just delete those files.

Once it's all gone, download KeePass 2.27 setup exe and install it on your computer. Then try KeeFox, following the setup instructions if they appear.

Also, please consider upgrading Firefox - that's a very old unsupported and insecure version that might cause problems.

Let us know what happens once you have just one KeePass version installed.

It sounds like your problem does not relate to "RequestPolicy". Do you have that addon installed?

— Reply to this email directly or view it on GitHub https://github.com/RequestPolicy/requestpolicy/issues/427#issuecomment-48601521.

luckyrat commented 10 years ago

Hi,

Which version of KeeFox did you upgrade from? I can't think of any reason that any recent version could have caused this behaviour but it's possible you had an older version of KeeFox, which used a different connection system.

If you've never seen the new authorisation screen pictured in the KeeFox 1.3+ upgrade notes, you should give that page a read too.

I know you're very dismissive of the troubleshooting resources we've put together for these situations but I'm fairly sure you will find the answers there. If not, there must be something extremely unusual about your system - I'll try my best to work through your log files to work out what is going on but you need to start by going through all of the advice here: https://github.com/luckyrat/KeeFox/wiki/en-|-Troubleshooting#keefox-toolbar-button-says-launch-keepass

I have taken a fresh look for any circular references in the troubleshooting guide but I just can't see what you are referring to. I'm sure others will appreciate it if you could explain which sections send you in a circle so I can fix it.

spjuliman commented 10 years ago

Hi,

yes, I have seen the authorization screen before, I had some 1.3x version installed, don't remember the exact version. As I said, the authorization had worked before (with my older version of KeePass). Every time I launched KeePass (from within the FF browswer) I got a window with the version and some upgrade notice, but it was not intuitive how to do the upgrade - because it was a sole download link. It was not clear to me whether I needed to uninstall first or just install the newly downloaded version (would be nice to have this information somewhere easily accessible - as done today by most of the software developers). As I said before, I got lost at your website, too much information and the essential one (what do I need to do type information) is hard to find.

The troubleshooting tips don't work. If I use chrome://keefox/content/install.xul I get the orange screen, but when I try to setup KeeFox the normal login window of KeePass pops up, I log in with the master password but it does not connect to KeeFox. Every time I open a new FF window I get the top bar "you are not logged in to your password database", which is kind of annoying. I am frustrated and I might take this think off my computer - sad, because it has worked nicely for years :(

On 13/07/2014 18:07, luckyrat wrote:

Hi,

Which version of KeeFox did you upgrade from? I can't think of any reason that any recent version could have caused this behaviour but it's possible you had an older version of KeeFox, which used a different connection system.

If you've never seen the new authorisation screen pictured in the KeeFox 1.3+ upgrade notes https://github.com/luckyrat/KeeFox/wiki/en-%7C-Upgrading-from-KeeFox-1.2, you should give that page a read too.

I know you're very dismissive of the troubleshooting resources we've put together for these situations but I'm fairly sure you will find the answers there. If not, there must be something extremely unusual about your system - I'll try my best to work through your log files to work out what is going on but you need to start by going through all of the advice here: https://github.com/luckyrat/KeeFox/wiki/en-|-Troubleshooting#keefox-toolbar-button-says-launch-keepass https://github.com/luckyrat/KeeFox/wiki/en-%7C-Troubleshooting#keefox-toolbar-button-says-launch-keepass

I have taken a fresh look for any circular references in the troubleshooting guide but I just can't see what you are referring to. I'm sure others will appreciate it if you could explain which sections send you in a circle so I can fix it.

— Reply to this email directly or view it on GitHub https://github.com/RequestPolicy/requestpolicy/issues/427#issuecomment-48844534.

Radagast commented 9 years ago

I've just switched from lastpass to Keepass/keefox and I'm seeing this issue too. Basically, RP seems blocking the websocket communication between keepass and keefox.

From testing, It seems I can disable blocking in RP, establish the connection between keepass/keefox, then re-enable blocking and it works but it's not ideal.

myrdd commented 9 years ago

@Radagast What's the version of RP you're using? Is it from the Continued project?

If you're having this problem with the RP Continued as well, please report it in https://github.com/RequestPolicyContinued/requestpolicy/issues/427.

Radagast commented 9 years ago

@myrdd. Apologies, I posted in the wrong place. I'm using 1.0.beta8.2. So the aforementioned post needs to move over to RPC.