Skip to content
Permalink
Browse files
Add TOR_PT_OUTBOUND_BIND_ADDRESS support.
This patch adds support for the TOR_PT_OUTBOUND_BIND_ADDRESS variable to
both PT proxies and servers.

See: https://bugs.torproject.org/5304
  • Loading branch information
ahf committed May 18, 2019
1 parent e1ad77e commit c5ed6c20a9c38c15bae61821d81a97bc79e59b9c
Showing with 23 additions and 0 deletions.
  1. +23 −0 pt-spec.txt
@@ -216,6 +216,29 @@ Table of Contents

TOR_PT_EXIT_ON_STDIN_CLOSE=1

"TOR_PT_OUTBOUND_BIND_ADDRESS"

Specifies an IP address that the PT proxy or server SHOULD use as source

This comment has been minimized.

Copy link
@NullHypothesis

NullHypothesis May 19, 2019

The rest of the specification talks about a "client proxy" and "server proxy," or a "forward proxy" and "reverse proxy," but not "proxy" and "server." I think we should be consistent with this naming scheme.

address for outgoing IP connections. This feature allows people with multiple

This comment has been minimized.

Copy link
@NullHypothesis

NullHypothesis May 19, 2019

Nitpick: I would write "IP packets" instead of "IP connections."

network interfaces to specify explicitly which interface they prefer the PT to
use.

If this value is unset or empty the PT MUST use the default source

This comment has been minimized.

Copy link
@NullHypothesis

NullHypothesis May 19, 2019

Nitpick: There's a missing comma after "empty."

address for outgoing connections.

This setting MUST be ignored for connections to
loopback addresses (127.0.0.0/8 and [::1]).

IPv6 addresses MUST always be wrapped in square brackets.

Example with IPv4:

TOR_PT_OUTBOUND_BIND_ADDRESS=203.0.113.4

Example with IPv6:

TOR_PT_OUTBOUND_BIND_ADDRESS=[2001:db8::4]

3.2.2. Pluggable Transport Client Environment Variables

Client-side Pluggable Transport forward proxies are configured

0 comments on commit c5ed6c2

Please sign in to comment.