- tor-relays - lists.torproject.org

DirPortFrontPage file '.....' not found | Permission denied
by Petrusko 02 Apr '21

02 Apr '21

Hey, I'm having a little problem with setting up (my be some rights...) the html page on the relay DIRPort. On my logs : 00:00:03 [NOTICE] Tor 0.4.5.7 opening new log file. 00:00:03 [WARN] Could not open "/var/www/html/tor-relay.html": Permission denied 00:00:03 [WARN] DirPortFrontPage file '/var/www/html/tor-relay.html' not found. Continuing anyway. I've not found any information about how to set up this correctly. Many thanks in advance.

4 4

ipv6 ORPort + DIRPort too ?
by Petrusko 01 Apr '21

01 Apr '21

Hey, I've set up a new relay, available with ipv4 and ipv6. And I'm not sure if I can serve DIRPort on the ipv6 too ? In the torrc file, I've config : ORPort 9001 ORPort [xxxx:xxxx:xxx:x:xxxx:xxxx:xxxx:xxx]:9001 DIRPort 9030 Is it allowed to add something like this, to advertise on ipv6 too ?? : DIRPort [xxxx:xxxx:xxx:x:xxxx:xxxx:xxxx:xxx]:9030 Thank you all !

4 7

Help with FreeBSD relays
by xplato 31 Mar '21

31 Mar '21

Greetings, I am a bit of a noob here so please bear with me. I ran a relay using Ubuntu with very few issues however I decide to add an additional relay and decided to use FreeBSD. They will only run for around 18 hours and then they shut down. I have adjust the torrc file every way I know how and increased the Max vnodes thinking this may have been my issue. I can post the sysrc and torrc if needed. Anyone that might help me figure this out I would be grateful otherwise I am going to reluctantly move them both back to Ubuntu. Thanks, Dan Sent from ProtonMail for iOS

5 13

relay impersonation (contactinfo)
by nusenu 31 Mar '21

31 Mar '21

Hi, I'd like to raise your awareness of an ongoing scheme of questionable entities that make use of your name or relay contactinfo and/or relay nicknames. Those using other people's relay _nicknames_ got and get spotted by multiple people already and are somewhat obvious (at least for now), but I'd like to highlight those using familiar names in contactInfo that are likely less frequently uncovered because people lookup their relays by searching for their relay nicknames (and not so often by searching their contactinfo). So here are two practical things that you can do to help uncover more of them: - list your relay fingerprints under the well-known tor-relay URI: https://<your domain>/.well-known/tor-relay/rsa-fingerprint.txt and add "url:<your domain> proof:uri-rsa ciissversion:2" to your ContactInfo to allow for automated linkability verification. This protects your relays against spoofing of the url field. A domain is not required: You can use github-pages or similar if you do not have a domain. more details: https://gitlab.torproject.org/tpo/core/torspec/-/blob/master/proposals/326-… https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/ Thanks to the 291 relays, that allow for automated verification already. Verifiable relay groups also get graphs on OrNetStats, for an example see: https://nusenu.github.io/OrNetStats/artikel10.org.html - search for your names/nicknames/org names/... in the ContactInfo field. On Relay Search you can do so using "contact:searchstring" Be creative in your search terms. This even makes sense if you do not run relays at all but your name is somewhat known in this context. kind regards, nusenu -------- Forwarded Message -------- Subject: tor relays rosiwig429(at)lidte(dot)com Date: Tue, 30 Mar 2021 23:55:01 > 2021-03-29 > > | Up | Ext | JoinTime | IP | AS | CC | ORp | Dirp | OS | Version | Nickname | eFamMembers | FP | > |------+-------+------------+----------------+------------------------------------------+------+-------+--------+-------+-----------+------------------+---------------+------------------------------------------| > | 1 | 1 | 06:25:11 | 103.82.32.14 | CMC Telecom Infrastructure Company | vn | 9001 | 9030 | Linux | 0.4.5.7 | coffswifi5 | 1 | B8D95BB1AAFB6F234EC50A100F46E4CC8E8E90FB | > | 1 | 1 | 07:34:40 | 78.138.135.110 | Ojsc oao Tattelecom | ru | 9001 | 9030 | Linux | 0.4.5.7 | artikel5ev3b2 | 1 | 771C9BC56DF4B29BA97CAA9387FB1FC140CFE3E3 | > | 1 | 1 | 13:43:04 | 103.56.156.143 | VNPT Corp | vn | 9001 | 9030 | Linux | 0.4.5.7 | CalyxInstitute18 | 1 | 04998AB63A49C4A0B5A5CD2994D95D098D2B5399 | > | 1 | 1 | 14:28:18 | 77.245.158.134 | Niobe Bilisim Teknolojileri Yazilim San. | tr | 9001 | 9030 | Linux | 0.4.5.7 | Merlin2 | 1 | B4285A497939D190739C976B947053D6CC0AE07C |

1 0

