Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leaks actual IP when failing to authenticate #11

Open
dgraziotin opened this issue Jan 12, 2021 · 2 comments
Open

Leaks actual IP when failing to authenticate #11

dgraziotin opened this issue Jan 12, 2021 · 2 comments

Comments

@dgraziotin
Copy link

dgraziotin commented Jan 12, 2021

I accidentally provided wrong authentication details. Checked for my public IP via curl (using the proxy) and found out that my public IP was being used.

Here is the output of docker logs:

2021-01-12 10:59:43.104 7f81ea130b48 Info: Listening on port 8080 on IP address 0.0.0.0
Tue Jan 12 10:59:43 2021 AUTH: Received control message: AUTH_FAILED
2021-01-12 10:59:44.643 7f81ea01cb20 Request: icanhazip.com/
Tue Jan 12 10:59:45 2021 AUTH: Received control message: AUTH_FAILED

I wonder if Privoxy should listen to a specific IP tied to openvpn rather than 0.0.0.0?

@strictboss
Copy link

strictboss commented Aug 31, 2022

Hello! :)
Did you solve the problem? I really need to except IP leakage, but i do not how. Any suggestions?

It is need to block all outgoing traffic from all gateways, except openvnp's one, but it is absent, when auth failed.
Need feature, called killswitch, which will work automatically. Moreover, traffic from the privoxy must be acceptable and answered with error, if openvpn is not connected.

@josearodrigueze
Copy link

Could anyone solve this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants