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

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

Experimental DoS mitigation is in tor master
by Roger Dingledine 11 Mar '18

11 Mar '18

Hi folks, Thanks for your patience with the relay overload issues. We've merged https://bugs.torproject.org/24902 into tor git master. We'll be putting out an 0.3.3.2-alpha release in not too long for wider testing, and eventually backporting it all the way back to 0.2.9, but if you're the sort who enjoys running code from git, now is a great time to try it and let us know of problems and/or successes. Here's the changelog stanza: o Major features: - Give relays some defenses against the recent network overload. We start with three defenses (default parameters in parentheses). First: if a single client address makes too many connections (>100), hang up on further connections. Second: if a single client address makes circuits too quickly (more than 3 per second, with an allowed burst of 90) while also having too many connections open (3), refuse new create cells for the next while (1-2 hours). Third: if a client asks to establish a rendezvous point to you directly, ignore the request. These defenses can be manually controlled by new torrc options, but relays will also take guidance from consensus parameters, so there's no need to configure anything manually. Implements ticket 24902. To repeat that last part: there are a bunch of torrc options you can use to tweak stuff, but you can leave it all at the defaults and it will read its instructions out of the consensus parameters: https://consensus-health.torproject.org/#consensusparams Woo, --Roger

12 22

unreplied conntrack sessions
by Quintin 10 Feb '18

10 Feb '18

nusenu wrote: > If your hoster suspends your server if you exceed 10k concurrent connections > I'm afraid it is probably not suitable for an exit relay The response from the hoster was: > Your server should not have over 20,000 unreplied connections. This is a sign of abuse. What about the exit node causes such abormally high conntrack sessions? Q -- 0101100101000001010010000101010101000001010010000010000001000010 0100110001000101010100110101001100100000010110010100111101010101

3 5

Relays operators meetup @ FOSDEM 2018 ?
by Nicolas Braud-Santoni 03 Feb '18

03 Feb '18

Hi, I might be able to organise a relays operators meetup at FOSDEM, early February. (This is contingent on me being able to come, though.) I wanted to ask whether there are other relay operators who are planning to go, and which times would work; I made a quick poll to this effect : https://framadate.org/HpPbnRwOYNmK6D5G Feel free to add yourself without filling your availability yet, if you will be around but haven't looked at the schedule yet. I know we had the yearly meetup at 34C3 quite recently, but after discussions there it seemed like a good idea to reach out to relays operators who don't necessarily attend congress, to people who don't yet run relays but have questions, and do so in a different context than congress. Best, nicoo

2 4

75 Exit Relays (48 currently running) - AS 197226 SPRINT SA (PL) - No Contact/MyFamily
by nusenu 01 Feb '18

01 Feb '18

