- tor-relays - lists.torproject.org

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 04 Jan '19

04 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