mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-24 20:33:31 +01:00
411ec3c0f8
We detect and reject said attempts if there is no chosen exit node or circuit: connecting to a private addr via a randomly chosen exit node will usually fail (if all exits reject private addresses), is always ill-defined (you're not asking for any particular host or service), and usually an error (you've configured all requests to go over Tor when you really wanted to configure all _remote_ requests to go over Tor). This can also help detect forwarding loop requests. Found as part of bug2279.
14 lines
556 B
Plaintext
14 lines
556 B
Plaintext
o Minor bugfixes
|
|
- Avoid a double mark-for-free warning when failing to attach a
|
|
transparent proxy connection. Fixes bug 2279. Bugfix on
|
|
Tor 0.1.2.1 alpha.
|
|
|
|
o Minor features
|
|
- Detect attempts at the client side to open connections to private
|
|
IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with a randomly
|
|
chosen exit node. Attempts to do so are always ill-defined, generally
|
|
prevented by exit policies, and usually in error. This will also
|
|
help to detect loops in transparent proxy configurations.
|
|
|
|
|