Dear anonymous relay operator, thank you for adding so many exit relays this month in AS 197226 SPRINT SA (PL) (netblocks 185.234.218.x and 77.87.79.x) we would really like to keep these relays on the network, but they do not have any contact information and MyFamily configuration set - which is required for such big relay groups. If you are the relay operator, please set a working contactInfo and proper MyFamily configuration and drop an email to bad-relays(a)lists.torproject.org. If they do not hear from you, tor directory authorities might decide remove these relays. It would be a shame to loose so much bandwidth. thanks for your understanding, nusenu +---------------------+-----------------+-------------+------------+---------+---------+------------------------------------------+ | first_seen | IP | tor_version | nickname | or_port | contact | fingerprint | +---------------------+-----------------+-------------+------------+---------+---------+------------------------------------------+ | 2018-01-17 22:00:00 | 185.234.218.37 | 0.3.2.9 | Ceto | 23774 | NULL | 171F6B9BBEC4EBF903CF312CB71CE554F46D8689 | | 2018-01-17 22:00:00 | 185.234.218.34 | 0.3.2.9 | Hera | 25565 | NULL | 75712D28F4744FBECAD2E67250644C7258FA71F6 | | 2018-01-17 22:00:00 | 185.234.218.36 | 0.3.2.9 | Brizo | 25595 | NULL | A44A3AF8B117665AEB200D0D60674177629EBD18 | | 2018-01-17 22:00:00 | 185.234.218.39 | 0.3.2.9 | Helios | 27365 | NULL | 625DC27C540CAE9EF37A8E8851808556AE3E4621 | | 2018-01-17 22:00:00 | 185.234.218.46 | 0.3.2.9 | Rhea | 32736 | NULL | 52E2BC36E8B333561C3F36689C1DF9A384B281AC | | 2018-01-17 22:00:00 | 185.234.218.40 | 0.3.2.9 | Hestia | 28736 | NULL | 983221B0D3E68EF8A1D0D6A1EF2DDCF0BA73F710 | | 2018-01-17 22:00:00 | 185.234.218.31 | 0.3.2.9 | Aphrodite | 25535 | NULL | 7D8EFB8923173FB89EFE457BA2A6B04D7A9C3395 | | 2018-01-17 22:00:00 | 185.234.218.35 | 0.3.2.9 | Zeus | 25575 | NULL | F8ED98209AB9E73420530AA18BABE8AABC4E7619 | | 2018-01-17 22:00:00 | 185.234.218.33 | 0.3.2.9 | Hades | 25555 | NULL | 0875C580CC0F0F7E57727AC3C2233F5E6A58AE28 | | 2018-01-17 22:00:00 | 185.234.218.42 | 0.3.2.9 | Pallas | 30263 | NULL | D3E518F3749F9FC398261EC60B00B3B1D7535E42 | | 2018-01-17 22:00:00 | 185.234.218.38 | 0.3.2.9 | Chaos | 26536 | NULL | 1C49F07147A9113583190D38E58BA40DBECFB9F7 | | 2018-01-17 22:00:00 | 185.234.218.43 | 0.3.2.9 | Styx | 28736 | NULL | D6FC8F1E0FB2FC3AC4634FC26E4E1E4D7E1FB558 | | 2018-01-17 22:00:00 | 185.234.218.41 | 0.3.2.9 | Nyx | 29096 | NULL | 8B200C067525B70930C4D6CB5DE4C7320B0418AC | | 2018-01-17 22:00:00 | 185.234.218.44 | 0.3.2.9 | Tyche | 29736 | NULL | F76368EC7009FB98F81544473B2F709859FB5327 | | 2018-01-17 22:00:00 | 185.234.218.32 | 0.3.2.9 | Apollo | 25545 | NULL | 830227075292332360349D7A5842B1125004DC6D | | 2018-01-17 22:00:00 | 185.234.218.45 | 0.3.2.9 | Uranus | 31837 | NULL | 01F6F2FA7921681EF6CF9DD327D8E1531B249B78 | | 2018-01-17 23:00:00 | 77.87.79.46 | 0.3.2.9 | Artemis | 29384 | NULL | 65B2D3A0E002704B32B751C4238983D83297E5FB | | 2018-01-17 23:00:00 | 185.234.218.49 | 0.3.2.9 | Maia | 32736 | NULL | ECC5026169EDC6012244B06C2C8C9E90A4574077 | | 2018-01-17 23:00:00 | 77.87.79.49 | 0.3.2.9 | Astra | 29374 | NULL | B4FEC3BD7FF7D269490A5DDCD5B96799BC46489A | | 2018-01-17 23:00:00 | 185.234.218.50 | 0.3.2.9 | Heracles | 31945 | NULL | 94D951D305DEFBBF2552BBDD9C919B09633DDA24 | | 2018-01-17 23:00:00 | 77.87.79.47 | 0.3.2.9 | Hypnos | 25363 | NULL | 537DD2E2D2F026FA9CD210E4B854584762DD9DB6 | | 2018-01-17 23:00:00 | 185.234.218.48 | 0.3.2.9 | Proteus | 28373 | NULL | 7F6DF29D2E0A82834E45AC210990B855802752B6 | | 2018-01-17 23:00:00 | 185.234.218.47 | 0.3.2.9 | Peitha | 28342 | NULL | 6716D11B3D43EA12EC883AA45A600EA277946A39 | | 2018-01-18 00:00:00 | 77.87.79.59 | 0.3.2.9 | Charon | 32734 | NULL | 7868248CD8FEE709AEAC0D13F1E30F79EC02D4C4 | | 2018-01-18 00:00:00 | 77.87.79.60 | 0.3.2.9 | Nemesis | 27364 | NULL | 54DC9A823CDFAB833590B4E4AE7EC386F38E2EB2 | | 2018-01-18 00:00:00 | 77.87.79.56 | 0.3.2.9 | Sirens | 35736 | NULL | AA545B49FE9AE5FC4B2295330E77EAD7BA228AEC | | 2018-01-18 00:00:00 | 77.87.79.52 | 0.3.2.9 | Erotes | 28374 | NULL | 36876E90176DBE3395A3EE8A2584FE7C3513C3C6 | | 2018-01-18 00:00:00 | 77.87.79.57 | 0.3.2.9 | Eleus | 28374 | NULL | F47044B9A265994F17EE02FBDA2046DB1A48E6F6 | | 2018-01-18 00:00:00 | 77.87.79.55 | 0.3.2.9 | Doris | 33625 | NULL | 9D30457253C5F43AAF38D6356C2B1E8CE4D4672D | | 2018-01-18 00:00:00 | 77.87.79.53 | 0.3.2.9 | Astra | 34948 | NULL | C486FA81814E1EA9E6B4585205816B6CBF96445F | | 2018-01-18 00:00:00 | 77.87.79.54 | 0.3.2.9 | Selene | 34837 | NULL | 6B8FDB5B3CFBB68DCC553922268EF0587BAB44B0 | | 2018-01-18 00:00:00 | 77.87.79.64 | 0.3.2.9 | Cybele | 39475 | NULL | CEB93C2E3D2876FF62BA0DC2F21808346E36270A | | 2018-01-18 00:00:00 | 77.87.79.51 | 0.3.2.9 | Elysium | 26374 | NULL | 34D18949F03875F6B1FCC4F6418CE10137BA7942 | | 2018-01-18 00:00:00 | 77.87.79.61 | 0.3.2.9 | Adriane | 39374 | NULL | BD37B322CE0EF1ACA6B7FDD0D66F54504C053BF5 | | 2018-01-18 00:00:00 | 77.87.79.58 | 0.3.2.9 | Theia | 37845 | NULL | 594252BFEE13625AC120F50F3015CB3C1DA55690 | | 2018-01-18 00:00:00 | 77.87.79.62 | 0.3.2.9 | Ino | 27364 | NULL | 02B2B98F879CFC70313BB20C4A88AE150E121DFD | | 2018-01-18 00:00:00 | 77.87.79.63 | 0.3.2.9 | Cotys | 34273 | NULL | 10E609E88024C1DB1E8D701602F254C0E8A7576E | | 2018-01-18 01:00:00 | 77.87.79.65 | 0.3.2.9 | Acheron | 35334 | NULL | 94FA1F71A8192C4337F734EC911FBA846045AB54 | | 2018-01-18 01:00:00 | 77.87.79.68 | 0.3.2.9 | Ourea | 27364 | NULL | A75AAE0B7C4A394F3E67DE31E2185EF37F439A5B | | 2018-01-18 01:00:00 | 77.87.79.70 | 0.3.2.9 | Cronus | 34567 | NULL | CAD689550FF6D332698E3687CD0DC40B2475CB38 | | 2018-01-18 01:00:00 | 77.87.79.67 | 0.3.2.9 | Dione | 35334 | NULL | E7C04B1DDE6DFA350A275E88D8612A5380020667 | | 2018-01-18 01:00:00 | 77.87.79.66 | 0.3.2.9 | Atlas | 36543 | NULL | CA318FEF4A3274CBF89416FD580C8B64D6A7589F | | 2018-01-18 01:00:00 | 77.87.79.48 | 0.3.2.9 | Nike | 28376 | NULL | A201E6FAC690713EB25AAE42A18D4C7E277C3B73 | | 2018-01-18 01:00:00 | 77.87.79.69 | 0.3.2.9 | Themis | 29374 | NULL | DCE904F85AC6E399455E9E41584B582CC71B65E8 | | 2018-01-26 01:00:00 | 185.234.218.225 | 0.3.2.9 | Gala | 9001 | NULL | D568DDFC9EB8990DB407ADB727DE07A51D835084 | | 2018-01-26 01:00:00 | 185.234.218.229 | 0.3.2.9 | Pluto | 9001 | NULL | 4A8B675A0B3C1D6454DBE7A2BD25BF039F596C8F | | 2018-01-26 01:00:00 | 185.234.218.222 | 0.3.2.9 | Chronos | 9001 | NULL | 5C6CA8731F14EFEFEF809533847FD560FB7A9CDA | | 2018-01-26 01:00:00 | 185.234.218.231 | 0.3.2.9 | Asclepius | 9001 | NULL | BBEE2C18269C474539F30016CE427FA5C8D6EB81 | | 2018-01-26 01:00:00 | 185.234.218.237 | 0.3.2.9 | Falacer | 9001 | NULL | 0267D63ECED91B436E697A6A09EEBC10EF1834B4 | | 2018-01-26 01:00:00 | 185.234.218.226 | 0.3.2.9 | Hephaestus | 9001 | NULL | 9BEBB4DA55DC8C29289FC8929D32B5AC36FEB3E1 | | 2018-01-26 01:00:00 | 185.234.218.224 | 0.3.2.9 | Eros | 9001 | NULL | B95EE27634948F7AB399A1E6E43595A9C07B8A75 | | 2018-01-26 01:00:00 | 185.234.218.221 | 0.3.2.9 | Asclepius | 9001 | NULL | A7B317D3E45882524B071FF26D02ED5CA3896A94 | | 2018-01-26 01:00:00 | 185.234.218.227 | 0.3.2.9 | Rea | 9001 | NULL | 93EA7712DADE2D903A63241C028CDC61828B6474 | | 2018-01-26 01:00:00 | 185.234.218.230 | 0.3.2.9 | Caelus | 9001 | NULL | 63829EB51C9E731A1B842CBB887B30F28141C636 | | 2018-01-26 01:00:00 | 185.234.218.232 | 0.3.2.9 | Diana | 9001 | NULL | 49D2098FFC4E19F387E6180EEAD8F59EF3F49E3C | | 2018-01-26 01:00:00 | 185.234.218.235 | 0.3.2.9 | Ops | 9001 | NULL | D6EA61F4D08F60278AAFC867EEF7BFFD62693689 | | 2018-01-26 01:00:00 | 185.234.218.234 | 0.3.2.9 | Mercury | 9001 | NULL | 407C9F6C0765C30734798999B3F61F9DA44BAACF | | 2018-01-26 01:00:00 | 185.234.218.238 | 0.3.2.9 | Fiora | 9001 | NULL | D9BF6019077878703EF6534B23D2136598E4D09E | | 2018-01-26 01:00:00 | 185.234.218.223 | 0.3.2.9 | Dionysus | 9001 | NULL | 3AEEC2D6F168CC59F46F62531BDF234F5066C30D | | 2018-01-26 01:00:00 | 185.234.218.228 | 0.3.2.9 | Somnus | 9001 | NULL | AE8F5B743EA1D772FD1017CF3DE070FE0CB0A702 | | 2018-01-26 01:00:00 | 185.234.218.236 | 0.3.2.9 | Vesta | 9001 | NULL | FC9AE0DD0B4A03ACA845A534A29B1442B2CB1654 | | 2018-01-26 02:00:00 | 185.234.218.248 | 0.3.2.9 | Pales | 9001 | NULL | 7779110F487C0F1C399321848D7879F16CFB7933 | | 2018-01-26 02:00:00 | 185.234.218.250 | 0.3.2.9 | Fides | 9001 | NULL | F92479656F51E2C0C29935F75AFE94921D77E8D5 | | 2018-01-26 02:00:00 | 185.234.218.242 | 0.3.2.9 | Diana | 9001 | NULL | 742C08BD99FC849BF641331C8A0E5B198CA058D0 | | 2018-01-26 02:00:00 | 185.234.218.244 | 0.3.2.9 | Sol | 9001 | NULL | 80F620ABA515A928CBE2D043B4253536F022EF16 | | 2018-01-26 02:00:00 | 185.234.218.249 | 0.3.2.9 | Vediovis | 9001 | NULL | FDDF7F36DDD254FDEAE5127F595C5DA0A571034A | | 2018-01-26 02:00:00 | 185.234.218.246 | 0.3.2.9 | Larunda | 9001 | NULL | 17E0D5E328FD6A06D3BD1A1CCB190682D038A7AA | | 2018-01-26 02:00:00 | 185.234.218.241 | 0.3.2.9 | Lucina | 9001 | NULL | 3EEA0DD81D8C4CE243E991538E47CA32EFF5CCC4 | | 2018-01-26 02:00:00 | 185.234.218.239 | 0.3.2.9 | Vulcan | 9001 | NULL | 8726F9C47A3703A1F0D79626CDCB0CF0DEB0FDBC | | 2018-01-26 02:00:00 | 185.234.218.240 | 0.3.2.9 | Lares | 9001 | NULL | 084AC15FD4FC3F1229A994D8E8F8ABE8FDD77E97 | | 2018-01-26 02:00:00 | 185.234.218.247 | 0.3.2.9 | Feronia | 9001 | NULL | 83F72AB24DE1EC398FF5828C9DB19A6357E573DC | | 2018-01-26 02:00:00 | 185.234.218.243 | 0.3.2.9 | Fons | 9001 | NULL | 5B06421F56248CED92212987F72D27BB4F0BB3C2 | | 2018-01-26 02:00:00 | 185.234.218.233 | 0.3.2.9 | Mars | 9001 | NULL | 25E7317FC422673C537221860B16DD1B3283B88C | | 2018-01-26 02:00:00 | 185.234.218.245 | 0.3.2.9 | Luna | 9001 | NULL | F4DA978E63B181C60C4FC206E9274D46810489ED | | 2018-01-30 23:00:00 | 185.234.218.33 | 0.3.2.9 | Hades | 25555 | NULL | A7F34E65DD14F72E237760216CCB65A99EB9BE59 | +---------------------+-----------------+-------------+------------+---------+---------+------------------------------------------+ -- https://mastodon.social/@nusenu twitter: @nusenu_

