Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:20:50Zhttps://gitlab.torproject.org/legacy/trac/-/issues/8173Amazon Cloud instructions for port forwarding2020-06-13T17:20:50ZcypherpunksAmazon Cloud instructions for port forwardingThe caption in picture six should also mention port 52176:
https://cloud.torproject.org/#get_started
Maybe that's the right moment to update the Amazon EC2 Cloud images to include pyobfsproxy?The caption in picture six should also mention port 52176:
https://cloud.torproject.org/#get_started
Maybe that's the right moment to update the Amazon EC2 Cloud images to include pyobfsproxy?https://gitlab.torproject.org/legacy/trac/-/issues/6883Separate configuration options for separate Socks/NATD/Trans/DNS ports2020-06-13T14:22:57ZgrarpampSeparate configuration options for separate Socks/NATD/Trans/DNS portsVarious config, actions and policies such as...
trackhostexits
mapaddress
newnym
circuit/exit isolation
etc
have an affect on Tor as a whole. The recent addition
of multiple *Ports capability leads to the idea that
Tor could be exte...Various config, actions and policies such as...
trackhostexits
mapaddress
newnym
circuit/exit isolation
etc
have an affect on Tor as a whole. The recent addition
of multiple *Ports capability leads to the idea that
Tor could be extended capable of serving multiple
needs with one daemon. The only way to do this now
is with multiple daemons... which wouldn't take advantage
of certain shared knowledge, and is inefficient from
system resource and admin perspective.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/3511Automatically chosen published ports should be stable2020-06-13T14:13:07ZNick MathewsonAutomatically chosen published ports should be stableTor 0.2.2.x adds the ability to configure ports with "FooPort auto", and get Tor to choose a port on its own. However, these ports will almost certainly not be the same across invocations of Tor, which makes them unsuitable for ORPort a...Tor 0.2.2.x adds the ability to configure ports with "FooPort auto", and get Tor to choose a port on its own. However, these ports will almost certainly not be the same across invocations of Tor, which makes them unsuitable for ORPort and DirPort usage.
Tor should record the values chosen for published (that is, ORPort and DirPort) "auto" ports, and try to reuse them in later invocations. Of course, if those ports aren't available, it'll need to choose a new port anyway.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/7718Vidalia network settings: specified allowed ports disappear after editing torc2020-06-13T02:13:35ZTracVidalia network settings: specified allowed ports disappear after editing torcBug in Vidalia -> Settings -> Network tab:
If "My firewall only lets me connect to certain ports" is marked, the specified "Allowed ports:" often disappear after editing torc.
This bug is not consistent. When it occurs, the Vidalia Mes...Bug in Vidalia -> Settings -> Network tab:
If "My firewall only lets me connect to certain ports" is marked, the specified "Allowed ports:" often disappear after editing torc.
This bug is not consistent. When it occurs, the Vidalia Message Log then reports that the bridge becomes unreachable by our firewall policy (since its port disappears from the allowed list).
It takes multiple repeated attempts to specify the ports again before they are retained.
**Trac**:
**Username**: bugcatcherTomas ToucedaTomas Touceda