Skip to content
This repository has been archived by the owner on Sep 16, 2024. It is now read-only.

target DNS gets resolved prior to proxy connect (MITM) #45

Closed
GlenDC opened this issue Feb 21, 2023 · 1 comment · Fixed by #47
Closed

target DNS gets resolved prior to proxy connect (MITM) #45

GlenDC opened this issue Feb 21, 2023 · 1 comment · Fixed by #47

Comments

@GlenDC
Copy link
Contributor

GlenDC commented Feb 21, 2023

The MITM Proxy receives a resolved IP address of the target to connect to. This works for most providers but some providers seem to result in undesired behaviour such as wrong upstream proxy selection when going via the target IP address on connect instead of the actual DNS.

Currently one can hack around this — if your provider allows dynamic parts in the proxy url — by including socks5h somewhere in the url, as the MITM proxy Typescript code checks on this. It's however far from ideal.

Better would be to either make this opt-out or opt-in. So that at least we can disable it for the proxy providers that we know it causes issues for.

@GlenDC
Copy link
Contributor Author

GlenDC commented Feb 21, 2023

More info regarding the proxy provider. Apparently they do not allow by default to target IP addresses (for reasons), and as such this is why we get issues when using target addresses instead of DNS addresses.

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

Successfully merging a pull request may close this issue.

1 participant