-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi,
is there a way to properly configure a relay (ORPort reachable) that has full internet access beside outgoing destination port 80 that will properly work?
Problems: publishing descriptor to authorities that use that port, clients are not aware of this restriction of a relay and will try to build circuits where $nextrelay uses ORPort 80 -> circuit will fail (currently 28 relays use ORPort 80)
I guess one should simply not bother trying to run a relay in such a scenario. Is my assumption correct?
thanks, tagnaq ps: FascistFirewall is for clients only
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On Thu, 28 Apr 2011 15:05:19 +0200 tagnaq tagnaq@gmail.com wrote:
is there a way to properly configure a relay (ORPort reachable) that has full internet access beside outgoing destination port 80 that will properly work?
Problems: publishing descriptor to authorities that use that port, clients are not aware of this restriction of a relay and will try to build circuits where $nextrelay uses ORPort 80 -> circuit will fail (currently 28 relays use ORPort 80)
I guess one should simply not bother trying to run a relay in such a scenario. Is my assumption correct?
Yes, for now. We haven't figured out how to handle network topology restrictions like this safely yet.
Robert Ransom
tor-relays@lists.torproject.org