Re: [tor-relays] Updating tor issue

On Freitag, 3. Mai 2024 18:17:41 CEST Keifer Bly wrote: > System is up to date, I run apt-get update regularly. Did you even only read 2 sentences from the link? Buster is EOL and will be completely archived in a few weeks. > > https://www.debian.org/releases/buster/ Debian is 2 releases ahead!

Re: [tor-relays] Updating tor issue

On Freitag, 3. Mai 2024 17:00:44 CEST Keifer Bly wrote: > What is the correct format for adding tor as a trusted source? A not outdated system. ¹AFAIK obfs4proxy for buster (oldoldstable) has had a security hole for a long time and you are putting your users at risk! > deb-src

Re: [tor-relays] Backdoor in upstream xz/liblzma leading to ssh server compromise

On Samstag, 30. März 2024 01:02:54 CEST he...@relaymagic.org via tor-relays wrote: > Just wanted to bring this to everyone’s attention if you hadn’t seen it > already. Developer discovered a backdoor in xz-utils > https://www.openwall.com/lists/oss-security/2024/03/29/4 Pretty

Re: [tor-relays] Tor is not upgrading via apt from deb.torproject.org

On Montag, 19. Februar 2024 00:27:04 CET s7r wrote: > Peter Palfrader wrote: > > > > > our gitlab-ci has not managed to build a tor nightly in ages. > > > > > Thank you for stepping in! No better person to ask :) > > The upgrade via apt from nightly used to work every time, back since >

Re: [tor-relays] Problem with relay and ovh??

On Sonntag, 18. Februar 2024 01:42:30 CET Keifer Bly wrote: Every few months the same question with the same log messages :-( > 00:36:35.000 [warn] You are running Tor as root. You don't need to, and you > probably shouldn't. ^^Still not fixed. > Feb 18 00:36:34.640 [notice] Opening OR listener

Re: [tor-relays] Tor is not upgrading via apt from deb.torproject.org

On Donnerstag, 15. Februar 2024 13:54:51 CET s7r wrote: > I have recently found something interesting on my relays. On all relays > and clients actually. > > As always I am using Debian and apt to get Tor from deb.torproject.org > tor-nightly-main-bullseye main (for example). I also have the

Re: [tor-relays] Relay in AT marked as DE in metrics

On Mittwoch, 31. Januar 2024 19:50:13 CET Carlo P. via tor-relays wrote: > I have a relay on 152.53.17.183 / 2a0a:4cc0:1:1333::beef which is listed as > "German" in metrics.torproject.org, but actually it is in Austria Was just a topic here recently:

Re: [tor-relays] A new kind of attack?

On Montag, 15. Januar 2024 23:19:37 CET Chris Enkidu-6 wrote: > I've noticed a new kind of possible attack on some of my relays, as > early as Dec.23 which causes huge spikes of outbound traffic > > I have included charts and excerpts from the log in my post in Tor forum > at below link: > >

Re: [tor-relays] Dutch Relays

On Dienstag, 19. Dezember 2023 16:23:27 CET Jordan Savoca via tor-relays wrote: > On 12/18/23 6:59 AM, ab...@relayon.org 2023 wrote: > > These are complete and utter shit. > > > > avoid like the plague! > > > > nifty ;-) You've landed in the sun again, I envy you. > Oh? I'm curious to hear

Re: [tor-relays] Metrics

So you don't have to dig through the logs: (as root or sudo) ~# cat /var/lib/tor/pt_state/obfs4_bridgeline.txt ~# cat /var/lib/tor/fingerprint or with multiple instances: ~# cat /var/lib/tor-instances/NN/pt_state/obfs4_bridgeline.txt -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and

Re: [tor-relays] WebTunnel: What ASNs/networks work best?

On Montag, 14. August 2023 16:40:09 CEST Jordan Hillis wrote: > Can I get a copy of the webtunnel-bridge Docker image and > documentation? Thanks https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtunnel#server-setup More info in the last (June 24) Tor Relay Operator Meetup

Re: [tor-relays] Middle relay IP blocking

On Dienstag, 8. August 2023 00:30:38 CEST Gary C. New via tor-relays wrote: > In addition to network diversity, there is the fact that most individuals > find it necessary to run an at Home internet connection 24 x 7 x 365. So... > Other than for the reasons inspired by the subject of this post,

Re: [tor-relays] Middle relay IP blocking

On Montag, 7. August 2023 22:28:32 CEST s7r wrote: > While all the above is true, a thing to remember is to make sure we > don't end up all renting too many VPS'es or dedicated servers in the > same places / same AS numbers - we need network diversity, Especially at the exits, which

