as not manipulating traffic. To the extent that that
becomes less true, the notion of behaving exits becomes more detached from
the practical situation.
--- Drake Wilson
___
tor-relays mailing list
tor-relays@lists.torproject.org
https
_full_ TCP other than
the bidirectional octet streams; I forget whether the urgent marker is
passed through, for instance).
So it's not inconsistent to hear those for exit operators WRT Tor's design.
If you think the design is flawed, that's a separate matter.
--- Drake Wilson
Drake Wilson wrote:
But the TCP specification doesn't. Nor is the Tor client signaling
to you that they want an HTTP connection and not a raw TCP connection.
Whether they happen to be passing octets over it that correspond to an
HTTP stream is irrelevant.
Or alternatively, let me put
over it that correspond to an
HTTP stream is irrelevant.
--- Drake Wilson
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
works for host and user
names
(among other things), and passwd is usually needed to map names to UIDs. If
there's
anything that takes a which user should I run as parameter then it'll read
those
two in the process of looking up the user, for instance.
--- Drake Wilson
? Surely not, given that the policy is published in the exit
descriptor. (I can't speak to the legalities of (ii).)
--- Drake Wilson
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor
of connections open
simultaneously, and if it is not permitted to do this it may not
function properly.
Hope this helps.
--- Drake Wilson
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor
