tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

Become a Fallback Directory Mirror (deadline: July 23)
by gus 17 Sep '20

17 Sep '20

Dear Relay Operators, Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint. Important: you have until July 23 2020 to reply to this message to get in the fallback directory mirror list. If your relay is on the current fallback list, you don't need to do anything. If you're asking: Q: What's a fallback directory mirror? Fallback directory mirrors help Tor clients connect to the network. For more details, see [1]. Q: Is my relay on the current list? Search [2] and [3] for your relay fingerprint or IP address and port. [2] is the current list of fallbacks in Tor. [3] is used to create the next list of fallbacks. Q: What do I need to do if my relay is on the list? Keep the same IP address, keys, and ports. Email tor-relays if the relay's details change. Q: Can my relay be on the list next time? We need fast relays that will be on the same IP address and port for 2 years. Reply to this email to get on the list, or to update the details of your relay. Once or twice a year, we run a script to choose about 150-200 relays from the potential list [3] for the list in Tor [2]. Q: Why didn't my relay get on the list last time? We check a relay's uptime, flags, and speed [4]. Sometimes, a relay might be down when we check. That's ok, we will check it again next time. It's good to have some new relays on the list every release. That helps tor clients, because blocking a changing list is harder. cheers, Gus [1] https://gitlab.torproject.org/tpo/core/tor/-/wikis/NetworkTeam/FallbackDire… [2] https://gitweb.torproject.org/tor.git/tree/src/app/config/fallback_dirs.inc [3] https://gitweb.torproject.org/fallback-scripts.git/tree/fallback_offer_list [4] https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_… -- The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/

26 30

OVH Warnings
by Dr Gerard Bulger 15 Sep '20

15 Sep '20

OVH seemed to have upped their game with more information than just throwing all traffic into "mitigation" which can result in bad exit status, with no information as to what their systems are detecting as a threat of denial of service attack. For the first time I got an email.no mitigation. Dear Customer, Abnormal activity has been detected on your VPS Attack detail : 4Kpps/2Mbps dateTime srcIp:srcPort dstIp:dstPort protocol flags bytes reason 2020.09.15 19:02:21 CEST <http://51.38.64.136:42845/> my ip:42845 <http://212.22.93.124:25565/> 212.22.93.124:25565 TCP SYN 60 ATTACK:TCP_SYN 2020.09.15 19:02:21 CEST <http://51.38.64.136:39673/> my ip:39673 <http://212.22.93.124:25565/> 212.22.93.124:25565 TCP SYN 60 ATTACK:TCP_SYN Etc Gerry

1 0

Odd error with tor 4.3 log file
by Keifer Bly 14 Sep '20

14 Sep '20

1 0

non-encrypted connections from Tor exit relays
by kirgali＠riseup.net 10 Sep '20

10 Sep '20

hi, generalized question about Tor exit relays and exit relay operators. do some exit relay operators have a policy to prevent connections leaving their exit node via non-encrypted ports (e.g. port 25)? this could be a philosophical position - not even wanting to be in a position to observe users' data passing through the exit node in clear text. or a pragmatic position - hoping that encrypted connections provide some level (even very weak) of plausible deniability in the event that a connection attracts the attention of law enforcement. this is just my thoughts.

3 2

Re: [tor-relays] Could Zoom be using the wrong dan-tor blacklist
by Eddie 10 Sep '20

10 Sep '20

Gus, It's "OnNoNotAnotherTorRelay"; D195E5CE8AE77BAC91673E6CFB7BD0AF57281646 Cheers. On 9/9/2020 7:44 PM, gus wrote: > Hi Eddie, > > Could you inform your relay fingerprint? > > Thanks, > Gus > > On Mon, Sep 07, 2020 at 11:54:47AM -0700, Eddie wrote: >> Starting yesterday (maybe Saturday) we have been unable to initiate any Zoom >> calls. They just sit "connecting". According to Zoom, there are no issues >> that would lead to this. >> >> My investigation, traces I have run on the server, and using a VPN (on a >> tablet on my LAN) show the exact same symptoms I had a year (or so) ago with >> a couple of AT&T sites, which I eventually narrowed down to being caused by >> the same blacklist by routinely switching IPs and then eventually shutting >> down my relay temporarily. >> >> Is anyone else seeing similar and/or have any suggestions as I rather not >> have to shut my relay down. Running a multitude of VPNs on my internal >> machines is not really an option and my relay isn't going to function if I >> throw a VPN on my server. >> >> Cheers. >> >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

SMTP port 465/587
by kirgali＠riseup.net 10 Sep '20

10 Sep '20

Hi, question for Tor exit relay operators. Do exit relay operators allow connections to SMTP port 587 more than port 465? The RiseUp webpage says “SMTP port 465 is often blocked by Tor exit nodes but port 587 is less frequently blocked” (https://riseup.net/en/email/clients) because port 465 is considered deprecated (see RFC 8314). In practice do most exit relay operators allow connections to both SMTP ports? Thanks

1 0

OVH Mitigation
by Dr Gerard Bulger 10 Sep '20

10 Sep '20

I know we should dilute our dependence on OVH, but cheap and seem to ignore the fact the machine is an exit node. OVH has a seemingly patented a system to deal with denial of service attacks. I am not sure what they detect but when they do we get this: "We have just detected an attack on IP address x.x.x.x. In order to protect your infrastructure, we vacuumed up your traffic onto our mitigation infrastructure. The entire attack will thus be filtered by our infrastructure, and only legitimate traffic will reach your servers. At the end of the attack, your infrastructure will be immediately withdrawn from the mitigation" To be fair, the automated system takes it off after an our or two. If my tor server is left in this mitigated state, the tor exit gets labelled a BAD EXIT which is something to avoid as takes days to be trusted again. As soon as I get their email I now stop TOR to prevent that embarrassing label, and perhaps doing so stops whatever it is OVH is detecting. Being shutdown for a few hours seems better than being a bad exit. Gerry

3 2

Could Zoom be using the wrong dan-tor blacklist
by Eddie 07 Sep '20

07 Sep '20

Starting yesterday (maybe Saturday) we have been unable to initiate any Zoom calls. They just sit "connecting". According to Zoom, there are no issues that would lead to this. My investigation, traces I have run on the server, and using a VPN (on a tablet on my LAN) show the exact same symptoms I had a year (or so) ago with a couple of AT&T sites, which I eventually narrowed down to being caused by the same blacklist by routinely switching IPs and then eventually shutting down my relay temporarily. Is anyone else seeing similar and/or have any suggestions as I rather not have to shut my relay down. Running a multitude of VPNs on my internal machines is not really an option and my relay isn't going to function if I throw a VPN on my server. Cheers.

1 0

How many threads needed for unbound at a fast relay?
by Toralf Förster 05 Sep '20

05 Sep '20

I do wonder about a reasonable number. -- Toralf

3 3

Re: [tor-relays] Tor relay marked "false positive" from NCSC-FI
by Peter Gerber 03 Sep '20

03 Sep '20

Hi tschador(a)posteo.de: > today my ISP received an abuse report from > ncsc-fi-autoreporter(a)traficom.fi [1]: > --- > The information below is presented in the following format: > ASN | IP | TIMESTAMP (UTC) | PTR/DNAME | CC | TYPE | CASE | INFO > > 24940|95.217.16.212|2020-09-01 07:27:48 > +0000|95.217.16.212|DE|malweb|1130659|Datasource: b, Url: > hxxp://95.217.16.212/tor/server/fp/23ad6b165137d957c09aa0f7a3ee7b05cec4a8f2, > Http Request: GET, Additional Information: This host is most likely > serving a malware URL., Artifact Hash: 69b9e2721018f0ebaebf901d98d8c9b9 > --- > The ip belongs to my non-exit relay. [2] There is no action required for > me, but I wonder why they mark traffic on the dirport as 'malware'? I've received a similar mail not too long ago. Looking into it, I couldn't but conclude that it was some sort of phishing scam. When following the link one was asked to provide a lot of information. The webpage seems to be outdated, incomplete and nowhere was explained why they'd scan the internet for anything. All in all, the page looked as "phishy" as it gets. For reference, below is the abuse mail I received. Regards Peter -------- Forwarded Message -------- Subject: Fwd: Abuse Message [AbuseID:730BD4:2C]: AbuseCleanMXInfo: [clean-mx-viruses-172313691](95.216.14.206)-->(abuse(a)hetzner.de) viruses sites (1 so far) within your network, please close them! status: As of 2020-08-09 16:47:16 CEST Date: Sun, 09 Aug 2020 16:48:21 +0200 From: abuse(a)hetzner.com Reply-To: abuse(a)hetzner.com To: <removed> Dear Mr Peter Gerber, For your information we are forwarding you the email of the ticket [AbuseID:730BD4:2C]. The source email with details about the issue is attached to this email. Important note: When replying to us, please leave the abuse ID [AbuseID:730BD4:2C] unchanged in the subject line. Kind regards Abuse department Hetzner Online GmbH Industriestr. 25 91710 Gunzenhausen / Germany Tel: +49 9831 505-0 Fax: +49 9831 505-3 abuse(a)hetzner.com www.hetzner.com Register Court: Registergericht Ansbach, HRB 6089 CEO: Martin Hetzner, Stephan Konvickova, Günther Müller For the purposes of this communication, we may save some of your personal data. For information on our data privacy policy, please see: www.hetzner.com/datenschutzhinweis On 09 Aug 16:47, abuse(a)clean-mx.de wrote: > Dear abuse team, > > please have a look on these perhaps offending viruses sites(1) so far. > > Notice: We do NOT urge you to shutdown your customer, but to inform him about a possible infection/misbehavior ! > > status: As of 2020-08-09 16:47:16 CEST > > Please preserve on any reply our Subject: [clean-mx-viruses-172313691](95.216.14.206)-->(abuse(a)hetzner.de) viruses sites (1 so far) within your network, please close them! status: As of 2020-08-09 16:47:16 CEST > > > http://support.clean-mx.de/clean-mx/viruses.php?email=abuse@hetzner.de&resp… > > (for full uri, please scroll to the right end ... > > This information has been generated out of our comprehensive real time database, tracking worldwide viruses URI's > > If your review this list of offending site(s), please do this carefully, pay attention for redirects also! > Also, please consider this particular machines may have a root kit installed ! > So simply deleting some files or dirs or disabling cgi may not really solve the issue ! > > Advice: The appearance of a Virus Site on a server means that > someone intruded into the system. The server's owner should > disconnect and not return the system into service until an > audit is performed to ensure no data was lost, that all OS and > internet software is up to date with the latest security fixes, > and that any backdoors and other exploits left by the intruders > are closed. Logs should be preserved and analyzed and, perhaps, > the appropriate law enforcement agencies notified. > > DO NOT JUST DELETE THE FILES. IF YOU DO NOT FIX THE SECURITY > PROBLEM, THEY WILL BE BACK! > > You may forward my information to law enforcement, CERTs, > other responsible admins, or similar agencies. > > +----------------------------------------------------------------------------------------------- > > |date |id |virusname |ip |domain |Url| > +----------------------------------------------------------------------------------------------- > |2020-08-09 16:05:31 CEST |172313691 |PUA.Win.Trojan.Generic-6629274-0 |95.216.14.206 |95.216.14.206 |http://95.216.14.206/tor/status-vote/current/consensus-microdesc/0232af+14c131+23d15d+27102b+49015f+d586d1+e8a9c4+ed03bb+efcbe7.z > +----------------------------------------------------------------------------------------------- > > > Your email address has been pulled out of whois concerning this offending network block(s). > If you are not concerned with anti-fraud measurements, please forward this mail to the next responsible desk available... > > > If you just close(d) these incident(s) please give us a feedback, our automatic walker process may not detect a closed case > > explanation of virusnames: > ========================== > unknown_html_RFI_php not yet detected by scanners as RFI, but pure php code for injection > unknown_html_RFI_perl not yet detected by scanners as RFI, but pure perl code for injection > unknown_html_RFI_eval not yet detected by scanners as RFI, but suspect javascript obfuscationg evals > unknown_html_RFI not yet detected by scanners as RFI, but trapped by our honeypots as remote-code-injection > unknown_html not yet detected by scanners as RFI, but suspious, may be in rare case false positive > ...javascript.insert Please pay attention for script code after </html> > unknown_exe not yet detected by scanners as malware, but high risk! > all other names malwarename detected by scanners > ========================== > > > yours > > Gerhard W. Recher > (CTO) > > net4sec UG (haftungsbeschraenkt) > > Leitenweg 6 > D-86929 Penzing > > GSM: ++49 171 4802507 > > Geschaeftsfuehrer: Martina Recher > Handelsregister Augsburg: HRB 27139 > EG-Identnr: DE283762194 > > w3: http://www.clean-mx.de > e-Mail: mailto:abuse@clean-mx.de > PGP-KEY: Fingerprint: A4E317B6DC6494DCC9616366A75AB34CDD0CE552 id: 0xDD0CE552 > Location: http://www.clean-mx.de/downloads/abuse-at-clean-mx.de.pub.asc

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays