April 2018 - tor-relays - lists.torproject.org

Re: [tor-relays] tor-relays Digest, Vol 87, Issue 4
by Jivan Amara 03 Apr '18

03 Apr '18

Hey Jack, Here's my understanding of your concerns, anyone else please chime in if I'm mistaken anywhere. For running a normal relay compared to a client connecting to a relay via obfs4, it's less likely to be discovered by examining the content of traffic. The obfs4 protocol is designed to disguise the connection between a client (i.e. torbrowser). Once the traffic hits a relay, the interaction between relays contains less opportunities to identify it as tor traffic as opposed to any other encrypted traffic. That being said, there are a couple of other things that would make it very easy to identify a TOR relay. First, by default, relays are listed for anyone to examine. Second, if the authorities are watching, the change in traffic to/from your home computer will be pretty obvious. Regarding your concerns about children being inappropriately exposed to the dark web, running a relay will make very little difference compared to not running one. For your children to see the content of the dark web they'll need to install torbrowser (or equivalent) and that's going to be the same whether or not you're running a relay. The only potential difference is that if in your area it's very difficult to connect to the tor network and your children know you're running a relay, with some knowledge they could configure torbrowser to connect first to your relay. In some sense, if the authorities are successful in blocking access to the tor network, you could be enabling their romps on the dark web. HTH Jivan On 04/03/2018 02:38 AM, tor-relays-request(a)lists.torproject.org wrote: > Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > > Today's Topics: > > 1. Re: failed setup of obfs4 on relay (jackoreamnos(a)tutanota.com) > 2. Re: failed setup of obfs4 on relay (jackoreamnos(a)tutanota.com) > 3. Re: Estimation of bridge traffic / Bridge or relay needed? > (jackoreamnos(a)tutanota.com) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 3 Apr 2018 05:00:18 +0200 (CEST) > From: <jackoreamnos(a)tutanota.com> > To: <tor-relays(a)lists.torproject.org> > Cc: <tor-relays(a)lists.torproject.org> > Subject: Re: [tor-relays] failed setup of obfs4 on relay > Message-ID: <L98Ret7--3-0(a)tutanota.com> > Content-Type: text/plain; charset="utf-8" > > Thank you all, that was very helpful. - Jack > > 30. Mar 2018 20:53 by arma(a)mit.edu <mailto:arma@mit.edu>: > > >> On Fri, Mar 30, 2018 at 04:52:23PM -0400, Roger Dingledine wrote: >>> For obfs4, the active prober doesn't know the secret "cert" parameter, >> For far far more detail on the various pluggable transports and how >> they look on the wire, check out this awesome page that David Fifield >> put together: >> >> https://trac.torproject.org/projects/tor/wiki/doc/AChildsGardenOfPluggableT… <https://trac.torproject.org/projects/tor/wiki/doc/AChildsGardenOfPluggableT…> >> >> --Roger >> >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org <mailto:tor-relays@lists.torproject.org> >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays> >

4 3

Re: [tor-relays] The IP of relay 6A7551EEE18F78A9813096E82BF84F740D32B911 has changed
by teor 03 Apr '18

03 Apr '18

> On 2 Apr 2018, at 02:19, tschador(a)posteo.de wrote: > > FYI > > My relay "TorMachine" (FallbackDir) has moved to another ISP. > > New IP is: 94.130.186.5 and will be longterm stable too. Thanks, we are tracking this change in: https://trac.torproject.org/projects/tor/ticket/24805#comment:16 T

1 0

decommissioning 2 fallback directory mirrors
by tor 03 Apr '18

03 Apr '18

I am planning on decommissioning the following 2 relays which have the FallbackDir flag: 175921396C7C426309AB03775A9930B6F611F794 1DBAED235E3957DE1ABD25B4206BE71406FB61F8 They've been running as fallback directory mirrors for 2+ years, but I'm unable to continue running them.

2 1

Outdated relay versions are they secure to use?
by Gary 03 Apr '18

03 Apr '18

Hello. Go to https://check.torproject.org > "...for more info about this relay...relay search" link If I receive a message saying this relay uses an outdated version does that mean that my traffic is any less secure? Does Tor take potentially insecure relay versions in to account when creating circuits? Thanks

3 2

failed setup of obfs4 on relay
by jackoreamnos＠tutanota.com 02 Apr '18

02 Apr '18

Am a novice compiling Tor (0.3.2.9) and been successful using this from a Tor Browser as a private bridge by entering "a.b.c.d:9001" into Tor Browser. However, pointing my Tor Browser to the obfs4 on the same machine fails with something like General SOCKS failure in the log. Below is my torrc: SOCKSPort 0 CookieAuthentication 1 ControlPort 9051 ORPort 9001 ExtORPort auto ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy # ServerTransportListenAddr obfs4 [::]:60443 ServerTransportListenAddr obfs4 0.0.0.0:60443 ExitRelay 0 BridgeRelay 1 PublishServerDescriptor 0 Tests I have done: (1) using obfs4 compiled from git repository, as well as the OS package. (2) opening port 60443, as well as dropping all firewalls - does not make a difference; meanwhile, pointing telnet at a.b.c.d 60443 connects successfully (3) using Tor Browser with default supplied obfs4 bridges works well (log shows I was able to download a list of bridges and their fingerprints). So I think I have ruled out problems with my Tor client (Tor Browser), and I have ruled out firewall configurations on the server, and ruled out obfs4 being blocked on my ISP. Since Tor itself works, and I have tried obfs4 from source as well as from the OS package, the only thing I can think of is something wrong with the config above. Any hints would be appreciated, as well as any steps I can do to further diagnose would be helpful. Thanks, Jack

3 5

running relay excluded from votes
by Dark Matter 01 Apr '18

01 Apr '18

Hello, my relay 69D9FF1BE14B9AE77701A6BCBC075FF837F5AFF9 (darkmatter) disappeared from all votes (and hence from the consensus) starting today at the voting for valid after 07:00:00. Any explanation for this behavior? There is nothing unusual in the relay's logs and there was no reboot today. In my opinion it's strange that a relay suddenly disappears from the votes. If I got it right, usually an authority votes for "not running" if a relay can't be reached for some reason. But ALL votes excluded my relay starting today at seven am. Would like to understand what happened... Bye, Dark

3 2

ansible-relayor, how to ?
by Petrusko 01 Apr '18

01 Apr '18

Hey! I'm planning to try the "ansible-relayor" to deploy some Tor relay instances. If I'm not wrong, it's a main goal ? 2 instances / IP... (soooory for being really noob about this!!!) But I'm lost... not found a tutorial, step by step, you know the tutorial so loved by all noobs! For now, on a fresh Debian8 install, there are : - tor 0.2.9.8 (fresh install from depo, client is ok when opening log file) - ansible - ansible-galaxy install nusenu.relayor - git clone https://github.com/nusenu/ansible-relayor (the folder is stored in my /home...) Will it configure (automatically) many torrc file per instance ? +every key files /relay ? (I'm not too much lost!) Do have I to do this install on every server built ? Or relayor can manage few servers on different locations ? Command lines list use this tool if available ? Many thx for help !!! (and hard work for this tool :) -- Petrusko C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5

6 9