I would like to opt-in my relay, which is on the candidate list.
pixelminer
CE75BF0972ADD52AF8807602374E495C815DB304
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hereby I want to opt-in the following relays which are present on the
list:
BabylonNetwork02 (fingerprint: 54660C671B47E6986B465B8014BD19E5A34B)
BabylonNetwork03 (fingerprint: C79552275DFCD486B942510EF663ED36ACA1A84B)
And opt-out the next one f
Hi operators,
for a couple of days, I see a little bit more than twice as much inbound than
outbound connections on my (non-exit, non-guard) relay [0]. I have no real
concern about this but I want to explain it to myself somehow.
As my relay has the HSDir flag, I started looking at the statisti
Hey everyone,
This is an advisory for anyone running an exit node, but it also applies
to any Linux setup where you don't trust your DNS server. TL;DR: this is
a guide for switching unsecured DNS to DNSCrypt + Unbound, which
prevents a network host from monitoring DNS lookups, thus increasing
priv
On 12/19/2015 11:23 PM, Jesse V wrote:
> Hey everyone,
>
> This is an advisory for anyone running an exit node, but it also applies
> to any Linux setup where you don't trust your DNS server. TL;DR: this is
> a guide for switching unsecured DNS to DNSCrypt + Unbound, which
> prevents a network hos
>Using DNSCrypt will encrypt
>DNS queries and responses from your Tor relay to the DNSCrypt resolver.
>From that point on you do not know and cannot control how the resolver
>is going to do with DNS queries. And you don't know if that resolver
>uses Google or is compromised or is malicious etc.
W
On 12/19/2015 04:06 PM, Job Pfeiffer wrote:
>
> Why not route all DNS queries through Tor for "Plausible Deniability". The
> nuts and bolts are already there in the client.
>
Tor clients already do that. Tor exits can't do that, as the client
traffic has to reach the clearnet somewhere. It's p
On 19.12.15 16:23, Jesse V wrote:
> 10) I modified /etc/resolv.conf to "nameserver 127.0.53.53".
Good guide, which I implemented on my exit node. But one thing I noticed
from researching. Editing /etc/resolv.conf on Debian will not persist
through a reboot. I followed the instructions here:
http
