- tor-relays - lists.torproject.org

torservers.net impersonation: exit relay "Dontbleed9"
by nusenu 08 Jan '19

08 Jan '19

Hi, if you are the operator of the following relay, please stop impersonating torservers.net via ContactInfo and DirFrontPage or risk getting removed from the tor network. +----------------------------------------------------------------------------+------------------+----------------+----------------------------------------+-------------+ | contact | nickname | IP | as_name | efamMembers | +----------------------------------------------------------------------------+------------------+----------------+----------------------------------------+-------------+ | https://www.torservers.net/donate.html <support .AT. torservers .DOT. net> | Dontbleed9 | 213.61.215.54 | COLT Technology Services Group Limited | 1 | +----------------------------------------------------------------------------+------------------+----------------+----------------------------------------+-------------+ https://metrics.torproject.org/rs.html#details/C332CB1924619CF9E74898154232… -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Re: [tor-relays] [OrNetRadar] NickPrefix: "tOr" (14)
by nusenu 07 Jan '19

07 Jan '19

please set a proper contactInfo and MyFamily when running so many relays to avoid getting removed from the network ornetradar(a)riseup.net: > 2019-01-06 > > | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | > |------+-------+------------+------------+-----------+-----------------+---------------------+------+-------+--------+-------+-------------------------------------+---------------+------------------------------------------| > | 1 | 0 | 13:47:33 | tOr | 0.3.4.9 | 176.9.73.145 | Hetzner Online GmbH | de | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 27A01740A87B5861DB4008BB81F8CFA518FDA554 | > | 1 | 0 | 15:15:06 | tOr | 0.3.4.9 | 51.15.47.139 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 62E436E252D3657D838AA2D3769530DEB0651BD5 | > | 1 | 0 | 15:18:09 | tOr | 0.3.4.9 | 51.15.179.39 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 430708DD45146CD58C18E34F6EF8E249AF5E2795 | > | 1 | 0 | 15:21:51 | tOr | 0.3.4.9 | 51.15.57.43 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 25E6490C85CCD7B399F816F855BEB1610D8EB56B | > | 0 | 0 | 15:22:12 | tOr | 0.3.4.9 | 51.15.55.204 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 97C183B6ED91CF734F18E3AE08A19D6886F6CA6F | > | 1 | 0 | 15:22:38 | tOr | 0.3.4.9 | 51.15.84.167 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | B9B11438B56875029AD58FC2806D5B6F6546B4F1 | > | 1 | 0 | 15:27:42 | tOr | 0.3.4.9 | 51.15.141.150 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 758022E3952DBA2E74EAA6A7F71FBC7671F50964 | > | 1 | 0 | 15:27:44 | tOr | 0.3.4.9 | 212.47.231.164 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 5935A516784B11A425B6CF82C2740EE53A20C8E7 | > | 1 | 0 | 15:33:08 | tOr | 0.3.4.9 | 51.15.51.3 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 89DDCCBAEBDC2B8C94DA657E8ED6C2FD9A810081 | > | 1 | 0 | 15:35:48 | tOr | 0.2.9.14 | 51.15.92.208 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 0CA7D6634359FC7691AC9159996AD0863D0248FF | > | 1 | 0 | 15:36:54 | tOr | 0.3.4.9 | 51.15.52.4 | Online S.a.s. | nl | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | A9A834754E43C80DADCC38E4CF81362F357CABE7 | > | 1 | 0 | 15:37:44 | tOr | 0.3.4.9 | 51.15.84.8 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | B8F0501E3AB911C2EA955EDC30D29B938F5B6B17 | > | 1 | 0 | 15:40:09 | tOr | 0.2.9.14 | 51.15.137.138 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 3FF883A45AEA15721FFFB970EBB7B88719C70E9E | > | 1 | 0 | 15:41:59 | tOr | 0.3.4.9 | 163.172.186.236 | Online S.a.s. | fr | 443 | 0 | Linux | 0xFFFFFFFF Random Person <nobody AT | 1 | 301F7608C5A6213F381BDBD7010EBB81128E0DAA | > > https://nusenu.github.io/OrNetRadar/2019/01/06/a4 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

tor 0.3.3.x reaches end-of-life on 2019-02-22
by nusenu 06 Jan '19

06 Jan '19

In less than 2 months from now, tor 0.3.3.x will reach its end of life date (2019-02-22). As of today there are still over 640 relays (>10% CW fraction) running that version. If you still run that or another end-of-life version of tor please update to help prevent known issues. -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