Re: [tor-relays] Middle relay IP blocking

On Samstag, 5. August 2023 08:40:42 CEST Marco Predicatori wrote: > secureh...@gmail.com wrote on 8/4/23 01:46: > > I tried reporting a similar issue a few months ago (post wasn’t approved > > by > > moderator). I was running a relay from my home ISP. After a short while > > certain websites

Re: [tor-relays] Help Turkmens to bypass Internet censorship: run an obfs4 bridge!

On Dienstag, 1. August 2023 23:22:12 CEST Gary C. New via tor-relays wrote: > The failure logs and metrics are going to be confusing to new obfsbridge > operators. I suppose documenting this on the obfsbridge setup page will > have to be sufficient in the interim; along, with pointing them to the

Re: [tor-relays] Help Turkmens to bypass Internet censorship: run an obfs4 bridge!

On Dienstag, 1. August 2023 23:22:12 CEST Gary C. New via tor-relays wrote: > On Tuesday, August 1, 2023, 10:54:40 AM MDT, wrote: > > On Montag, 31. Juli 2023 23:06:54 CEST Gary C. New via tor-relays wrote: > >> Please let me know, if you are able to get the OBFS4 > >> bridge working without

Re: [tor-relays] Help Turkmens to bypass Internet censorship: run an obfs4 bridge!

On Dienstag, 1. August 2023 19:21:08 CEST Toralf Förster wrote: > On 8/1/23 18:54, li...@for-privacy.net wrote: > > > == Announcements == > > rdsys is ignoring the running flag now :) > > * To hide your bridge's ORPort: > > ORPort 127.0.0.1:auto > > AssumeReachable 1 > > > I do assume I can

Re: [tor-relays] Help Turkmens to bypass Internet censorship: run an obfs4 bridge!

On Montag, 31. Juli 2023 23:06:54 CEST Gary C. New via tor-relays wrote: > Please let me know, if you are able to get the OBFS4 > bridge working without exposing the ORPort. Respectfully, Yes, that's working All Info about this new feature: Anti-censorship team meeting notes, 2023-06-29

Re: [tor-relays] Help Turkmens to bypass Internet censorship: run an obfs4 bridge!

On Montag, 31. Juli 2023 00:55:15 CEST Gary C. New via tor-relays wrote: > On Sunday, July 30, 2023, 3:30:55 PM MDT, li...@for-privacy.net wrote: > > I don't know if I should ignore that or better configure it that >way: > > ORPort 127.0.0.1:8443 NoListen > > ORPort 8443 NoAdvertise > > ORPort

Re: [tor-relays] Help Turkmens to bypass Internet censorship: run an obfs4 bridge!

On Freitag, 21. Juli 2023 18:07:35 CEST gus wrote: > New update: In the last few weeks, internal political conflicts and > other events[1] in Turkmenistan have led to another wave of censorship > on Tor and anti-censorship tools. Tor bridges have been one of the few > free alternatives for people

Re: [tor-relays] Wrong "first seen" flag for bridges at metrics.torproject.org

