- tor-relays - lists.torproject.org

Leaky-pipe circuit topology
by marziyeh latifi 18 Jan '19

18 Jan '19

Hello, May you explain me what is Leak-pipe circuit topology? I studied Leaky-pipe circuit topology in "tor- design" document but I don't understand how it work! thanks best regards marzieh

2 1

Bandwidth limiting at relay or network?
by Isaac Grover, Aileron I.T. 18 Jan '19

18 Jan '19

Good evening fellow relay operators, I haven't ever taken the time to configure bandwidth limits in torrc, always preferring to manage it at the firewall as we have other bandwidth limits set there as well. However, I'm curious - what do other relay operators prefer? Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. - " Because #ProactiveIsBetter " O: 715-377-0440<tel:715-425-0440>, F:715-690-1029<tel:715-690-1029>, W: www.aileronit.com<http://www.aileronit.com/> LinkedIn: https://www.linkedin.com/in/IsaacGrover/ YouTube: https://www.youtube.com/channel/UCqrwZNFKdR-guKtuQzFPObQ

3 2

Consensus weight drops continuously 28h after getting guard flag
by Ilka Schulz 16 Jan '19

16 Jan '19

Hi, approx. 28 hours after getting the guard flag, my relay <https://metrics.torproject.org/rs.html#details/A99B0D9E5FD5BC3C8F2D006EC91F…>'s consensus weight hit a peak and has declined rather rapidly since then (again 28 hours ago). Did I do something wrong? Is it because I restarted the relay 52 hours ago? Is there actually any detailed documentation on how consensus weight is calculated? Also, my bandwidth (as well as my cpu, etc.) is only used to a fraction of its capacity, even though my relay is three weeks old now. The /RelayBandwidthRate/ option does not limit here... Regards, Ilka

6 11

Torproject onion-repo down (sdscoq7snqtznauu.onion/torproject.org) ?
by petrarca＠protonmail.ch 16 Jan '19

16 Jan '19

Is it just me having issues - today, I couldn't reach the onion-repository of torproject.org at sdscoq7snqtznauu.onion anymore. It was working until very recently though. Everything else is working fine (internet, other onion services, etc.) and I didn't change anything really (just an upgrade to tor 0.3.5.7)...

2 1

Server sale on online.net
by niftybunny 16 Jan '19

16 Jan '19

Tor friendly (even Exist), no bw costs, you should check it out or not. I do not get anything from this. Cheers, markus

1 0

Fallback Directory Mirror
by [REDACTED] 15 Jan '19

15 Jan '19

Hi, i run 17 Entrys and one bridge at the moment. I dont plan to change the IP adresses or the ports and most of them are already paid for nearly two years and i dont see a reason to switch them off after that time so if more fallback directory mirrors are needed then feel free to add them: D379A1CB8285748FFF64AE94296CA89878F25B22 9288B75B5FF8861EFF32A6BE8825CC38A4F9F8C2 EE4AF632058F0734C1426B1AD689F47445CA2056 B57A87009FA838471FB2227DDE68165AB2A2FCC4 465D17C6FC297E3857B5C6F152006A1E212944EA 7AAF5597B18D82CC90CA95FB7976A1CEA4A32E06 39F91959416763AFD34DBEEC05474411B964B2DC 4DC4E6187F1193F2717A5E3DF5ACEBD6B162D5CC 57C6DF5B93E54EB9C8DB90029D9E9A1111BD34D2 3B07C500AC17E7B5A1EE616613E104A094AB87F3 8F6197E5508338B3E3A6BFF59F9EC8F21E1375FB 79E683340B80676DCEB029E48FBD36BC66EBDA1E A86EC24F5B8B964F67AC7C27CE92842025983274 A9DB853547A6459AB5190E62BF2F7B8F068FEB0A Some of them are still pretty new but i am sure they will get older:)

1 0

community team highlights: Relay Advocacy
by nusenu 15 Jan '19

15 Jan '19

FYI -------- Forwarded Message -------- Subject: [tor-project] community team highlights -- November and December Date: Wed, 09 Jan 2019 18:15:00 +0000 From: Alison Macrina <alison(a)torproject.org> Reply-To: tor-project(a)lists.torproject.org To: tor-project(a)lists.torproject.org Relay Advocacy ================================================================== Colin resumed running once a month IRC relay operator meetings. He also started planning the FOSDEM relay operator meet-up. Steph and Colin are working on updating the relay flyers. Colin continues to work on communicating with OVH regarding relays without contactinfo added to the network. Finally, Colin has been working with Bill from EFF on a Tor relay challenge.

9 10

New Fallbacks from December 2018
by teor 15 Jan '19

15 Jan '19

Dear Relay Operators, Thanks to everyone who opted-in their relays as fallback directory mirrors. We rebuilt the list of fallbacks in December 2018. [0] The new list was released in Tor 0.3.5.6-rc, and it was backported to all supported Tor releases. [1] The FallbackDir flags on Consensus Health [2] have been updated. The flags on Relay Search [3] might take a few days to update. Don't worry if your relay missed out this time. It's still helping Tor users. And we will rebuild the fallback list again in 6-12 months time. We are tracking fallback changes in this ticket [4]. To opt-in your relays, add a comment to the ticket [4], or reply to this thread. If you have multiple relays, you can opt-in as many as you like. (We picked up to 7 per operator this time, and we may pick more next time.) T [0]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc https://trac.torproject.org/projects/tor/ticket/24801 [1]: 0.2.9, 0.3.3, 0.3.4, 0.3.5, and 0.4.0. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… [2]: https://consensus-health.torproject.org/graphs.html [3]: For example, this relay is a new fallback: https://metrics.torproject.org/rs.html#details/0C039F35C2E40DCB71CD8A07E97C… [4]: https://trac.torproject.org/projects/tor/ticket/28794 T -- teor ----------------------------------------------------------------------

1 0

Adding Obfuscation Types To Windows Bridge
by Keifer Bly 15 Jan '19

15 Jan '19

Hello, So I am running an obfuscated bridge using the tor expert bundle and the compiled version of obfs4. There are some questions I wanted to ask. So, I am looking to add pluggable transports to my bridge, which currently only supports obfs4. I do not have access to any services that offer domain fronting, or third party servers, so I cannot run meek as a result. However, is it possible to add more than one pluggable transport, such as Format-Transferring Encryption or ScrambleSuit and also have obfs4? Are there compiled versions of these pluggable transports for windows? I also wanted to ask, do I need to update obfs4.exe when I update tor.exe? Another question, so I have in my torrc file, Contact Info: followed by an obfuscated version of this email address. However, as seen on my bridge listing at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032… The contact into does not appear. I do not want to give this email address out publicly, but I do want to register with bridge authorities so they can contact me if something is wrong with my bridge. Here is my torrc, with the ContactInfo line listed. Nickname torland ContactInfo keifer dot bly at gmail dot com SOCKSPort 0 # no local SOCKS proxy ORPort 9002 # public bridge must have an open ORPort ExtORPort auto # configure ExtORPort for obfs4proxy ExitPolicy reject *:* # no exits allowed BridgeRelay 1 # relay won't show up in the public consensus PublishServerDescriptor 1 # publish to the bridge authority # use obfs4proxy to provide obfs4 on port 9003 ServerTransportPlugin obfs4 exec C:\Users\keife\AppData\Roaming\tor\PluggableTransports\obfs4proxy.exe ServerTransportListenAddr obfs4 0.0.0.0:9003 Thanks all very much. --Keifer

1 0

Re: [tor-relays] why the network lost 350 relays and some, bridges
by Argo2 12 Jan '19

12 Jan '19

I was intrigued by the high number of consumer IP's that these relay are supposed to be running on while seemingly automated updating the relay version. The nickname made me look into Ubuntu Snaps as a possible tor distribution which led me to this snap: https://snapcraft.io/tor-middle-relay. It was last updated the 9th of January and when you download the stable snap it is actually named 'snap269'. So the maintainer in this case is the snap maintainer, but not necessarily the relay(s) operator. I have not looked into how these snaps actually work but it may be the case that they actually needed the PortForwaring functionality to get tor running inside a snap. Given that information it could very well be the case that these relays are not running behind a NAT and not run by the same operator but actually by a group of different people. > Date: Sat, 12 Jan 2019 08:07:00 +0000 > From: nusenu <nusenu-lists(a)riseup.net> > >> this occurred when these relays upgraded from tor 0.3.3.10 to 0.3.4.9 >> (package maintainer update) >> >> All these relays were behind NAT devices and they relied on a tor >> feature that got removed between these two versions: >> >>> o Removed features: >>> - The PortForwarding and PortForwardingHelper features have been >>> removed. [...]https://trac.torproject.org/projects/tor/ticket/25409 > > I guess I somehow expected that: the maintainer patched tor 0.3.4.10 to added this > feature again and here we go again with the flood of relays using that version of tor: > > 79 relays from 2019-01-11: > > | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | > |------+-------+------------+------------+-----------+-----------------+------------------------------------------+------+-------+--------+-------+-----------+---------------+------------------------------------------| > | 0 | 0 | 01:06:55 | snap269 | 0.3.4.10 | 117.104.229.222 | Instatelecom Limited | af | 43453 | 0 | Linux | None | 1 | CF52FF9F481C618E540D5DACB0C2875F1B7687B5 | > | 0 | 0 | 01:27:25 | snap269 | 0.3.4.10 | 90.253.141.146 | Vodafone Limited | gb | 46089 | 0 | Linux | None | 1 | B483C5FE8A2888F8E02885D8488404DBBEFBCF3B | > [SNIP]

3 3

why the network lost >350 relays and some bridges
by nusenu 12 Jan '19

12 Jan '19

As some of you might have noticed the tor network recently lost a noticeable number of relays and bridges as seen in the metrics.tpo relay graphs (0.7% cw fraction). https://metrics.torproject.org/networksize.html https://pbs.twimg.com/media/DwGAESoXgAEoB6L.jpg this occurred when these relays upgraded from tor 0.3.3.10 to 0.3.4.9 (package maintainer update) All these relays were behind NAT devices and they relied on a tor feature that got removed between these two versions: > o Removed features: > - The PortForwarding and PortForwardingHelper features have been > removed. [...]https://trac.torproject.org/projects/tor/ticket/25409 The portforwarding worked only in about 5% of cases so only 350 of the over 6000 relays actually became reachable. Since I still believe these relays are not run by humans I hope they remain unreachable behind their NAT routers. -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

3 4

Tor Relay Configuration: 'MyFamily' missing - byelitehacks
by nusenu 11 Jan '19

11 Jan '19

Hi byEliteHacks, 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#conatfynndo… Some more background: https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… Let us know if you need any help with this. regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

google Public DNS now Supports DNS-over-TLS
by I 11 Jan '19

11 Jan '19

2 1

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

08 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 07 Jan '19

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

07 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 05 Jan '19

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

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

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

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

03 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