Hi Georg,
First of all, thanks to all of you for the effort writing up the proposal!
I saw that email obfuscation was discussed but no solution was proposed. I
want to throw in some ideas about obfuscating the email centrally:
- Let's not publish cleartext email in any public descriptor, and
Hey John,
Perhaps one thing you can try in debugging is to run tcpdump on the server
in question, to check if it is indeed sending out a lot of port-scanning
packets. You can use the following command to filter for port 22 only. Make
sure to test with tor turned off as well.
"*sudo* *tcpdump -vv
Hi xmrk2,
As a fellow relay operator I think it might be helpful for me to add some
clarification to what you saw.
1. "comcast" the ISP didn't block or interfere with traffic to/from the
relay IP. (Thanks Jason for the clarification.)
However,
2. an average "comcast user" (with ISP-provided
@Enkidu
As an user of your filtering script, I want to first say thank you for
maintaining the script!
> The idea that all relays must be able to connect to other relays any time
and in any shape or form they choose can not exist in real world of DDoS
mitigation.
I totally agree, however I want
Hi Keifer,
AWS EC2 charges for egress traffic (although ingress is free). For Relays,
you will generally have about the same amount of ingress and egress
traffic. The free tier has 100G/month free. After that, you need to pay for
the "egress to internet" rate, which is "First 10 TB / Month, $0.09
Dear relay operators,
I recently upgraded one of my relays to Ubuntu 22.04 and now tor keeps
crashing. I debugged a little bit and saw the following error in the log.
It appears that it's due to seccomp not allowing "rseq" syscall, and
possibly related to the latest version of Glibc.
I
