On Sun, 25 Jun 2017 18:25:00 +
nusenu wrote:
> I'm aiming to enable tor's 'Sandbox' feature by default on Debian based
> relays starting with the next release of ansible-relayor [1].
>
> Before doing so I'd like to collect some feedback from tor relay
> operators willing to test this feature
> On 5 Jul 2017, at 10:36, Igor Mitrofanov wrote:
>
>> Port numbers and TLS ore orthogonal: port 443 can be used for cleartext,
>> and port 80 for encrypted traffic. In the case of IRC, it's quite common
>> for 6667 to be used with TLS.
>
> When a relay operator uses exit policies, I believe th
> On 5 Jul 2017, at 10:27, Fof582 wrote:
>
>> Most tor clients send a DNS name, and flags that say whether they
>> allow IPv4 and IPv6, and which one they prefer. They rely on the Exit
>> to resolve the IP address and connect to the site.
>>
>> On the current network, an IPv6-only Exit won"t ge
> Port numbers and TLS ore orthogonal: port 443 can be used for cleartext,
> and port 80 for encrypted traffic. In the case of IRC, it's quite common
> for 6667 to be used with TLS.
When a relay operator uses exit policies, I believe they express an
intent to block certain types of applications, a
> Most tor clients send a DNS name, and flags that say whether they
> allow IPv4 and IPv6, and which one they prefer. They rely on the Exit
> to resolve the IP address and connect to the site.
> On the current network, an IPv6-only Exit won"t get the Exit flag, and
> therefore won"t get much client
t...@t-3.net:
>
> The files in the repo location we have configured have not changed
> recently, and I know that Tor's been updated.
>
> The repo we're configured for is based out of:
>
> https://deb.torproject.org/torproject.org/rpm/el/6/x86_64
That repo is unmaintained, don't use it.
unfor
> On 5 Jul 2017, at 05:29, grarpamp wrote:
>
>>> ...
>>>
>>> My current, rather paranoid, list of accepted ports looks like this:
>>> 20-21, 53, 443, 993, 995, 6667. I am not sure how useful this is to
>>> Tor, and whether I will actually avoid complaints, but I guess I can
>>> only wait and se
>> at the "cry" relay (one of top 10) - it is not marked as "Exit" as it
>
> It means that clients won't chose the relay for preemptive exit circuits.
> I think it might get some other Exit usage, but I'm not sure.
Users (various technical folks) sometimes configure traffic though
exits lacking th
> On 5 Jul 2017, at 00:18, Igor Mitrofanov wrote:
>
> Hi,
>
> I am trying to run a few Exit relays on my 1 gbps connection. To keep
> donating the exit capacity to the Tor project I have to keep abuse
> reports to a minimum.
>
> In order to have the Exit flag I have read that I have to keep tw
Hi,
I am trying to run a few Exit relays on my 1 gbps connection. To keep
donating the exit capacity to the Tor project I have to keep abuse
reports to a minimum.
In order to have the Exit flag I have read that I have to keep two of
ports 80, 443 and 6667 open, plus allow exiting to at least one
10 matches
Mail list logo