3 5

High number of simultaneous connections from a single host
by zless 01 Feb '18

01 Feb '18

Hello everyone, I was inspecting my node and just saw that it has a very high number of connections. It jumped from the normal 6000-7000 to more than 17000 simultaneous connections. Looking at the connections with `ss` I see some hosts with over 1000 connections while the majority is usually bellow 10. Here are some stats with the IP and the associated number of simultaneous connections: 212.32.226.237 : 1531 207.244.110.200 : 1520 162.210.192.70 : 1471 207.244.70.120 : 1455 198.7.59.194 : 1454 212.32.239.28 : 1450 5.79.103.239 : 1414 5.79.103.238 : 1401 51.15.162.120 : 1379 37.48.104.231 : 56 5.79.72.66 : 26 37.48.105.240 : 25 212.83.3.154 : 25 78.46.99.242 : 23 178.63.47.145 : 18 46.4.84.142 : 17 213.133.100.55 : 17 46.4.106.87 : 15 144.76.18.214 : 14 Is it normal for a single host to produce so many connections? How do you people handle such situations? Thanks

5 5

0.3.2.9 not reporting bandwidth in atlas
by Paul Templeton 31 Jan '18

31 Jan '18

Is it me or is there some issue. Since I've upgraded to version 0.3.2.9 there has been no update to the bandwidth graphs. family:867B95CACD64653FEEC4D2CEFC5C49B4620307A7 Paul 609662E824251C283164243846C035C803940378

3 2

MyFamily and ContactInfo fields are required for operators running multiple tor instances
by nusenu 31 Jan '18

31 Jan '18

Hi, I'd like to highlight that today the following two sentences requiring ContactInfo and MyFamily for operators running multiple relays got added to the tor manual page [1]: > ContactInfo **must** be set to a working address if you run more than one > relay or bridge. (Really, everybody running a relay or bridge should set > it.) > > > MyFamily **must** be set correctly if you run more than one relay or > bridge. (That is, every relay should list all the others as described > above.) The main motivation for this change have been suspicious tor relays that bad-relays@ ML decided to remove but had no way direct way to contact and so was forced to make hard decisions. With these clear statements bad-relays@ ML group can handle problematic cases better. regards, nusenu [1] https://gitweb.torproject.org/tor.git/tree/doc/tor.1.txt#n1717 -- https://mastodon.social/@nusenu twitter: @nusenu_

6 8

Tor uses up all available memory and eventually quits
by georgemaschke＠posteo.de 31 Jan '18

31 Jan '18

I am running a Tor (0.2.5.16 on Debian Linux) relay on a VPS with one gigabyte of RAM and no swap partition or swap file. The hosting company states that it doesn't support swap in order to prolong the life of its solid state drives. Tor gradually uses up more and more memory until its percentage usage is in the high 90s. Then Tor quits. This happens within about 48 hours of launch. What can I do to resolve this problem? Thanks! George W. Maschke https://georgemaschke.net

6 7

#2667 [Core Tor/Tor]: Exits should block reentry into the tor network
by nusenu 31 Jan '18

31 Jan '18

> Comment (by arma): > > I continue to think that teaching exit relays to avoid allowing exit > connections to known relays (IP:ORPort) is a good and useful step. > > We keep running across messy situations where letting somebody connect to > a relay from an exit relay's IP address turns into a security surprise. Does that mean that exits will no longer be able to run tor clients (ie. to run apt updates via tor)? -- https://mastodon.social/@nusenu twitter: @nusenu_

2 2