search

pfn / passifox

Extensions to allow Chrome and Firefox (4.0+) to auto form-fill passwords from KeePass (requires KeePassHttp)
GNU General Public License v3.0
903 stars 185 forks source link

Problems with (Foxy)Proxy #77

Open daincredibleholg opened 12 years ago

daincredibleholg commented 12 years ago

Hi.

I use Firefox really seldom. But if I use it, I normally use it because of the "better" proxy configuration (Chrome uses the system proxy). To have all the proxy settings just one click ahead, I use the FoxyProxy Basic AddOn. Now comes the issue: If use a Socks proxy (doesn't really matter if I use the built-in proxy setup or the FoxyProxy AddOn) the access to my KeePass store is broken. The reason is clear: Using Socks proxies, the name resolving is done on the proxy site and there, no KeePass is running. First, I tried to add some Blacklist rules - I configured localhost:19445 and 127.0.0.1:19445 to be not passed thru the proxy. But it seems, the name resolution is still done on proxy side or I have missed additionally needed ports. Long text, short question: Is it possible to provide a configuration flag (and logic ;) ) letting the extension access the KeePass store directly via https instead of using the normal FF stack that is using the proxy settings?

Hopefully greets, Holger

pfn commented 12 years ago

The correct port is 19455

I don't know if you typod in your description, but give that a shot and let me know

Sent from my phone

Holger reply@reply.github.com wrote:

Hi.

I use Firefox really seldom. But if I use it, I normally use it because of the "better" proxy configuration (Chrome uses the system proxy). To have all the proxy settings just one click ahead, I use the FoxyProxy Basic AddOn. Now comes the issue: If use a Socks proxy (doesn't really matter if I use the built-in proxy setup or the FoxyProxy AddOn) the access to my KeePass store is broken. The reason is clear: Using Socks proxies, the name resolving is done on the proxy site and there, no KeePass is running. First, I tried to add some Blacklist rules - I configured localhost:19445 and 127.0.0.1:19445 to be not passed thru the proxy. But it seems, the name resolution is still done on proxy side or I have missed additionally needed ports. Long text, short question: Is it possible to provide a configuration flag (and logic ;) ) letting the extension access the KeePass store directly via https instead of using the normal FF stack that is using the proxy settings?

Hopefully greets, Holger

Reply to this email directly or view it on GitHub: https://github.com/pfn/passifox/issues/77

daincredibleholg commented 12 years ago

Hi.

Thanks for this really quick reply!

Yeah, it was a typo, sorry! I use 19455, not 19445. Any further ideas?

Cheers, Holger

pfn commented 12 years ago

What happens if you go to http://localhost:19455/ from the browser? It should just result in a blank page without any errors... otherwise, I don't know what is happening here.

daincredibleholg commented 12 years ago

Hi.

Well, as expected I get the empty page, you described, if do not use the SOCKS proxy. If I use it, localhost is not my local machine, it is the proxy server itself. This belongs to the logic, that DNS lookups are done on the SOCKS proxy side, not on the local machine.

Example: I use a socks proxy with the hostname socks.proxy.com. If I do a lookup on localhost, I get the 127.0.0.1 from socks.proxy.com. Without using the proxy, localhost is 127.0.0.1 on my machine.

This behaviour is useful, if you do not have a working / any DNS server accessible from your local network location. Or - and this is sometimes the reason why I use one of my servers - the local DNS servers are regulated / filtering.

To reproduce this on your site, you can simply connect to a server via SSH and configure a dynamic port forwarding. Then, configure your FF (or system) to use the dynamic port forwarding port, you defined during SSH connect command. (Sorry, I do not have the command by the hand right now.)

Thanks for reply!

pfn commented 12 years ago

that's odd, though, localhost should always resolve to 127.0.0.1... unless the proxy somehow interprets that and resolves it as its own IP...

FxRe commented 11 years ago

I believe I have a related issue.

I'm using Chrome and Switchy! to enable custom proxy settings. I have localhost, and 127.0.0.1 all in my exception list. But as soon as I enable the proxy profile in Switchy! ChromeIPass can't connect to KeePaasHttp anymore. When the profile is disabled, http://localhost:19455/ shows a blank page, when enabled it gives me an error 101 (net::ERR_CONNECTION_RESET).

Any ideas or suggestions? If this is unrelated, please tell me where I should post this.

keisonlineshoppe commented 10 years ago

hello, i have a problem with my foxyproxy, it's not working now on my computer. I really don't know what happened and I don't know what to do. I'am using foxyproxy for my job so i need it to work sooner. Please contact me @keisonlineshoppe@gmail.com

Thanks in advance!