On Montag, 17. Juli 2023 20:12:34 CEST telekobold wrote: > I have an issue regarding the "first seen" flag at > metrics.torproject.org: It is definitely wrong for my two bridges - both > dates are much too close in the past. > Has anyone observed similar behavior for its relay? (I found it >

Re: [tor-relays] (EVENT) Tor Relay Operator Meetup - June 24, 2023 @ 18.00 UTC

On Samstag, 24. Juni 2023 18:03:47 CEST li...@for-privacy.net wrote: > On Dienstag, 20. Juni 2023 23:01:23 CEST gus wrote: > > Just a friendly reminder that the Relay Operator meetup will happen this > > Saturday, June 24 at 18 UTC. > > > > ## Agenda > > > > 1. Announcements > > > > - Tor

Re: [tor-relays] (EVENT) Tor Relay Operator Meetup - June 24, 2023 @ 18.00 UTC

On Dienstag, 20. Juni 2023 23:01:23 CEST gus wrote: > Just a friendly reminder that the Relay Operator meetup will happen this > Saturday, June 24 at 18 UTC. > > ## Agenda > > 1. Announcements > - Tor Relay Operators meetup @ CCCamp 2023! > - More unrestricted snowflake proxies are needed >

Re: [tor-relays] Comcast blocks ALL traffic with tor relays

On Sonntag, 11. Juni 2023 13:46:06 CEST xmrk2 via tor-relays wrote: > Background: I am running a lightning node, lightning is a layer 2 protocol > to scale Bitcoin. Lightning nodes need to be connected to each other > ideally 24/7. I was contacted by the operator of another Lightning node, >

Re: [tor-relays] «Possible compression bomb» from Authority?

On Samstag, 3. Juni 2023 18:18:46 CEST Tschador wrote: > today I found this warning in the log of my relay > Jun 03 04:04:33.000 [warn] Possible compression bomb; abandoning stream. > What does this mean? A simple log message that the tord didn't unpack a Zip Bomp. DDOS protection in the Tor

Re: [tor-relays] Configuring key expiration warning messages?

On Freitag, 19. Mai 2023 13:55:10 CEST telekobold wrote: > If there isn't such an option, does anyone happen to have a script > ready for this (before I start trying to implement something like this > myself)? Yes in toralf's /torutils: https://github.com/toralf/torutils/blob/main/key-expires.py

Re: [tor-relays] new exit relay

On Mittwoch, 12. April 2023 17:14:46 CEST Linux-Hus Oni via tor-relays wrote: > hi again, actulay i have made my exit to a bridge, so my bandwith is not so > big for an exit. it is automatically removed from the metrics ? Get a new IP, you put users at risk! It doesn't matter, even if your relay

Re: [tor-relays] Police request regarding relay

On Mittwoch, 12. April 2023 18:28:09 CEST tor-opera...@urdn.com.ua wrote: > Finn wrote: > > The weird thing is, that the relay in question is only a relay and > > not an exit node since its creation (185.241.208.179) > > (https://nusenu.github.io/OrNetStats/w/relay/B67C7039B04487854129A66B16F5E >

Re: [tor-relays] Police request regarding relay

On Dienstag, 11. April 2023 14:09:15 CEST Finn wrote: > Hello everyone, > > We are hosting multiple relays under our AS 210558 and received an email > from a local police station in Germany requesting user data, nothing > unusual. Nothing unusual? I had a house search because of exits but never a

Re: [tor-relays] Selecting Exit Addresses

On Freitag, 31. März 2023 16:56:16 CEST denny.obre...@a-n-o-n-y-m-e.net wrote: > The second IP is still in "Exit Addresses" with the new configuration ... > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B > 5881B7D4C97C I don't understand that now either. I have at

Re: [tor-relays] Selecting Exit Addresses

Hi denny, > Hi, > > I just activated my first exit relay. ( > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B > 5881B7D4C97C ) I had the following in my torrc (plus some other things): I've answered the rest to the list. If you want to enable IPv6 at Frantech/BuyVM:

Re: [tor-relays] Selecting Exit Addresses

On Freitag, 31. März 2023 01:26:42 CEST denny.obre...@a-n-o-n-y-m-e.net wrote: > Hi, > > I just activated my first exit relay. ( > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B > 5881B7D4C97C ) I had the following in my torrc (plus some other things): Don't forget

Re: [tor-relays] AirTor/ATOR continues to pester Tor relay operators, promising donations

On Freitag, 17. März 2023 17:25:10 CET Bauruine wrote: > ... but I'll > just keep "mining" consensus weight. Because you don't need a modified > version of Tor and you don't need the blockchain for that. Just download > the consensus and look at the consensus weight and you have your proof > of

Re: [tor-relays] Confusing bridge signs...

On Sonntag, 12. März 2023 04:45:21 CET Keifer Bly wrote: > I do not use any scripts to start tor, I just type tor to start the process > on debian. That's where your problems begin. You start a 2nd tor process as root that doesn't take the default configs from:

Re: [tor-relays] Relay requirements

On Dienstag, 7. März 2023 13:31:13 CET mail--- via tor-relays wrote: > Running a few relays on 1-2 CPU cores with limited RAM is > fine, but just keep an eye on it and don't run other memory intensive stuff > on the server (like DNS query caching, which can take quite some RAM as > well). A

Re: [tor-relays] Confusing bridge signs...

On Mittwoch, 8. März 2023 18:13:01 CET Keifer Bly wrote: > Strangely, nothing whatsoever is being written to the notices.log file, > upon checking it it is completely empty, nothing there. That can't be, please post: ~# ls -A /var/log/tor In general, everything is always written to

Re: [tor-relays] Relay requirements

On Dienstag, 7. März 2023 03:00:49 CET Sydney wrote: > Newbie here. No network experience but already running 2 TOR instances: 1 > TOR service + 1 bridge. Never mix different relay types under one IP. > I would like to "upgrade" to TOR relays but have a few questions relating to > hardware needs.

[tor-relays] D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11 is spoofing my contact info

This is _not_ my relay: https://metrics.torproject.org/rs.html#details/D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11 https://nusenu.github.io/OrNetStats/w/relay/D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11.html -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!

Re: [tor-relays] Confusing bridge signs...

On Samstag, 4. März 2023 02:09:19 CET Keifer Bly wrote: > Wheres the pastebin page? Thanks. $websearch pastebin https://paste.debian.net/ https://paste.systemli.org/ https://pastebin.mozilla.org/ ... -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!

Re: [tor-relays] Confusing bridge signs...

On Dienstag, 28. Februar 2023 19:02:38 CET Keifer Bly wrote: > Yep, and after that the same still happens, it is still going offline In the syslog is why tor aborts. To help you, you should post your logs to a pastbin page. From the start of the tor daemon until it goes offline. -- ╰_╯ Ciao

Re: [tor-relays] Confusing bridge signs...

On Freitag, 24. Februar 2023 04:11:27 CET Keifer Bly wrote: > Yes, the limit is 50GB per month, but for some reason the distribution > mechanism is not updating and the bridge keeps going offline despite the > new torrc. What comes to my mind without logs (& your 'killall -HUP' of a systemd

Re: [tor-relays] Frantech (was Re: Confusing bridge signs)

On Freitag, 24. Februar 2023 14:19:13 CET Jeff Teitel wrote: > On Fri, Feb 24, 2023 at 12:10 AM Marco wrote: > > Yes, Frantech should actually be avoided. But in Miami there are few Tor > > relays. A SLICE 512 for $2.00/m or $20.00/y is sufficient for a bridge. > >

Re: [tor-relays] Confusing bridge signs...

On Donnerstag, 23. Februar 2023 13:43:29 CET gus wrote: > AccountingStart day 12:00 > AccountingMax 50 GB > > > Example: Let's say you want to allow 50 GB of traffic every day in each > direction and the accounting should reset at noon each day: Hi Gus, I think Keifer meant the 5GB limit or

Re: [tor-relays] Confusing bridge signs...

On Samstag, 18. Februar 2023 18:56:00 CET Keifer Bly wrote: > Ok. Here is the torrc file: > > GNU nano 3.2 /etc/tor/torrc > > > Nickname gbridge > ORPort 443 > SocksPort 0 > BridgeRelay 1 > PublishServerDescriptor bridge > ServerTransportPlugin obfs4 exec

Re: [tor-relays] Questions about Tor consensus weight & swag

On Samstag, 18. Februar 2023 18:26:55 CET shruub via tor-relays wrote: > > RelayBandwidthBurst > > One question, what actually is the burst? Haven't found anything online > nor in man. > man torrc: RelayBandwidthBurst N bytes|KBytes|MBytes|GBytes|TBytes|KBits|MBits|GBits| TBits If not 0, limit

Re: [tor-relays] Confusing bridge signs...

On Donnerstag, 16. Februar 2023 06:15:02 CET Keifer Bly wrote: > So my bridge at > https://metrics.torproject.org/rs.html#details/4D6E3CA2110FC36D3106C86940A1D > 4C8C91923AB says it has “none “, Well, then you have configured BridgeDistribution (Default: any) to none. > though the torrc file has

Re: [tor-relays] Questions about 4 Relays per IP and the ddos mitigation scripts

On Mittwoch, 8. Februar 2023 00:07:22 CET nusenu wrote: > I don't think relays should silently drop > other relays packets without first trying: > - to confirm that accepting that IP would render the relay (mostly) unusable > (by first running in a mode that accepts relay IPs) - to understand the

Re: [tor-relays] backports obfs4proxy unsigned

On Freitag, 13. Januar 2023 18:18:21 CET tor wrote: > the backport of obfs4proxy seems to be unsigned Backports has been an official Debian service since ~2010 and the packages are signed with the debian-archive-keyring. > I needed to use: > deb [trusted=yes] http://deb.debian.org/debian

Re: [tor-relays] obfs4proxy ubuntu jammy arm64

On Freitag, 13. Januar 2023 18:05:19 CET Martin wrote: > Just out of curiosity, when will this version be implemented in the TOR > repositories? As far as I can tell, not in the near future. (this version and also future versions) Obfs4proxy has too many dependencies and is packed better (as

Re: [tor-relays] obfs4proxy ubuntu jammy arm64

On Freitag, 13. Januar 2023 16:09:33 CET li...@for-privacy.net wrote: > > Where do I get version 14? > > From backports: > https://lists.torproject.org/pipermail/tor-relays/2023-January/020976.html A little help for backports that I've already posted:

Re: [tor-relays] obfs4proxy ubuntu jammy arm64

On Freitag, 13. Januar 2023 15:40:50 CET tor wrote: > Hello > > I'm running ubuntu, jammy, arm64. > > When I run: > > machine@user_1:~$ sudo apt-get install obfs4proxy > Reading package lists... Done > Building dependency tree... Done > Reading state information..

Re: [tor-relays] I think I'm available 24/7

On Dienstag, 3. Januar 2023 00:46:30 CET fastliftednloud via tor-relays wrote: > I'm game to do my part and operate a relay, something simple for a > technologically simple guy, like a guard or middle relay. You can help directly with a Firefox plugin: Snowflake proxy. Has the same function as

Re: [tor-relays] inet_csk_bind_conflict

On Freitag, 2. Dezember 2022 16:30:48 CET Chris wrote: > As I'm sure you've already gathered, your system is maxing out trying to > deal with all the connection requests. When inet_csk_get_port is called > and the port is found to be occupied then inet_csk_bind_conflict is > called to resolve the

Re: [tor-relays] Performance issues/DoS from outgoing Exit connections

On Samstag, 22. Oktober 2022 22:40:38 CEST Toralf Förster wrote: > On 10/21/22 22:09, Alexander Dietrich wrote: > > This is still experimental, so if you decide to give the script a try, > > please keep an eye on it. > > IMO a "reload tor" is fully sufficient and should be preferrred over >

Re: [tor-relays] bridge down

On Mittwoch, 19. Oktober 2022 01:12:37 CEST Anonforpeace via tor-relays wrote: > I have set the static NAT and forwarded the port. On your router? > Here is what I get. :-( Logs and configs are more readable on a pastbin page. E.g. paste.debian.net or privatebin.deblan.org >

Re: [tor-relays] knock knock, police is here

On Samstag, 10. September 2022 14:37:18 CEST volker.m...@gmx.de wrote: > On Tuesday morning police knocked on my door, performing a full house > search. For me the bastards were 2 weeks ago at 6:05 am :-( Until now I was not told which IP's and when it was. > Unfortunately they found some dope

Re: [tor-relays] Relays spamming my OR port

On Donnerstag, 18. August 2022 19:47:45 CEST Toralf Förster wrote: > On 8/18/22 18:19, li...@for-privacy.net wrote: > > kantorkel's Article10 relays have more than 100 connections per IP to me. > > Those IPs mostly close with an error: > > $> grep -h " 185.220.101.*" /tmp/orstatus.*9051 | awk '{

Re: [tor-relays] Relays spamming my OR port

On Donnerstag, 18. August 2022 19:25:54 CEST Toralf Förster wrote: > On 8/18/22 18:19, li...@for-privacy.net wrote: > > 10, 20 or more users can have set up the circuits using the same relays. > > kantorkel's Article10 relays have more than 100 connections per IP to me. > > IMO there'se no 1:1

Re: [tor-relays] Relays spamming my OR port

On Donnerstag, 18. August 2022 19:22:44 CEST Toralf Förster wrote: > On 8/18/22 18:19, li...@for-privacy.net wrote: > >> D767979FE4C99D310A46EC49037E9FE7E3F64E9D is a particularly frequent > >> naughty boy. > > > > ;-) It is very, very unlikely that there is a naughty relay in AS680. > > That

Re: [tor-relays] Relays spamming my OR port

On Mittwoch, 17. August 2022 19:31:48 CEST Logforme wrote: > I run the relay 8F6A78B1EA917F2BF221E87D14361C050A70CCC3 > > I have tried to mitigate the current DoS by implemented connection > limits in my iptables using Toralf's template: More than 25 connection > during 10 mins and you end up on

Re: [tor-relays] easy way to test my exit policy

On Dienstag, 16. August 2022 16:36:52 CEST Tom Yates wrote: > i've been grumbled at in a way that makes me want to validate my exit > policy before dismissing the grumble. I don't know exactly what you want to test there. You can see what you have open on tor metrics. No IP/nftables for outgoing

Re: [tor-relays] Have you experienced DDoS?

On Montag, 15. August 2022 16:59:47 CEST abuse compartment wrote: > Daily. “Best” day was around 320 Uptime Robot mails after a good night > sleep. :-) Because you always write such nice replies to abuse mails. > > Was somebody else also subject to DDoS today? Um, this has been a high topic in

Re: [tor-relays] Setting a bridge to automatically change IP adresses

On Mittwoch, 10. August 2022 02:02:36 CEST Keifer Bly wrote: > Thanks. But it just seems that would make it easier to have "new" bridges, > as all of the in use ones will eventually be blocked? So either you have dozens of unused IP's on your server then do as I do, let the bridges run, _now_

[tor-relays] OT: cheap bar metal machines

HiHo, because I switched to my own servers in colocation, I canceled some rented ones. These were all Supermicro blades 8c Opteron, 2 hd's and BMC (IPMI). https://www.supermicro.com/Aplus/system/3U/3012/AS-3012MA-H12TRF.cfm SSD: Samsung (840,850,860) EVO, SATA: WD Enterprice (WDC_WD1003FBYX)

Re: [tor-relays] Overload (dropped ntor) due to DDoS??

On Friday, August 5, 2022 1:11:27 AM CEST s7r wrote: > Richard Menedetter wrote: > > I have a non exit relay running on a root server (4 AMD Epyc cores, 8 GB > > RAM, 2.5 GBit/s Ethernet) I have limited tor to numcpus 2, Why? Do you have other services on the server? Otherwise, omit num CPU. Let

Re: [tor-relays] Metrics shows my relay down. But it's not.

On Freitag, 24. Juni 2022 21:11:30 CEST Eddie wrote: > The metrics is showing one of my relays > (40D13096BBD11AF198CE61DEE4EAECCE5472F2E7) as down for around the last 3 > hours. Logging in to it, I see everything running normally. > > This server has also lost a bunch of flags for no apparent

Re: [tor-relays] Identifying a relay

On Wednesday, June 15, 2022 8:17:54 PM CEST Eddie wrote: > Have a question about how a server I connect to can tell I am running a > guard/middle relay. All I can think of is that they check the published > list of tor nodes against the IP. Unfortunately, many people do this, often because they

Re: [tor-relays] EXPKEYSIG when running 'apt update'

On Monday, June 13, 2022 7:11:32 PM CEST Imre Jonk wrote: > Hi tor-relays, > > I'm getting this error when running 'apt update': mee too ;-) > Err:4 https://deb.torproject.org/torproject.org bullseye InRelease > The following signatures were invalid: EXPKEYSIG 74A941BA219EC810 >

Re: [tor-relays] [New Initiative] Tor Weather: Improving the Tor Weather

On Wednesday, June 8, 2022 3:39:55 AM CEST Sarthik Gupta wrote: > The tor-weather service will offer a plethora of notifications options for > the relays. If you program something new, see if you can use the old code: https://github.com/thingless/torweather As far as I know, nusenu is also

Re: [tor-relays] My current node setup

On Tuesday, June 7, 2022 5:25:18 PM CEST Nyasaki Server wrote: > Hi to all new ppl that may have joined after the sysadmin101 workshop. Yes, that was a fun event ;-) > Exit-Node: > Archlinux with tor Awesome, Arch and Gentoo relais are rare *BSD even less and unfortunately nobody talks about

Re: [tor-relays] bridge issue

On Saturday, June 4, 2022 1:58:29 AM CEST potlatch via tor-relays wrote: > Hello, > I have a bridge [1] that doesn't have any keys in /var/lib/tor/keys! How is > that possible and how do I fix the problem? > > potlatch > > [1] FB45183DD82D572CA2B2641C1AB0EB0D8CE7B858 > > Sent with [Proton

Re: [tor-relays] Update on tor issue on my debian

On Friday, June 3, 2022 10:51:07 PM CEST Keifer Bly wrote: > Nevermind, I got it. > > Now there are two other things I wanted to ask about, is there a way I can > set tor to automatically update over time? Also, my bridge at >

Re: [tor-relays] New OrNetStats Section: Largest Bridge Operators

On Sunday, May 29, 2022 6:25:02 PM CEST nusenu wrote: > AROI support for bridges > > You can also protect your bridge ContactInfo against spoofing now. > The same fields as for relays apply. If you have setup your AROI [1] on your > relays already you can simply copy the ContactInfo to your

Re: [tor-relays] Update on tor issue on my debian

On Wednesday, June 1, 2022 7:25:44 PM CEST Keifer Bly wrote: > So upon trying all of the mentioned commands, my tor installation still > encounters an error when trying to update. Attached is a photo of my > sources.list.debian.templ and sources.list. When trying to update the > returned error

[tor-relays] Bridge operators contact addresses online ;-)

I happened to see that Bridge operators contact addresses can now be displayed. https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/40017 Demo on Tor Metrics for all 'bauruine' and 'ForPrivacyNET' bridges. Thanks to the torproject team. -- ╰_╯ Ciao Marco! Debian

Re: [tor-relays] Sanity check on NumCPUs

On Thursday, May 26, 2022 2:31:41 AM CEST Thoughts wrote: > For a non-exit relay, is "NumCPUs 2" still the recommended maximum? > Running on a quad core and recently saw a message indicating I had > insufficient CPU power to support the desired number of connections... > NumCPU I always let the

Re: [tor-relays] [Event] Relay Operators Meetup - May 21, 2022 @ 1900 UTC

On Monday, May 23, 2022 6:53:13 PM CEST Vasilis The Pikachu via tor-relays wrote: > Are the notes for this meeting available? I was not able to make it but > i would like to read up on what was talked about > The pads are always set to 'keep'. That means at Riseup = 1 year/365 days. > >> We're

Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory

deb.debian.org/debian buster-updates InRelease > Temporary failure resolving 'deb.debian.org' > Reading package lists... Done > Building dependency tree > Reading state information... Done > 18 packages can be upgraded. Run 'apt list --upgradable' to see them. > W: Failed to fet

Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory

pdate-ca-certificates'. -- Forwarded Message -- Subject: Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory Date: Donnerstag, 5. Mai 2022, 15:09:07 CEST From: ben To: tor-relays CC: lists > Simply displays a message "

Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory

On Saturday, May 7, 2022 6:50:43 PM CEST Keifer Bly wrote: > Ok will try these things. Does that it's an ovh debain have anything to do > with it? Hosted by them and they may frown on tor. No, there are a lot (actually too many) Tor relays at OVH.

Re: [tor-relays] Ext Relay Operators: Please Upgrade to 0.4.7.7!

On Tuesday, May 10, 2022 4:55:57 PM CEST Ladar Levison via tor-relays wrote: > Anyone know when the EPEL TOR packages will updated? The EL 8 repos only > offer 0.4.5.11. EL 9 is only a little newer with RPMs for TOR 0.4.6.8. > Fedora 35 and 36 (with the latter launching today) have only been >

Re: [tor-relays] Relay Throttling

On Friday, May 6, 2022 2:39:09 PM CEST trinity pointard wrote: > Hi, > > There are two main mechanisms to limit relays bandwidth usage. > The first is by setting RelayBandwidthRate and RelayBandwidthBurst to limit > the average and peak bandwidth usage of your bridge. > The second is by setting

Re: [tor-relays] Tor Exit: Complaints of IP being used for "spam" despite exit policy

On Thursday, May 5, 2022 3:57:02 PM CEST The Doctor wrote: > --- Original Message --- > > On Wednesday, May 4th, 2022 at 11:16, Neel Chauhan wrote: > > If you need to send emails, you could: > > > > a. use Sendgrid or Mailgun or whatever to send emails if they don't > > block exit IPs

Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory

On Thursday, May 5, 2022 5:17:23 AM CEST Keifer Bly wrote: > Thank you. But running wget -qO- > https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E88 > 6DDD89.asc > > gpg --dearmor | tee /usr/share/keyrings/tor-archive-keyring.gpg >/dev/null Maybe copy paste error. It must

Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory

On Thursday, May 5, 2022 2:29:30 AM CEST Keifer Bly wrote: > Ok. I have tried different things. And the same is still happening: > > sources.list file: > > ## Note, this file is written by cloud-init on first boot of an instance > ## modifications made here will not survive a re-bundle. > ## if

Re: [tor-relays] Ext Relay Operators: Please Upgrade to 0.4.7.7!

On Wednesday, May 4, 2022 11:31:05 PM CEST Mike Perry wrote: > Tor 0.4.7.7-stable contains a very important performance improvement, > called Congestion Control. > > You can read more about this improvement here: > https://blog.torproject.org/congestion-contrl-047/ > > The TL;DR is that users of

Re: [tor-relays] Tor Exit: Complaints of IP being used for "spam" despite exit policy

On Tuesday, May 3, 2022 8:42:20 PM CEST Neel Chauhan wrote: > A day or two ago, my Tor exit host, Psychz Networks, has sent me > complaints about my IPs being used to send "spam" despite me having > blocked Port 25 (and 465/587) in the exit policy. > > Psychz threatened to block Port 25 even

Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory

On Tuesday, May 3, 2022 7:10:00 PM CEST Keifer Bly wrote: > I am not sure how to get rid of the trusty / ubuntu packages? You just have to write 'buster' instead of 'trusty'. Either in /etc/apt/ sources.list or you have created the file /etc/apt/sources.list.d/tor.list? > I simply followed the

Re: [tor-relays] Debian is not allowing tor to update despite it being listed as a trusted respritory

On Tuesday, May 3, 2022 7:31:46 AM CEST Keifer Bly wrote: > So I am running a tor relay on Debian, but no matter what when updating tor > there is an “updating from such a respiritpry can’t be done securely and is > therefore disabled by default”. Here is the log > > In addition to the

Re: [tor-relays] Bridge Distribution Mechanism none

On Wednesday, April 20, 2022 10:22:54 AM CEST Ross Camm wrote: > I have no error from Apparmor and I dont believe obfs4 proxy is the issue > as I have obfs4 installed and confirmed running > > dpkg -l | grep obfs4 > ii obfs4proxy 0.0.7-4 > > ps ax | grep obfs4 > 5501 ? Sl 0:01

Re: [tor-relays] Bridge Distribution Mechanism none

On Tuesday, April 19, 2022 2:28:01 PM CEST 55578 via tor-relays wrote: > Probably because obfs4 is not installed or not running properly. Get the obfs4proxy package from backports. Outdated obfs bridges are rejected AFAIK. https://lists.torproject.org/pipermail/tor-relays/2022-March/020447.html

Re: [tor-relays] Relay question

On Sunday, April 10, 2022 2:04:02 AM CEST onion...@riseup.net wrote: > > 30 new exits at Frantec. Did you follow the AUP and send Francisco a > > ticket > > _beforehand_? Reverse DNS! Exit policy Port: 465, 587! > > https://buyvm.net/acceptable-use-policy/ > > No, we did not pay attention to

Re: [tor-relays] Relay question

On Saturday, April 9, 2022 9:36:40 AM CEST onion...@riseup.net wrote: > Hello, I have a question for other operators of the Tor. I started the > nodes recently. On yui.cat status is displayed as offline > (https://yui.cat/family/F81C34435CA08B81105B3C77CF29EE7824652BFB/, >

Re: [tor-relays] Next Tor Relay Operator Meetup - April 2 @ 1900 UTC

On Tuesday, April 5, 2022 5:11:05 AM CEST gus wrote: > Here is our meetup notes. > > cheers, > Gus Yes, as always, thank you > ## Tor Relay Operator - April 02, 2022 > > * Performance tweaks for high bandwidth / multi instance servers, > [server confi templates - >

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

On Monday, March 14, 2022 8:46:23 PM CEST Christian Pietsch wrote: > I almost put the netcologne mirror into a blog post I co-wrote > – but then I noticed > that the download links do not work. The nice admin from NetCologne fixed the links. There is

Re: [tor-relays] update obfs4proxy if you run a bridge

On Wednesday, March 23, 2022 6:08:10 PM CET Toralf Förster wrote: > On 3/21/22 18:45, meskio wrote: > > > Thank you for running bridges, > > let me know if you need any help upgrading it. > > > I'm not really familar with Debian and do wonder, what line I have to > add to

Re: [tor-relays] What is the current method of submitting Tor-friendly ISPs for consideration?

On Thursday, March 17, 2022 9:12:35 PM CET Isaac Grover, Aileron I.T. wrote: > Following up on a previous post to this list, I started contacting AS > administrators in bulk and currently have five ISPs in unique ASs who state > they can accommodate Tor exit nodes. Great, thanks for the effort.

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

On Tuesday, March 15, 2022 12:02:45 AM CET li...@for-privacy.net wrote: > Shame on me, I didn't test the downloads. Only the Android binaries can be > downloaded. I will write to the admins and ask them to offer the files for > download. Maybe someone has hints for NetCologne mirror admin here:

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

On Monday, March 14, 2022 8:46:23 PM CET Christian Pietsch wrote: > I almost put the netcologne mirror into a blog post I co-wrote > – but then I noticed > that the download links do not work. For example, >

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

On Monday, March 14, 2022 9:19:41 AM CET Georg Koppen wrote: > > Pad notes will be posted after the meeting. > > > Here they come. Thanx a lot! > * Censorship situation in Russia: > > Since Dec 2021, the censorship department in Russia started to block > parts of the Tor network. It's not

  1   2   3   >