diff options
author | Alexander Færøy <ahf@torproject.org> | 2019-07-02 20:21:13 +0200 |
---|---|---|
committer | David Goulet <dgoulet@torproject.org> | 2020-10-06 09:30:11 -0400 |
commit | 5f61e19d8a4e96be9e8692777d835dde8d1ea7f8 (patch) | |
tree | 2965fc7099ef48322deba8203968573b15d095f7 /changes | |
parent | 69c1a4ebc369d79b2a58c25926187407a34b511e (diff) | |
download | tor-5f61e19d8a4e96be9e8692777d835dde8d1ea7f8.tar.gz tor-5f61e19d8a4e96be9e8692777d835dde8d1ea7f8.zip |
Expose TOR_PT_OUTBOUND_BIND_ADDRESS_{V4,V6} to Pluggable Transports.
This patch adds support for exposing the environment variables
`TOR_PT_OUTBOUND_BIND_ADDRESS_V4` and `TOR_PT_OUTBOUND_BIND_ADDRESS_V6` to
Pluggable Transport proccesses. These two values will contain the IPv4
and IPv6 address that the user have specified in torrc that they wish
the PT to use for all outgoing IP packets.
It is important to note here that it is up to the indvidual Pluggable
Transport if they are willing to honor these values or ignore them
completely.
One can test this feature using the following dummy PT written in POSIX
shell script:
#!/bin/sh
echo "LOG SEVERITY=warning MESSAGE=\"Value for IPv4: ${TOR_PT_OUTBOUND_BIND_ADDRESS_V4}\""
echo "LOG SEVERITY=warning MESSAGE=\"Value for IPv6: ${TOR_PT_OUTBOUND_BIND_ADDRESS_V6}\""
while true ; do
sleep 1
done
with the following entries in your torrc:
OutboundBindAddressPT 203.0.113.4
OutboundBindAddress 203.0.113.5
OutboundBindAddressPT 2001:db8::4
OutboundBindAddress 2001:db8::5
See: https://bugs.torproject.org/5304
Diffstat (limited to 'changes')
-rw-r--r-- | changes/bug5304 | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug5304 b/changes/bug5304 new file mode 100644 index 0000000000..9afa838129 --- /dev/null +++ b/changes/bug5304 @@ -0,0 +1,6 @@ + o Minor features (pluggable transports): + - Added option OutboundBindAddressPT to torrc. This option allows users to + specify which IPv4 and IPv6 address they want pluggable transports to use + for outgoing IP packets. Tor does not have a way to enforce that the pluggable + transport honors this option so each pluggable transport will have to + implement support for this feature. Closes ticket 5304. |