- tor-relays - lists.torproject.org

Re: [tor-relays] Tor relay on Verizon FiOS/FTTH: Advertised Bandwidth capped at ~19.5MiB/s
by Roman Mamedov 19 Feb '19

19 Feb '19

On Mon, 18 Feb 2019 09:06:05 -0500 Neel Chauhan <neel(a)neelc.org> wrote: > Verizon gives both 300 mbps upload and download speeds. Uploads are more > heavily oversubscribed on FiOS, primarily because GPON gives 2.5gbps > downloads and 1.25gbps uploads. But then again the upload will be barely utilized by typical residential Internet users. Still my recommendation is to test your bandwidth in multiple ways first, be it speedtest.net, or (better yet) https://github.com/sivel/speedtest-cli, or iperf3 servers, if you can find any near your location. If tests show that you do get near 300 Mbit both directions, the next step would be to just set up two instances of Tor, as I suggested before in your thread[1]. Actually fun to see my prediction from back then coming true precisely (with regard to getting only 200 Mbit). [1] https://www.mail-archive.com/tor-relays@lists.torproject.org/msg15819.html Running two instances is the universal solution which should improve Tor's bandwidth utilization on almost any connection. -- With respect, Roman

2 2

IRC operator meeting - February 7th
by Colin Childs 14 Feb '19

14 Feb '19

Hi everyone, As previously discussed (https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html <https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html>) we are resuming our IRC relay operator meetings this Thursday, February 7th @ 2:00UTC. These meetings will be held in #tor-meeting on irc.oftc.net <http://irc.oftc.net/>. If you’d like to add to the agenda, please edit the pad at https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6D… <https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6D…> See you all there!

2 3

Re: [tor-relays] BadExit why?
by Olaf Grimm 13 Feb '19

13 Feb '19

Thank you for the answer. I try to get a new IP from the Trabia support. Olaf Am 12.02.19 um 21:51 schrieb David Goulet: > On 12 Feb (21:35:29), Olaf Grimm wrote: >> inet 178.175.148.15 > Thanks Olaf! > > That IP was flagged as rewritting bitcoin addresses on Jan 21st, 2019. > > It appears you re-used a malicious IP from I.C.S. Trabia-Network S.R.L. > > Do you have an easy way to request a new IP for that Exit node or it is kind > of a pain? > > Un-blacklisting a relay that is still not considered expired from our reject > rule set can be a laborious process because essentially, we have to make a > case to the directory authorities and they decide if they remove the rule or > not based on our arguments ;). > > So changing the IP would be definitely the easiest way else we can try to > convince the dirauth :). > > Sorry for the inconvenience! > David > >> Am 12.02.19 um 21:34 schrieb David Goulet: >>> On 12 Feb (21:30:10), Olaf Grimm wrote: >>>> Hello ! >>>> >>>> I provisioning a new exit since two hours. It is a totally new relay in >>>> a VM. My other relays at the same provider are ok. Why I see "BadExit" >>>> in Nyx??? Now my first bad experience with my 11 relays... >>>> >>>> fingerprint: CCDC4A28392C7448A34E98DF872213BC16DB27CD >>>> Nickname Hydra10 >>> This relay is not yet on Relay Search: >>> >>> http://rougmnvswfsmd4dq.onion/rs.html#search/CCDC4A28392C7448A34E98DF872213… >>> >>> I'm guessing it is quite new. >>> >>> That fingerprint is *not* set as a BadExit so this means you might have gotten >>> the IP address of an old BadExit. >>> >>> Can you share the address so I can look it up? >>> >>> Thanks! >>> David >>> >>>> At all exits I have the same firewall rules and torrc configs: >>>> >>>> ufw status >>>> Status: active >>>> >>>> To Action From >>>> -- ------ ---- >>>> 22/tcp ALLOW Anywhere >>>> 9001/tcp ALLOW Anywhere >>>> 9030/tcp ALLOW Anywhere >>>> 80/tcp ALLOW Anywhere >>>> 443/tcp ALLOW Anywhere >>>> 1194/tcp ALLOW Anywhere >>>> 53/tcp ALLOW Anywhere >>>> 53/udp ALLOW Anywhere >>>> 1194/udp ALLOW Anywhere >>>> 22/tcp (v6) ALLOW Anywhere (v6) >>>> 9001/tcp (v6) ALLOW Anywhere (v6) >>>> 9030/tcp (v6) ALLOW Anywhere (v6) >>>> 80/tcp (v6) ALLOW Anywhere (v6) >>>> 443/tcp (v6) ALLOW Anywhere (v6) >>>> 1194/tcp (v6) ALLOW Anywhere (v6) >>>> 53/tcp (v6) ALLOW Anywhere (v6) >>>> 53/udp (v6) ALLOW Anywhere (v6) >>>> 1194/udp (v6) ALLOW Anywhere (v6) >>>> >>>> Please take a look what happens. >>>> >>>> Olaf >>>> _______________________________________________ >>>> tor-relays mailing list >>>> tor-relays(a)lists.torproject.org >>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >>> _______________________________________________ >>> tor-relays mailing list >>> tor-relays(a)lists.torproject.org >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > >

2 1

BadExit why?
by Olaf Grimm 13 Feb '19

13 Feb '19

Hello ! I provisioning a new exit since two hours. It is a totally new relay in a VM. My other relays at the same provider are ok. Why I see "BadExit" in Nyx??? Now my first bad experience with my 11 relays... fingerprint: CCDC4A28392C7448A34E98DF872213BC16DB27CD Nickname Hydra10 At all exits I have the same firewall rules and torrc configs: ufw status Status: active To Action From -- ------ ---- 22/tcp ALLOW Anywhere 9001/tcp ALLOW Anywhere 9030/tcp ALLOW Anywhere 80/tcp ALLOW Anywhere 443/tcp ALLOW Anywhere 1194/tcp ALLOW Anywhere 53/tcp ALLOW Anywhere 53/udp ALLOW Anywhere 1194/udp ALLOW Anywhere 22/tcp (v6) ALLOW Anywhere (v6) 9001/tcp (v6) ALLOW Anywhere (v6) 9030/tcp (v6) ALLOW Anywhere (v6) 80/tcp (v6) ALLOW Anywhere (v6) 443/tcp (v6) ALLOW Anywhere (v6) 1194/tcp (v6) ALLOW Anywhere (v6) 53/tcp (v6) ALLOW Anywhere (v6) 53/udp (v6) ALLOW Anywhere (v6) 1194/udp (v6) ALLOW Anywhere (v6) Please take a look what happens. Olaf

3 2

plans to require ContactInfo to be non-empty
by nusenu 12 Feb '19

12 Feb '19

Hi, due to some recent and ongoing events related to a malicious entity running tor relays I'll start to pursue an idea that I had for some time: require non-empty ContactInfo (non-empty does not mean valid email address) This is primarily a non-technical policy discussion which will take place on tor-dev@. If you want to help right away and currently don't make use of the ContactInfo, please set it. If you think such a change would negatively affect you please let me know (off-list is also fine if you prefer). thanks, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

9 12

2 ip addresses at the same device, works except for the DirPort
by Toralf Förster 08 Feb '19

08 Feb '19

I ordered a 2nd ip address for my server and put them in the first order in my network configuration. I do wonder, why this adapted torrcconfiguration: $> cat /etc/tor/torrc # torrc at tor-relay # PIDFile /var/run/tor/tor.pid DataDirectory /var/lib/tor/data Nickname zwiebeltoralf OutboundBindAddress 5.9.158.75 DirPort 80 ORPort 443 DirPort [2a01:4f8:190:514a::2]:80 NoAdvertise ORPort [2a01:4f8:190:514a::2]:443 ControlPort 9051 Log warn file /tmp/warn.log #Log notice file /tmp/notice.log #Log info file /tmp/info.log ExitRelay 0 IPv6Exit 0 works at the first glance (about 6,000 connection) but still give after a while in the log: Feb 06 19:59:08.000 [notice] Tor 0.4.0.1-alpha opening log file. Feb 06 20:19:26.000 [warn] Your server (<xx>:80) has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. (where <xx> is the new main ip address at my eth0 device) -- Toralf PGP C4EACDDE 0076E94E

2 2

Tor meetup @ Onionspace, Berlin
by Vasilis 04 Feb '19

04 Feb '19

Dear Tor friends and relay operators, Tomorrow (02.02.2019) a relay operators meetup will take place at Onionspace, Berlin. When: Saturday, February 2nd, 2019 Time: 16:00 / 4:00 PM Where: Gottschedstrasse 4, Entrance 4, 13357 Berlin (U Nauener Platz) Event link: https://blog.torproject.org/events/tor-meetup-berlin Hope to see many of you there! Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

3 2

note to Falback Directory operators: bandwidth wasting bot
by starlight.2018q2＠binnacle.cx 03 Feb '19

03 Feb '19

For the last year a bot of some kind has loaded Fallback Directory relays with excessive directory document requests. Some detail can be found in ticket #27921 at https://trac.torproject.org/projects/tor/ticket/27921. To determine if your relay is affected, look the relay up in https://metrics.torproject.org/rs.html, click the 6-Month history tab, and examine the graph for significantly higher "write bytes per second" relative to "read bytes per second". I find this annoying (since I pay for the wasted bandwidth) and came up with a one-line hack that mitigates the abuse without impairing the usefulness of the DIR service to normal relays and clients. If you compile your daemon from source and are interested contact me directly for the patch.

2 1

Re: [tor-relays] Tor RAM usage (DoS or memory leaks?) - Flood of circuits
by petrarca＠protonmail.ch 03 Feb '19

03 Feb '19

There is something really strange going on indeed. What I noticed is an increase of circuits and my device running out of memory until it stopped working so I had to reboot it on 31. Jan. Then again the memory usage increased until it leveled out at a rather unusual, high usage. The actual bandwidth usage is not unusual though (always around 2Mbps on my relay). Attached a screenshot of my memory usage the last few days (I hope attachments do work here; it's in fact Tor using that memory as could be checked with ps and htop). Heartbeat messages of the log are: Jan 31 10:57:56.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 447 circuits open. I've sent 2.66 GB and received 2.65 GB. Jan 31 16:57:56.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 19764 circuits open. I've sent 9.59 GB and received 9.54 GB. Jan 31 22:57:56.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 54178 circuits open. I've sent 12.36 GB and received 12.30 GB. Feb 01 04:57:56.000 [notice] Heartbeat: Tor's uptime is 23:50 hours, with 79333 circuits open. I've sent 14.89 GB and received 14.81 GB. Feb 01 10:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 5:50 hours, with 110815 circuits open. I've sent 19.55 GB and received 19.45 GB. Feb 01 16:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 11:50 hours, with 141724 circuits open. I've sent 24.03 GB and received 23.90 GB. Feb 01 22:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 17:50 hours, with 12829 circuits open. I've sent 29.96 GB and received 29.75 GB. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 1. February 2019 23:50, Roman Mamedov <rm(a)romanrm.net> wrote: > Hello, > > There seems to be an issue with Tor's memory usage. > Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the > machine got 430 MB into swap, slowing down to a crawl from iowait on accessing > the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" > in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that > doesn't add up to exhausting the 1.5 GB, and there are no other heavy > processes on the machine running. I rebooted it without further investigation. > > And right now on another machine running 2.9.16 I see: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor > > But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up > recently. > > Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, > with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. > Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: > 11361/11361 TAP, 239752/239752 NTor. > Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 > connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; > and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, > and 8779474 v4 connections. > Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits > rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. > Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) > failed. > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > With respect, > Roman > > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

4 3

FOSDEM Relay Operator Meetup
by relaya relaya 02 Feb '19

02 Feb '19

Hello! I read there is a Relay Operator Meetup organized by Colin at. I'm surprised it has not been announced on this list yet. Where and when does it take place exactly? thank you!

2 3

AS: "I.C.S. Trabia-Network S.R.L."
by nusenu 02 Feb '19

02 Feb '19

Hello, if you are the operator of the relays listed bellow, please set MyFamily and contactInfo in your torrc to avoid getting rejected. ornetradar(a)riseup.net: > 2019-02-01 > > | Up | Ext | JoinTime | IP | CC | ORp | Dirp | Version | Contact | Nickname | eFamMembers | FP | > |------+-------+------------+-----------------+------+-------+--------+-----------+---------------------------+--------------+---------------+------------------------------------------| > | 1 | 1 | 13:41:51 | 178.175.132.211 | md | 9001 | 8080 | 0.3.5.7 | chatter | chatter | 1 | E0259C34CEDF2D7A15271336EF65E21171EDF0FE | > | 1 | 1 | 13:44:58 | 178.175.132.210 | md | 9001 | 8080 | 0.3.5.7 | rendon | rendon | 1 | 14678AB26ED87E843B232EAEDF2A7BB384652473 | > | 1 | 1 | 13:44:58 | 178.175.143.158 | md | 9001 | 8080 | 0.3.5.7 | lincoln | lincoln | 1 | 56F55271722E2F8FFC3A77CA3F7F955B703CB027 | > | 1 | 1 | 13:44:59 | 178.175.132.212 | md | 9001 | 8080 | 0.3.5.7 | dossier | dossier | 1 | 1B2E31990B0F0A51920F40D5AB7598D41B214A20 | > | 1 | 1 | 13:44:59 | 178.175.132.213 | md | 9001 | 8080 | 0.3.5.7 | lark | lark | 1 | 1C3EE6E25868F0A8B816B62D81534146F2616008 | > | 1 | 1 | 13:44:59 | 178.175.143.156 | md | 9001 | 8080 | 0.3.5.7 | cuban | cuban | 1 | 1F25B74EF811858112DE18220B456F3CF6EE642E | > | 1 | 1 | 13:44:59 | 178.175.143.157 | md | 9001 | 8080 | 0.3.5.7 | charly | charly | 1 | 3722EEBB445B4E91B1A10CED86CD2E32B3C92D41 | > | 1 | 1 | 13:44:59 | 178.175.132.209 | md | 9001 | 8080 | 0.3.5.7 | matador | matador | 1 | 3E48BE2E2AC257D20546B5547729F4A5096BE39F | > | 1 | 1 | 13:44:59 | 178.175.132.214 | md | 9001 | 8080 | 0.3.5.7 | azorian | azorian | 1 | 72193825EE4EE6F9EF3243D8A7B49DB9122ADF21 | > | 1 | 1 | 13:44:59 | 178.175.143.155 | md | 9001 | 8080 | 0.3.5.7 | contras | contras | 1 | A67EB8AA880ACC94B716E178576142CB25D63B8C | > > https://nusenu.github.io/OrNetRadar/2019/02/01/a1 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Re: [tor-relays] Circuit storms
by starlight.2018q2＠binnacle.cx 02 Feb '19

02 Feb '19

Jan 26 Heartbeat: circuits 6666 sent 103gb received 100gb Jan 26 Heartbeat: circuits 5672 sent 101gb received 98gb Jan 26 Heartbeat: circuits 6156 sent 106gb received 103gb Jan 26 Heartbeat: circuits 5902 sent 92gb received 90gb Jan 27 Heartbeat: circuits 6171 sent 80gb received 78gb Jan 27 Heartbeat: circuits 5920 sent 85gb received 82gb Jan 27 Heartbeat: circuits 4841 sent 82gb received 79gb Jan 27 Heartbeat: circuits 5718 sent 77gb received 71gb Jan 28 Heartbeat: circuits 5676 sent 86gb received 80gb Jan 28 Heartbeat: circuits 5157 sent 84gb received 81gb Jan 28 Heartbeat: circuits 7548 sent 105gb received 102gb Jan 28 Heartbeat: circuits 16448 sent 88gb received 84gb Jan 29 Heartbeat: circuits 31521 sent 107gb received 97gb Jan 29 Heartbeat: circuits 6255 sent 90gb received 86gb Jan 29 Heartbeat: circuits 14920 sent 91gb received 89gb Jan 29 Heartbeat: circuits 21502 sent 75gb received 72gb Jan 30 Heartbeat: circuits 37649 sent 80gb received 76gb Jan 30 Heartbeat: circuits 69831 sent 84gb received 81gb Jan 30 Heartbeat: circuits 16740 sent 102gb received 99gb Jan 30 Heartbeat: circuits 59552 sent 105gb received 101gb Jan 31 Heartbeat: circuits 73727 sent 88gb received 84gb Jan 31 Heartbeat: circuits 12156 sent 74gb received 71gb Jan 31 Heartbeat: circuits 63624 sent 81gb received 79gb Jan 31 Heartbeat: circuits 89129 sent 77gb received 72gb Feb 1 Heartbeat: circuits 98432 sent 105gb received 80gb Feb 1 Heartbeat: circuits 97975 sent 69gb received 66gb Feb 1 Heartbeat: circuits 27443 sent 94gb received 91gb

1 0

Tor RAM usage (DoS or memory leaks?)
by Roman Mamedov 02 Feb '19

02 Feb '19

Hello, There seems to be an issue with Tor's memory usage. Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the machine got 430 MB into swap, slowing down to a crawl from iowait on accessing the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that doesn't add up to exhausting the 1.5 GB, and there are no other heavy processes on the machine running. I rebooted it without further investigation. And right now on another machine running 2.9.16 I see: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up recently. Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: 11361/11361 TAP, 239752/239752 NTor. Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, and 8779474 v4 connections. Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) failed. -- With respect, Roman

1 0

tor relay shutsdown
by Neelix 02 Feb '19

02 Feb '19

Hello, I have setup a tor exit but it seems like that is shutsdown after x hours. I can not find anything in the logs. Anyone knows how this might happen? Regards, Neelix fingerprint: 32A6 5D7A 955C 546C 0E9B F559 EB09 D028 36A3 79E

5 11

Circuit storms
by Felix 01 Feb '19

01 Feb '19

Hi everybody Circuit storms observed of up to 100k and 250k per relay for over hours. Consumed BW rises by about 10%. Number of stateful server connections is higher. Using Tor 356 to 401. Anybody else observes that? Switching to some paranoid server settings for some days :) -- Cheers, Felix

2 2

Installing Tor As Windows Service And Updating Via Script (was RE: Having Trouble With Speed Of OBFS4 Bridge)
by Keifer Bly 30 Jan '19

30 Jan '19

Darn, I just restarted the relay because tor 0.3.5.7 came out today before seeing this email. I have been playing with the Windows Powershell regarding this and made some interesting discoveries. So, I found that the Windows Powershell equivalent to linux's "apt-get" is "install-package -Name". And so, I tried running "install-package -name tor" and got this error (see the attached screenshot). The error is that tor project is not in the list for Windows to install packages from on Windows (it's not finding tor packages as a result), as I discovered at the other attached image. However, according to my research at https://docs.microsoft.com/en-us/powershell/module/packagemanagement/regist… Windows Powershell can register sources to install packages from via Register-PackageSource -Name command listed. So Something along the lines of PS C:\> Register-PackageSource -Name "tor" -Location "http://torurl" -ProviderName "TorProject" may have interesting results possibly. What is the tor packages download url so I may try this? Once this is returned to me I will return to the list with my findings. Cheers. -----Original Message----- From: tor-relays <tor-relays-bounces(a)lists.torproject.org> On Behalf Of teor Sent: Monday, January 28, 2019 10:24 PM To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] Having Trouble With Speed Of OBFS4 Bridge On January 29, 2019 3:45:55 AM UTC, Keifer Bly <keifer.bly(a)gmail.com> wrote: >Thanks. I also wanted to ask, is there a way to upgrade tor using >Windows Powershell? The way I am doing that is downloading the tor >expert bundle when a new one is released and manually replacing both >tor.exe and obfs4.exe with the new versions. I have tor installed as a >Windows service via powershell, so is there a way to do this? I am >asking because the current tor expert bundle is tor 0.3.4.8 whereas I >believe 0.3.5.7 has been released. Thank you. Hmm, I thought someone answered this question already, but I can't find the answer in the list archives. 0.3.4.8 is still a supported version. You don't need to update. One simple way to keep Tor up to date on Windows is to use the Chocolatey package manager to install the tor package: https://chocolatey.org/packages/tor It has Tor 0.3.3.9, which is still a recommended version. You can script chocolately using the "choco" command. Otherwise, you can script powershell to download and install packages. I can't help you with the details, because I don't do a lot of work on Windows. But maybe someone else on the list can. If you work out how to do it, please write back to the list with the scripts you used. T -- teor ---------------------------------------------------------------------- _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

IRC relay operator meetups
by Colin Childs 30 Jan '19

30 Jan '19

Hi everyone, The IRC Tor relay operator meetups are beginning again! To get started, we are going to be holding these meetups once per month. The meetups will be held the first Thursday of the month, at 2:00UTC. This means the February meetup will be held next week, on the 7th. To allow us to use meetbot for recording the meetup, we will be holding them in #tor-meeting. On the first Monday of the month, I will send out a reminder email with the date and time, along with a pad that people can add discussion topics to. For February, the reminder email will go out on the 4th. I look forward to seeing everyone there!

1 0

Hetzner - "no.spam@example.com" relays
by nusenu 30 Jan '19

30 Jan '19

Hi, to the operator of the relays listed bellow. You care currently not setting the MyFamily option on your relays, which puts tor users at risk. Please configure your relays with MyFamily to avoid getting your relays rejected. more information: https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays#Whatis… 2019-01-28 | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | |------+-------+------------+---------------------+-----------+----------------+---------------------+------+-------+--------+-------+---------------------+---------------+------------------------------------------| | 0 | 0 | 01:34:19 | somerelay | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 24C3BC672621D6FCB7923DE031738B23EE0C1819 | | 0 | 0 | 01:48:53 | somerelay | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CBDCA8B16E2D4111A6618BAB3F114C358B8E35DB | | 1 | 0 | 05:00:50 | somerelay1IHcuer9Cn | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CA307A53194D6DE8B033226C541654117AFCF5F2 | | 1 | 0 | 02:54:44 | somerelayId8wPoBbRJ | 0.3.3.7 | 116.203.57.160 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | F9578C192A76062C2B49F938A53291AA5CE3CFBF | | 1 | 0 | 02:54:49 | somerelayT7WbYRznBW | 0.3.3.7 | 116.203.59.81 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CFDF026F3FC52BF347A395A1224D70D9ACBEF9C5 | | 1 | 0 | 02:55:45 | somerelayung2AiqzXu | 0.3.3.7 | 116.203.66.45 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 97F47C07A3DEA4C1A885C2C15008592635DA54B6 | | 1 | 0 | 02:54:46 | somerelayvpoDStFnGZ | 0.3.3.7 | 94.130.184.189 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 5CD0F83B59229F86419757FE54CFF6EE859EA0ED | https://nusenu.github.io/OrNetRadar/2019/01/28/a7 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Having Trouble With Speed Of OBFS4 Bridge
by Keifer Bly 29 Jan '19

29 Jan '19

Hello, So my OBFS4 bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032E CF14E5B9E9A seems to be having some speed issues, only reaching about 40-50 kb/s of speed. This is strange, as it should be much faster than this. My thoughts on why this is happening: Where I living, am probably nowhere near the bridge authorities for one. I am running an obfuscated bridge (which as this requires an additional process to be running alongside the tor process, could this be a part of it?) I am running off of the only internet provider available in my area (Charter / Spectrum) which is an isp that uses cable structure so maybe they have some kind of limitation in place? My router is a Netgear Orbi router which should be able to handle up to 60,000 connections at once so there should be no issue there. Any help is appreciated, thank you. --Keifer

3 8

diff-cache OOM
by notatorserver 29 Jan '19

29 Jan '19