Re: [tor-relays] ISP (?????? ???????)
by Mark Murray 31 Mar '21

31 Mar '21

I used to run a couple of relays on their DEV1-S instances and never had any problems. They let you use the advertised bandwidth 24/7 without being throttled. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, March 31, 2021 8:26 AM, <tor-relays-request(a)lists.torproject.org> wrote: > Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > Today's Topics: > > 1. Re: ipv6 ORPort + DIRPort too ? (Petrusko) > 2. This is not me (Paul Templeton) > 3. Re: syn flood iptables rule (Toralf F?rster) > 4. Re: DirPortFrontPage file '.....' not found | Permission > denied (torix(a)protonmail.com) > > 5. ISP (?????? ???????) > 6. Re: Is OVH a safe vps provider to run an exit relay on? > (Volker Mink) > > > Message: 1 > Date: Tue, 30 Mar 2021 21:38:59 +0200 > From: Petrusko petrusko(a)riseup.net > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] ipv6 ORPort + DIRPort too ? > Message-ID: f943db9d-b3c9-e51b-03ea-ac3447f780cf(a)riseup.net > Content-Type: text/plain; charset="utf-8" > > Ouch, this config looks like not so cool... > I see on Metrics the ipv6 choosen by Tor process, is now on : > "Unreachable OR Addresses" > > I'll write the other solution you given previously... with > ORPort xxx.xxx.xxx.xxx:9001 > ORPort [xxxx:xxxx:xxx:x:xxxx:xxxx:xxxx:xxx]:9001 > > 30/03/2021 ? 20:07, Petrusko : > > > Ok ! > > So this only line will serve on both ipv4 and ipv6 together, ok thx ! Cool > > 30/03/2021 ? 15:51, lists(a)for-privacy.net : > > > > > ORPort 9001 > >

1 0

ISP
by Андрей Гвоздев 31 Mar '21

31 Mar '21

Did anyone run relays on Scaleway?

4 3

This is not me
by Paul Templeton 31 Mar '21

31 Mar '21

the relay with fingerprint B8D95BB1AAFB6F234EC50A100F46E4CC8E8E90FB (coffswifi5)is not me... coffswifi4 is mine so don't ask me to add as a family... Paul 137CF322859E400455E457DB920F65FFDD222CDF

2 1

Recent Postings
by manifoil 30 Mar '21

30 Mar '21

Hello fellow Tor Relay operators! Recent activity on this mailing list has given me a headache... Let me explain. I subscribed to this mailing list to keep up to speed with new technical developments, trouble shooting advice and security advisories. If there is a mailing list that covers this criteria, please let me know because that is where I want to be. This recent 'noise' about Mr Stallman is, in my opinion, unnecessary and unwarranted on this particular mailing list. It reminds me of a similar episode on this mailing list a while back where someone appeared to have a personal problem with someone who ran a hosting company - I nearly wrote something about that. My relay has been chugging away at home for many years and bandwidth assigned to the network has steadily increased as my home broadband capability has improved. I am happy that it contributes to Tor and might help people in genuine need - be it politically, racially, sexual orientation wise or as a whistle blower. Finally, I would like to thank the poster who highlighted the OpenSSL vulnerability - my relay was promptly updated. To quote someone else and because I like this persons' sigh-off: With respect, Rattus Norvegicus Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

This past week's most active discussion has forced my hand
by Isaac Grover, Aileron I.T. 30 Mar '21

30 Mar '21

Good morning from Wisconsin, Back in 2019, I was involved in a discussion on this list to seek out hosting providers friendly to Tor exit nodes so that the list on the Tor Project website could be updated and geographic and provider diversity could be improved. Because our twins were newborns at the time, the project took a back burner but I had built up the initial automation and templates for the contacts. Would there be any interest in reviving this project for the aforementioned reasons? Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. – “ Because #ProactiveIsBetter ” O: 715-377-0440, F:715-690-1029, W: www.aileronit.com

3 2

Tor [0.4.5.7] {Bridge} IPv4 not found
by Someone 30 Mar '21

30 Mar '21

Hey, I'm running Tor [0.4.5.7] on Ubuntu 20.04.2 LTS and started running my first bridge following the exact tutorials on the community guide for running bridge. However, the syslog says(resulting in non-reachability of the port.): Tor[6278]: Unable to find IPv4 address for ORPort 11120. You might want to specify IPv6Only to it or set an explicit address or set Address. Here's my torrc conf: BridgeRelay 1 ORPort 11120 IPv4Only ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:356 IPv4Only ExtORPort auto ContactInfo __REDACTED_FOR_PRIVACY__ Nickname dubridge Steps done: Saw the router configuration (IPv6 disabled in there). Thought maybe some issue with dynamic/static IP so configured DHCP ADDRESS RESERVATION to get a static IP. Followed a similar thread on this topic by a guy recently so wrote IPv4Only in front of both ORPort and obfs4 Thanks! Someone

2 2