having just 1 exit port - helpful?
by Toralf Förster 06 Jan '19

06 Jan '19

If just 1 port would be opened at an relay, eg. 6697, would this help the Tor network or would only spammers and DDoS use that port? -- Toralf PGP C4EACDDE 0076E94E

4 3

Onion v2 HSDir Support (ref: v3 prop224) [was: fishy fingerprint patterns]
by grarpamp 05 Jan '19

05 Jan '19

> relays have a rather distinct signup and fingerprint pattern > usually seen for onion attacks. > ... > a) If you are an .onion operator I'd like to encourage you to switch to onion > services version 3 > ... > so we can start > ... > b) dropping onion version 2 services eventually. These are two separate things not necessarily tied together, thus split for clarity as above. The former a) is up to the onion operator based on their needs. If they have no need for v2, or need v3, they can or should switch to v3, indeed. The latter b) is a feature that some users and operators in and for onionspace explicitly choose and depend on to support common apps, and thus would definitely not like to see yanked out from under them. Better instead to advertise and update the default onion semantics for [new] users to v3, and continue support and backport doable features to v2 until time below... Node operators (tor-relays) would continue offering v2 HSDir support module until such time as the reasons for choosing v2 by those above are supported in v3 or vN. See the threads on this subject on tor-talk, tor-onions, and tickets for more. [CC for inclusion, move there if not relay specific]

4 6

hello aurum1704 tor relay operator
by nusenu 04 Jan '19

04 Jan '19

Hi aurum1704, thanks for adding so many relays. If I may ask: Are you planing to run them long term? Just be aware of the traffic pricing at DigitalOcean: https://www.digitalocean.com/community/tutorials/digitalocean-bandwidth-bil… | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | |------+-------+------------+------------+-----------+-----------------+-------------------+------+-------+--------+-------+-------------------------------------+---------------+------------------------------------------| | 1 | 0 | 21:26:48 | cobalt0 | 0.3.4.9 | 157.230.136.180 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com | 14 | 4EF954752C47906CF26AFA9FDD2E82FE9B2CF040 | | 1 | 0 | 21:30:40 | cobalt00 | 0.3.4.9 | 157.230.136.180 | None | us | 9101 | 9032 | Linux | aurum1704(at)gmail(dot)com | 14 | 30BE64D2C5AAFD3F7BACFDE1E1CC8D540CE4D905 | | 1 | 0 | 06:42:48 | cobalt10 | 0.3.4.9 | 157.230.140.92 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | 31B9D3F99A32543D1FE1DC2E2B2A2B21C0DFAB97 | | 1 | 0 | 06:47:53 | cobalt100 | 0.3.4.9 | 157.230.140.92 | None | us | 9101 | 9032 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | 225821522D8652DCECA757D59779587FE23B245F | | 1 | 0 | 02:36:57 | cobalt11 | 0.3.4.9 | 157.230.143.151 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | 68C9268B76D27E199C7683771F3C83BE00FE3192 | | 1 | 0 | 02:54:17 | cobalt12 | 0.3.4.9 | 68.183.173.106 | DigitalOcean, LLC | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | AFA580D001379B6CF80FA38E3A0CB2A8B7FC5046 | | 1 | 0 | 02:56:16 | cobalt13 | 0.3.4.9 | 157.230.128.91 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | 09058A1C003E5F9B7735D028D378C42DCF92CA46 | | 1 | 0 | 21:43:50 | cobalt14 | 0.3.4.9 | 157.230.132.69 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | 94BF5FB37B5F7FEE124273A8751D416AE6F61380 | | 1 | 0 | 05:10:04 | cobalt15 | 0.3.4.9 | 157.230.132.150 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | E1442DB84252242848E53E2599E1DBE7DF80278F | | 1 | 0 | 05:56:42 | cobalt16 | 0.3.4.9 | 157.230.132.151 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com | 14 | 70FE4B7B908875359F34F22F7FC15C4F6CD7B27D | | 1 | 0 | 06:26:16 | cobalt7 | 0.3.4.9 | 157.230.132.153 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | 640B889E6FE5F8AFC5A3A8553A9BE3377E43B4C5 | | 1 | 0 | 06:27:40 | cobalt8 | 0.3.4.9 | 157.230.132.175 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | 9AE92FD739FCF3547C1ECD3C4EF71D434D5834E2 | | 1 | 0 | 06:31:00 | cobalt9 | 0.3.4.9 | 157.230.140.94 | None | us | 9001 | 9030 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | C3907FD65A2C0B389AB9CDF38EB6CA065064C134 | | 1 | 0 | 06:50:07 | cobalt99 | 0.3.4.9 | 157.230.140.94 | None | us | 9101 | 9032 | Linux | aurum1704(at)gmail(dot)com [tor-rel | 14 | A8AC085EAB39191F2304D7C86B5BDCB1E85A390C | -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Re: [tor-relays] Metrics show Relay donw
by Darek Kramin 04 Jan '19

04 Jan '19

Looks problem is solved. Online now On Tue, Dec 25, 2018, 21:13 Darek Kramin <cptkramin(a)gmail.com wrote: > hi, > > I did started 2 days ago tor relay. when I set daily accounting was ok and > now with weekly set of GB relay is listed down. It is a glitch or my > misconfiguration. > Relay is named dasBoot at IP 46.175.238.8 > > brgds > Darek > > -- > > Cpt D.Kramin > +48 505 135145 >

2 1

My Fallback Directory Mirror is going down
by Viktor Nikolov 04 Jan '19

04 Jan '19

Hi! My Fallback Directory Mirror B6904ADD4C0D10CDA7179E051962350A69A63243 at 81.2.209.10 is going down permanently because my provider decommissioned the data center where I had my HW. :-( I will likely host my HW at a new provider soon, but at a new IP address. Viktor

2 1

openinternet.io: Tor Relay Configuration: 'MyFamily' missing and public munin graphs
by nusenu 03 Jan '19

03 Jan '19

Hi sysop (openinternet.io), thanks for helping the tor network by running relays. please do not forget to set your "MyFamily" configuration parameter on all your relays, so Tor clients are not at risk of using your relays in multiple positions in a single circuit. https://nusenu.github.io/OrNetStats/endtoend-correlation-groups Some more background: https://hackernoon.com/some-tor-relays-you-might-want-to-avoid-5901597ad821 Let us know if you need any help with this. Also note that it is very discouraged to publish munin network traffic graphs of tor relays (5min granularity) please remove them. kind regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Hyperlink in ContactInfo
by Ilka Schulz 03 Jan '19

03 Jan '19

Hi, I wrote a little PHP-based contact page and put the link to the /ContactInfo/ of my relay's /torrc/. I added some HTML tags (/<a href=...> ... </a>/) to let Tor Metrics show the link as such; but, of course, the string is sanitized properly, so the /Contact/ field on Tor Metrics shows the literal HTML tags. Is there any chance to show the hyperlink on Tor Metrics, so that visitors can directly click on it? The same would be interesting for clear text email addresses. Regards, Ilka

2 1

Compatibility issue with OpenSSL 1.1.1a
by Nick Mathewson 02 Jan '19

02 Jan '19

Hi, folks! You should know that there is a compatibility issue between Tor and OpenSSL 1.1.1a, when TLS 1.3 is in use. Only OpenSSL 1.1.1a is affected; other OpenSSL versions are not. The effect here is that Tor relays using this version of OpenSSL will not be able to negotiate TLS 1.3 connections with one another. This is caused by a regression in OpenSSL 1.1.1a's implementation of tls13_hkdf_expand() function. For more information, see https://trac.torproject.org/projects/tor/ticket/28616 We're looking into possible mitigations. best wishes, -- Nick

5 7

300mbps FreeBSD Tor relay on HPE MicroServer Gen10 (AMD X3421)
by Neel Chauhan 02 Jan '19

02 Jan '19

Hi tor-relays@, I have a Tor middle relay NeelTorRelay2 hosted on a 50 megabit symmetrical Verizon FiOS (FTTH/GPON) connection. The server used is a HPE MicroServer Gen10 (AMD X3421 quad-core version, 8GB DDR4 RAM). This relay can be seen here: https://metrics.torproject.org/rs.html#details/D5B8C38539C509380767D4DE20DE… My relay runs FreeBSD 11.2 and Tor runs in a "jail". I am using AESNI and Tor is configured to use OpenSSL cryptodev. Here's the situation: I will be moving apartments in a few days, and Verizon is upgrading my broadband speed to 300 megabits symmetrical. I plan to use this extra bandwidth for Tor. Right now, I set my RelayBandwidthRate to my line speed (yes really!), and plan to increase this setting according to my new speed. I know that Tor is not optimized for multicore CPUs, and that's the reason why I am posting here. My question is that can Tor work on the HPE MicroServer Gen10 with the AMD X3421 (or one with a similar computer of any brand with a similar performance CPU, whether desktop or server, Intel or AMD) with all 300 megabits to a single instance or would I need two instances (each at 150 megabits each)? Looking at my top usage, I average at about 20-30% CPU usage on my 50 megabit relay. Also keep in mind that: * I am using my own router instead of Verizon's and I plan to keep doing so * I want to keep using FreeBSD on my server and do not want to run Linux * I would prefer to have a single instance, but can use multiple if I have to * When I move, I will upgrade my server to FreeBSD 12.0 * My server supports hardware accelerated AES and SHA. I am using this on FreeBSD with the aesni kernel module and Tor with "HardwareAccel 1" and "AccelName cryptodev" Thank You, Neel Chauhan === https://www.neelc.org/

7 9

Re: [tor-relays] 35C3 Tor Relay Operators Meetup
by 35C3 35C3 01 Jan '19

01 Jan '19

> Hi, I have only my smartphone at the moment. It would be great if you swap the rooms. Thank you added a second slot on the first day/night: 2018-12-28 00:30 Room M3 I did NOT replace the first slot in the smaller room (2018-12-28 16:30) because the second slot is a bit late to avoid collisions with ie "It Always Feels Like the Five Eyes Are Watching You" - Kurt Opsahl https://fahrplan.events.ccc.de/congress/2018/Fahrplan/events/9951.html https://events.ccc.de/congress/2018/wiki/index.php/Session:Tor_relay_operat…

3 3

Security issue
by dns1983＠riseup.net 29 Dec '18

29 Dec '18

Hello, Do I have to worry about those many warns on my log file? [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending) I found some old posts on this warn, but I don't understand if it is a security issue and what I have to do to fix this. Someone could tell me if there is something that I can do to fix this and improve security of my Debian -derived machine? Thanks Gigi

2 2

New exit relay help
by dns1983＠riseup.net 28 Dec '18

28 Dec '18

Hi, I need to install some additional software, to make the "DirFrontPage" work? I loaded an html file on my tor directory, uncommented the diretive "DirFrontPage /path/html-file", but It doesn't works and I don't see anything related to it in the log notice file. What I am doin wrong? I don't know how to solve the problem, can you help me please? best regards Gigi

5 6

Dec 2018: 24 new relays with fishy fingerprint patterns in Aruba and "INTERNET CZ" ASN
by nusenu 26 Dec '18

26 Dec '18

these 24 relays have a rather distinct signup and fingerprint pattern usually seen for onion attacks: +------------------------------------------+---------------------+--------------+--------------------+-------+------+----------------+---------+-------------+---------------------------------+ | fingerprint | first_seen | nickname | as_name | hsdir | exit | IP | or_port | tor_version | contact | +------------------------------------------+---------------------+--------------+--------------------+-------+------+----------------+---------+-------------+---------------------------------+ | 38D26817234F6B271E6A6DED306188BC09D1AA41 | 2018-12-19 13:00:00 | Escalibur | Aruba SAS | 1 | 0 | 185.8.50.23 | 9001 | 0.3.4.9 | NULL | | 38D2A1B04D004A61D2A9599EB5EC06FE42C463F7 | 2018-12-20 10:00:00 | delecat3d | Aruba S.p.A. | 0 | 0 | 195.231.66.172 | 9001 | 0.3.4.9 | NULL | | 38D2B873966A1C392E427CD1417BC7BB0E84B058 | 2018-12-17 08:00:00 | HGSTdisks | Aruba SAS | 1 | 0 | 94.177.226.229 | 9001 | 0.3.4.9 | coreproccores(a)gmail.com | | 510FEC23762319FEEAB3B65AF4592BE21515A7C4 | 2018-12-17 10:00:00 | tM666 | ArubaCloud Limited | 1 | 0 | 185.43.209.232 | 9001 | 0.3.4.9 | NULL | | 510FEC475B2B286A1886A22B333A1CCDEE8F0117 | 2018-12-16 15:00:00 | yeeboyd | INTERNET CZ, a.s. | 1 | 0 | 185.33.144.210 | 9001 | 0.3.4.9 | NULL | | 510FED6000FFEE2B451782DB0E82C2CCA8DF2332 | 2018-12-18 11:00:00 | takeAsit | Aruba SAS | 1 | 0 | 94.177.226.7 | 9001 | 0.3.4.9 | NULL | | 6688CD00E32D45DDC25FE0F4AE31EEB460DC02EF | 2018-12-20 12:00:00 | DoeRelay | Aruba SAS | 1 | 0 | 185.8.50.62 | 9001 | 0.3.4.9 | mrmrsdoehere gmaiil _ dot COM | | 6688E3150DC2898DDBD98D8AB70C078ECA468945 | 2018-12-19 10:00:00 | reltor | Aruba S.p.A. | 1 | 0 | 195.231.66.103 | 9001 | 0.3.4.9 | tripinonuyou gmail com | | 6688F26C215F92A0EF8B0C94B03FA160E22C4E75 | 2018-12-21 11:00:00 | Unnamed | Aruba S.p.A. | 0 | 0 | 80.211.253.155 | 9001 | 0.3.4.9 | NULL | | 8F29FDC9C2F85E5E9CC3F56E81B2A3D9CCB031FB | 2018-12-16 15:00:00 | SedS0K | Aruba S.p.A. | 1 | 0 | 195.231.66.240 | 9001 | 0.3.4.9 | seds0kkkk(at)gmail(dot)com | | 8F2A173B990CAE8CB61BEFDC61F9B8C047977667 | 2018-12-18 16:00:00 | FreeW | Aruba SAS | 1 | 0 | 185.8.50.73 | 9001 | 0.3.4.9 | NULL | | 8F2AE6EBB163B9B0BC64C0EE689946CE7A36B3F1 | 2018-12-17 18:00:00 | nobobyno | Aruba S.p.A. | 1 | 0 | 80.211.253.176 | 9001 | 0.3.4.9 | smpuffy_AT_mail.pl | | 9E9DA7C5060BEAB9860F120CCA5646ECBC92382B | 2018-12-19 09:00:00 | NextDoorBar | Aruba SAS | 1 | 0 | 94.177.226.250 | 9001 | 0.3.4.9 | NULL | | 9E9DAED63FE72C571753C03B2DF7C956AF02897A | 2018-12-18 12:00:00 | Unnamed | INTERNET CZ, a.s. | 1 | 0 | 185.33.144.110 | 9001 | 0.3.4.9 | NULL | | 9E9DE2E42485FBE95DAC35138EFE372A24D64D21 | 2018-12-17 22:00:00 | LiteMoka | Aruba S.p.A. | 1 | 0 | 195.231.66.108 | 9001 | 0.3.4.9 | juseppo2199()at()gmail_com | | A380D254B25878C74087C5D74C692D0241CBD6F0 | 2018-12-20 22:00:00 | AnonHappyBox | Aruba SAS | 1 | 0 | 94.177.226.230 | 9001 | 0.3.4.9 | anonanon55a_@_secmail_dot_net | | A380D347759DA5CBDC5BCBC4B51318A0C8567B53 | 2018-12-21 15:00:00 | Pendium | ArubaCloud Limited | 0 | 0 | 185.43.209.100 | 9001 | 0.3.4.9 | strangzapsl AT gmail DOT com | | A380E80F9C6405332C8113C02B566120B8099B06 | 2018-12-19 18:00:00 | volt220 | INTERNET CZ, a.s. | 1 | 0 | 185.33.144.204 | 9001 | 0.3.4.9 | spensr555oh _AT_ gmail _ dot_cm | | BE27A8DA5463AE0B32A4BAEC4214C0CD00F70DC3 | 2018-12-18 14:00:00 | Minicana | Aruba S.p.A. | 1 | 0 | 80.211.253.249 | 9001 | 0.3.4.9 | __Valentino404()gmail_com | | BE27E56E8D6B9D3B84120804CA1C3564DA70827D | 2018-12-19 22:00:00 | Bestrddd | ArubaCloud Limited | 1 | 0 | 185.43.209.236 | 9001 | 0.3.4.9 | no please | | BE27F22046D89A1EAD690C9C291F7AE85B9025DA | 2018-12-20 15:00:00 | Unnamed | INTERNET CZ, a.s. | 1 | 0 | 185.33.144.196 | 9001 | 0.3.4.9 | NULL | | E7D8A8B5FA3CA3B668F12B5D46AB0DE94B9A9C1D | 2018-12-16 22:00:00 | Unnamed | Aruba SAS | 1 | 0 | 185.8.50.188 | 9001 | 0.3.4.9 | NULL | | E7D8B9141E5EF11526D34DC231DD32297BC3F904 | 2018-12-19 16:00:00 | FlashGordon | Aruba S.p.A. | 1 | 0 | 80.211.253.88 | 9001 | 0.3.4.9 | sinsincytyATprotrityDOTnet | | E7D8F1E61D068E7681EE81D6AFC7862FEB29D261 | 2018-12-18 20:00:00 | Andersen | ArubaCloud Limited | 1 | 0 | 185.43.209.114 | 9001 | 0.3.4.9 | NULL | +------------------------------------------+---------------------+--------------+--------------------+-------+------+----------------+---------+-------------+---------------------------------+ If you are an .onion operator I'd like to encourage you to switch to onion services version 3 so we can start dropping onion version 2 services eventually. -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Metrics show Relay down
by Darek Kramin 25 Dec '18

25 Dec '18

hi, I did started 2 days ago tor relay. when I set daily accounting was ok and now with weekly set of GB relay is listed down. It is a glitch or my misconfiguration. Relay is named dasBoot at IP 46.175.238.8 brgds darek -- Cpt D.Kramin +48 505 135145

1 0

35C3 Tor Relay Operators Meetup
by 35C3 35C3 23 Dec '18

23 Dec '18

Hi nicoo, since you organized the tor relay operators meetups during the last few years at the CCC I was wondering if you will continue with that this year as well? If so, it would be great if we could get - a slightly bigger room than we had last year - a room with a beamer (Roger will not be there this year as he previously mentioned) The 35C3 wiki is not available yet. thank you!

2 2

Extreme Exit Policy
by John Ricketts 21 Dec '18

21 Dec '18

All, I am considering only allowing ports 53, 80, and 443 only. Discussion? John Ricketts Quintex Alliance Consulting

8 13

Re: [tor-relays] consensus-health.html and fallback dirs
by starlight.2018q2＠binnacle.cx 21 Dec '18

21 Dec '18

Ran the script: output is attached to this message for anyone interested. Live-network test results will vary by time and by the location of tester. Attached run was made over Tor itself using 'torsocks'. I was bit by having disabled the unencrypted DIR port for one day recently as an experiment. >Felix zwiebel at quantentunnel.de >Sun Dec 16 10:03:33 UTC 2018 > >>> I wonder how we can come from 116 running fallbacks to 155 within >>> one week (without a new release) > >Am 16.12.2018 um 08:01 schrieb starlight.2018q2 at binnacle.cx: >> The cause is >> >> https://gitweb.torproject.org/tor.git/commit/?id=78e177d622f5f3b24023d04458… > >Ah, great! This makes sense. It's a transient to the list update. > > > >> https://trac.torproject.org/projects/tor/ticket/24803 > >The upcoming one seems to be: >https://trac.torproject.org/projects/tor/ticket/28795 > >-- >Cheers, Felix >

2 1

Advice for new exit relay
by dns1983＠riseup.net 20 Dec '18

20 Dec '18

Hi, excuse my bad english. I would run an exit relay on a virtual server. For now i run just a non exit relay on my own mini server. I don't like too much do not have full control on the server, but, for me, it is the only way to run an exit relay. How do I know which service allow me to customize WHOIS records, so I can put my email address on report abuse section? Could you suggest me some providers that offer unlimited monthly data too? Regards Gigi

2 4

How to use a bridge configured with "ORport auto" within Tails?
by Toralf Förster 20 Dec '18

20 Dec '18

The Tails installer asked me for the bridge line (a bridge maintained by myself), but didn't accepted the ":auto" behind the ip address. I do wonder how to proceed? -- Toralf PGP C4EACDDE 0076E94E

2 3

Why are my relays flagged?
by Langrehr, Jan Christian 20 Dec '18

20 Dec '18

Hello everyone, I'm wondering why both of my Tor relays are flagged for running an unstable or outdated version or Tor. I'm running my relays on Ubuntu 18.04 and I get Tor from the deb https://deb.torproject.org/torproject.org bionic main repository. Both of my relays run Tor version 0.3.4.8. My relays are https://metrics.torproject.org/rs.html#details/9EDA50493B537837E72D83090BE4… and https://metrics.torproject.org/rs.html#details/8E57A56487EEA341965B77AE132E… I'm looking forward for an anwser. Thank you all very much

3 2

Re: [tor-relays] consensus-health.html and fallback dirs
by starlight.2018q2＠binnacle.cx 16 Dec '18

16 Dec '18

The cause is https://gitweb.torproject.org/tor.git/commit/?id=78e177d622f5f3b24023d04458… https://trac.torproject.org/projects/tor/ticket/24803 Would be appreciated if the Tor project published outputs of UpdateFallbackDirs.py job runs used when rebuilding the list. Thus operators who have expended effort to keep their relays eligible will know why when dropped. >Felix zwiebel at quantentunnel.de >Sat Dec 15 23:59:03 UTC 2018 > >Hi everybody > >Reading [1] shows the following statistics about the fallback dirs: > >Dec 5: >Running 116 >Not Running 0 >Missing 34 > >Dec 13: >Running 155 >Not Running 0 >Missing 2 > >Today (Dec 16) shows: >Running 151 >Not Running 0 >Missing 6 > >I wonder how we can come from 116 running fallbacks to 155 within one >week (without a new release): > > >Then I checked for some fallbacks and found: > >The relay with the fp F9246DEF2B653807236DA134F2AEAB103D58ABFE was a >fallback acc. fallback_dirs.inc until around 3.2.8rc, then it changed >ip. It is still in 2.9.x lts but with the old ip, recommended but >actually useless. > >Since around Dec 13 it is listed again [1] where it wasn't through 2018. > >The same with 8FA37B93397015B2BC5A525C908485260BE9F422. > >Are the two relays newly counted as running in [1], where they are >useless because of the changed ips? The new ips aren't in any >fallback_dirs.inc's and [2] shows no fallback flag. >Would thereby [1] look better than it is? > > >[1] https://consensus-health.torproject.org/consensus-health.html >[2] https://metrics.torproject.org/rs.html#details/F9246DEF2B653807236DA134F2AE… > >-- >Cheers, Felix

2 1

Re: [tor-relays] [OrNetRadar] NickPrefix: "AYAYA" (9)
by nusenu 16 Dec '18

16 Dec '18

Hello "AYAYA" relays > 2018-12-15 > > | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | > |------+-------+------------+------------+-----------+---------------+---------------+------+-------+--------+-------+-----------+---------------+------------------------------------------| > | 1 | 0 | 11:23:45 | AYAYA43 | 0.2.9.14 | 51.15.88.206 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | D0BADF4222F4CE7DF6D91A772E391E29FDEA82FB | > | 1 | 0 | 11:24:20 | AYAYA46 | 0.2.9.14 | 51.15.113.238 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | A4D98EE5916240F1AC6348174C40848B4C7F7C0C | > | 1 | 0 | 11:23:45 | AYAYA52 | 0.2.9.14 | 51.15.71.128 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | 25C3DEAE9AA786559DBB072D0470D1A6FC408846 | > | 1 | 0 | 11:23:45 | AYAYA6 | 0.2.9.14 | 51.15.78.215 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | BED1681C0DDEF5DE7B8A65E2603D262FE3B1DB59 | > | 1 | 0 | 11:23:45 | AYAYA64 | 0.2.9.14 | 51.15.43.15 | Online S.a.s. | nl | 9001 | 9030 | Linux | None | 1 | F6F70FEB215929701E027B9A436A38347D377367 | > | 1 | 0 | 11:23:44 | AYAYA70 | 0.2.9.14 | 51.15.85.153 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | 64FDE6159C134C606A24ADBA7A3E9A66F3810465 | > | 1 | 0 | 11:23:45 | AYAYA8 | 0.2.9.14 | 51.15.35.170 | Online S.a.s. | nl | 9001 | 9030 | Linux | None | 1 | B9A1E0C135464554ACCE036A9B5AB6F9469A9703 | > | 1 | 0 | 11:23:45 | AYAYA90 | 0.2.9.14 | 51.15.83.14 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | CCD5C2E7FABACCF8CD84BCDC8E689584881545B8 | > | 1 | 0 | 11:23:46 | AYAYA98 | 0.2.9.14 | 51.15.116.94 | Online S.a.s. | fr | 9001 | 9030 | Linux | None | 1 | 706A24208BE86E84B850ECAF42EC293CECE1ECC1 | > > https://nusenu.github.io/OrNetRadar/2018/12/15/a1 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0