I am running tor 4.0.1-alpha inside a docker container with a memory limit (6GB). Tor runs out of memory and aborts or crashes periodically. Usually I see an error message like this: Could not mmap file "/var/lib/tor/data/diff-cache/1149": Out of memory ...(repeated some number of times) followed by segfault Sometimes I see a message: Out of memory on malloc(). Dying followed by abort. Am I correct to assume the diff-cache is the issue here? Looking at the files it seems they are all pretty small (~500K). Is some badly behaved client requesting 12,000 of these diffs causing my relay to mmap them all at once? or is it just expensive to generate and generating 30-60 at once is enough to use all the memory? Are there any config options to reject expensive queries or otherwise limit concurrency? Thanks

2 2

Shutdown of fallback directory mirror armbrust: E781F4EC69671B3F1864AE2753E0890351506329
by Michael Armbruster 27 Jan '19

27 Jan '19

Dear tor-relay list, After a long time maintaining an exit relay that was also chosen to be a fallback directory mirror, I decided that the time has come to shut the relay down. It has only financial reasons (being a cheap server, but still using money out of my own pocket) and I will stay a happy user of Tor and, of course, will provide a new relay as soon as my financial situation gets better. How should we proceed and how long should I still let the fallback mirror run in order to gracefully migrate the fallback status away from my server? I do not want to disappear immediately without any further notice, so I wanted to ask how to further proceed. Kind regards, Michael Armbruster

2 1

Overlay Networks: Research Improvements and Attacks [was: planetlab butterfly relays]
by grarpamp 24 Jan '19

24 Jan '19

On 1/23/19, nusenu <nusenu-lists(a)riseup.net> wrote: > thanks for adding tor relays. > If you are using them for research purposes please ensure > you follow the safety guidelines: > https://research.torproject.org/safetyboard.html > https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… > https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays > | Up | Ext | JoinTime | Nickname | Version | IP | > AS | CC | ORp | Dirp | OS | > Contact | eFamMembers | FP | > https://twitter.com/nusenu_ > https://mastodon.social/@nusenu As many know, many guidelines regarding the stronger distributed encrypted overlay and messaging networks out there are naturally voluntary, and research and attacks are often generally unenforceable and or undetectable when undertaken by qualified adversaries. Many parties [publicly] subscribe to such guidelines, many [silently] don't. That's the nature [and one of the risks] of such networks, indeed of any network. Such adversaries exist and are highly active and capable. Know your adversary. Strengthen your designs to match and best them. As to the nodes, they're all planet-lab.net hosts, planetlab has at least two known tor slices "okstate_tor" and "uml_ZhenLing", some public research outputs [or not] of which might be listed below... https://www.cs.uml.edu/~xinwenfu/paper/TorCellSize_ICC11_Fu.pdf https://www.cs.uml.edu/~xinwenfu/paper/TorWard14_Fu.pdf http://cse.seu.edu.cn/PersonalPage/zhenling/publications_files/infocom2014_… http://cse.seu.edu.cn/PersonalPage/zhenling/publications_files/infocom2013_… http://cse.seu.edu.cn/PersonalPage/zhenling/publications_files/infocom2012_… https://news.okstate.edu/articles/communications/2015/tedx-returns-oklahoma… https://www.youtube.com/watch?v=9QsjkJcUznA MEMEX Christopher White ‎Jiangmin yu, Eric Chan-Tin: Realistic Cover Traffic to Mitigate Website Fingerprinting Attacks DOI: 10.1109/ICDCS.2018.00175 Conference: 2018 IEEE 38th International Conference on Distributed Computing Systems (ICDCS) Identifying Webbrowsers in Encrypted Communications DOI: 10.1145/2665943.2665968 Revisiting Circuit Clogging Attacks on Tor DOI: 10.1109/ARES.2013.17 Conference: Availability, Reliability and Security (ARES), 2013 Eighth International Conference on https://chantin.cs.luc.edu/~chantin/ARES2013.pdf Application Of Data Analytics - Case Studies https://shareok.org/bitstream/handle/11244/54637/Yu_okstate_0664D_15098.pdf

1 0

planetlab butterfly relays
by nusenu 24 Jan '19

24 Jan '19

Hi bf@ctct, thanks for adding tor relays. If you are using them for research purposes please ensure you follow the safety guidelines: https://research.torproject.org/safetyboard.html You care currently not setting the MyFamily option on your relays, which puts tor users at risk. Please configure your relays with MyFamily. more information: https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays#Whatis… | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | |------+-------+------------+--------------+-----------+-----------------+------------------------------------------+------+-------+--------+-------+---------------+---------------+------------------------------------------| | 1 | 0 | 08:03:03 | butterfly002 | 0.3.5.7 | 200.129.132.19 | Associa\u00E7\u00E3o Rede Nacional de En | br | 9001 | 9030 | Linux | bf(a)ctct.org | 1 | 508BDBDA23A6B76D3C5B2D17DBEA2A4E170859BD | | 1 | 0 | 09:40:10 | butterfly003 | 0.3.5.7 | 216.48.80.12 | University of Ottawa | ca | 9001 | 9030 | Linux | bf(a)ctct.org | 1 | 09F83FDF39A459D91AB8EC18B44A7F389BB5D87C | | 1 | 0 | 09:47:23 | butterfly004 | 0.3.5.7 | 200.17.202.195 | Fundacao da UFPR para o DCTC | br | 9001 | 9030 | Linux | bf4(a)ctct.org | 1 | 7BA8CCC7EFE0D6ED1386173631CC825CB39D6F6F | | 1 | 0 | 11:12:56 | butterfly005 | 0.3.5.7 | 129.97.74.12 | University of Waterloo | ca | 9001 | 9030 | Linux | bf5(a)ctct.org | 1 | ECFFC5A820CBFD37AC2F85AA2C8DC77F87796F16 | | 1 | 0 | 12:07:56 | butterfly006 | 0.3.5.7 | 200.19.159.35 | Associa\u00E7\u00E3o Rede Nacional de En | br | 9001 | 9030 | Linux | bf6(a)ctct.org | 1 | F1F92CC70007DB1EB63B28623B8481863ED3B29F | | 1 | 0 | 12:22:19 | butterfly007 | 0.3.5.7 | 128.8.126.111 | University of Maryland | us | 9001 | 9030 | Linux | bf7(a)ctct.org | 1 | FCA01B39D2CA5DAE896EAAABDB010B0040D068EF | | 0 | 0 | 11:56:55 | butterfly008 | 0.3.5.7 | 192.33.90.67 | SWITCH | ch | 9001 | 9030 | Linux | bf8(a)ctct.org | 1 | 2447A5A12AC3DB748317F97E3317814C42BF0380 | | 1 | 0 | 13:10:27 | butterfly008 | 0.3.5.7 | 133.69.32.131 | Asia Pacific Advanced Network - Japan | jp | 9001 | 9030 | Linux | bf8(a)ctct.org | 1 | 748653AF527B393EFB5870DFA840F8FD578E19BA | | 1 | 0 | 12:36:30 | butterfly009 | 0.3.5.7 | 188.44.50.106 | Federal State Educational Institution of | ru | 9001 | 9030 | Linux | bf9(a)ctct.org | 1 | DCC2DD20CC44DC617A859EA9EFE1A40C5215CAC0 | | 1 | 0 | 13:28:32 | butterfly010 | 0.3.5.7 | 134.117.226.180 | Carleton University | ca | 9001 | 9030 | Linux | bf10(a)ctct.org | 1 | FD82A15B62B73DF4CE20003B651CBB7384C37539 | -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

DNS Server
by dns1983＠riseup.net 24 Jan '19

24 Jan '19

Hello, i'm a student, so I lack many networking notions. Which are the most privacy reliable public dns servers? I don't exactly know how choose a third part DNS server. I read that cloudfare servers are audited by third parties but I'm not sure that I can trust. do you think that audition is trustworthy? Thanks -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.

4 11

Tor meetup @ RADIX hacklab, Athens
by Vasilis 19 Jan '19

19 Jan '19

Dear Tor friends and relay operators, Next Friday (25.01.201) a Tor relay operators meetup will take place at RADIX hacklab, Athens. When: Friday, January 25th, 2019 Time: 19:00 / 7:00 PM Where: Kaniggos 34 & Stournari, Athens 10682, Greece Event link: https://blog.torproject.org/events/tor-meetup-athens Hope to see many of you there. Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0