- tor-relays - lists.torproject.org

Help us get recent cached consensuses from your relay
by teor 08 Aug '18

08 Aug '18

Hi, Due to a recent CollecTor outage, we are missing consensuses from 2018-08-04 19:00 to 2018-08-05 17:00 UTC. We can recover about 16 of the missing consensuses, but we are still looking for the older 7. If your relay is: * running 0.3.1.1-alpha or later, and it is only using gzip compression, * or it is running on Windows, then it might have some of these consensuses in the diff-cache directory in its DataDirectory (or CacheDirectory). You can run the following command to count the cached consensuses: $ cd diff-cache; cat * | grep -a ^document-type | sort | uniq -c 66 document-type consensus 190 document-type consensus-diff If you have more than 68 consensus files, please take a copy of the diff-cache directory, and let us know where we can download it. Your relay will delete 2 old consensuses every hour. If you’re reading this email N hours after it was sent, your relay needs 68 + 2*N consensuses. T -- teor Please reply @torproject.org New subkeys 1 July 2018 PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ----------------------------------------------------------------------

7 10

Strange Traffic behaviour
by Tobias Sachs 06 Aug '18

06 Aug '18

Hey folks! My relay which is currently hibernating shows something strange. Hibernation is set to 19 TB’s of outgoing Traffic. Hetzner Cloud shows ~16TB outgoing traffic and the relays log itself 38TB. vnstat reports exactly 20.38 TiB tx so in conclusion Hetzner can not count there Bits and Bytes or the same as protection is not correct. Because if Hetzner’s stats are correct i would have send 3 TB’s of Traffic to other Tor servers and clients internally. Because internal traffic is not counted. I guess that a Juniper routers net flow tool is correct so how can i look at this? Because my second relay in Helsinki does have this too with a difference of 2 TB’s. "Heartbeat: Tor's uptime is 27 days 1:39 hours, with 0 circuits open. I've sent 38486.76 GB and received 38489.42 GB. We are currently hibernating.“ When i divide that by two this gives me 19 TB’s of outgoing Traffic. So i guess that this is a bug? Thanks! Tobias

10 22

contact for 'kommissarov'
by nusenu 05 Aug '18

05 Aug '18

Hi, please drop me an email if you are the operator of: https://metrics.torproject.org/rs.html#details/D1E99DE1E29E05D79F0EF9E083D1… thanks, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Canned Abuse Response
by conrad＠rockenhaus.com 05 Aug '18

05 Aug '18

Hello, I'm just curious, does anyone happen to have a canned abuse response that contains the safe harbor provisions of the DCMA? I figured I would ask before I wrote up a really long email. Thanks, Conrad -- Conrad Rockenhaus Fingerprint: 8049 CDBA C385 C451 3348 776D 0F72 F2B5 26DA E93F Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x0F72F2B526DAE93F https://www.rockenhaus.com ------ Get started with GreyPony Anonymization Today! https://www.greyponyit.com

3 2

Emails
by conrad＠rockenhaus.com 04 Aug '18

04 Aug '18

I'm suddenly without my tor-relays emails and I'm beginning to withdrawal.... test 1...2...3? Thanks, Conrad -- Conrad Rockenhaus Fingerprint: 8049 CDBA C385 C451 3348 776D 0F72 F2B5 26DA E93F Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x0F72F2B526DAE93F https://www.rockenhaus.com ------ Get started with GreyPony Anonymization Today! https://www.greyponyit.com

4 3

Tor exit is running but persistently listed as offline by Relay Search
by Ralph Seichter 03 Aug '18

03 Aug '18

Folks, I can't figure out why Relay Search is listing the FreeBSD Tor exit node with fingerprint DB00AF98D21464157AF37BE071F858C56F5220F3 as offline. I have last rebooted the node approx. 24 hours ago, and according to the logs Tor is alive (and 'ps' shows Tor is consuming CPU cycles). I have verified IPv4 and IPv6 connectivity and cannot spot any trouble. Any ideas? The sister exit node (Debian) with near-identical config is chugging along fine. -Ralph

3 3

NTP and tor
by Michael Brodhead 03 Aug '18

03 Aug '18

I brought up my first relay over the weekend and I am waiting for traffic to ramp up. In a few places I've read the suggestion to use NTP to keep the relay's clock in sync. Fair enough, but now there is a problem... I've been reading up on NTP a bit and using ntpdate to occasionally update the system time is now deprecated. We're supposed to run ntpd. Ntpd docs make it sound like ntpd needs to run a listener to function at all. I'd rather not add additional attack surface to my relay. Those of you who run relays, how are you keeping your system clock in sync? My relay is on FreeBSD 11. Thanks, ---mkb

5 7

dir port on non exit
by TorGate 02 Aug '18

02 Aug '18

Hi again, is the dir port on a nonexit node a god ide ? TorGate torgate(at)linux-hus.dk

4 6

Question regarding variables in torrc
by conrad＠rockenhaus.com 02 Aug '18

02 Aug '18

Hello All, I haven't had a chance to experiment with it yet, but can I source a variable from the tor startup script, let's say the IPv6 address of an instance, and define that within torrc as follows ORPort [$Instance_IPv6_ADDR]:443 I'm sure if it's possible it would of already been done. I just wanted to see if there was an easy fix for simplifying templates for end users. Thanks, Conrad -- Conrad Rockenhaus Fingerprint: 8049 CDBA C385 C451 3348 776D 0F72 F2B5 26DA E93F Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x0F72F2B526DAE93F https://www.rockenhaus.com ------ Get started with GreyPony Anonymization Today! https://www.greyponyit.com

3 2

ExtOrPort settings for obsf4, obfs3 and firewall
by Cristian Consonni 02 Aug '18

02 Aug '18

Hi, Form the instructions to install obsf4: https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4… --- ``` ExtORPort auto ``` [...] ``` [notice] Registered server transport 'obfs4' at '[::]:46396' ``` Remember the random port associated to your bridge needs to be open for incoming connections. You can find it from the logs: it's 46396 in this example. --- I can assume that using `ExtORPort auto` would mean that potentially any time Tor is restarted or reload a new port will be picked. Furthermore, in this thread[1] it is said: --- [...] ExtORPort tells tor to open a local-only (bound to localhost) socket for getting information from / communicating with obfsproxy --- So, if I want to be sure to know in advance which firewall port I should let open it is better that I choose a fixed port. Also, that port needs only to accept connections from localhost, i.e. the loopback interface? The only port that needs to be reachable from anywhere is the ORPort? Also, in this answer on Tor Stack Exchange[2] it is said that is possible to run both obfs3 and obfs4 from the same bridge. Is this useful/recommended? Also, in the answer: --- I had to make port forwards for the given obfs ports in iptables (easy with gufw) as well as in my hardware (internet-)firewall to make things work. So I am not so sure that the ExORPort is for local connections only as mentioned by Rodger (please let me know if I am wrong here). --- Thanks in advance (I am sorry for the flood of stupid question, but I prefer to ask a stupid question that having things not work and not understanding why...) C [1]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003909.html [2]: https://tor.stackexchange.com/a/6735

3 7