I agree, maybe this open letter is better aimed at the security vendors
that include DAN's (non-exit) Tor relays list on a blocklist by default,
or without warning about potential impact to other legitimate services
(universities, libraries, shared hosting providers, hobbyist email, etc)
population.
Cheers and thanks for providing the lists, mpan.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Is there a way to be notified when a relay goes offline?
Hello,
If your relay is running as a systemd service, you may add any action
to ExecStopPost.⁽¹⁾ That includes sending an email or any other means of
notification.
Cheers
⁽¹⁾
In the past 24 hrs, I have been receiving complaints from my hosting provider
that they're receiving hundreds of abuse reports related to port scanning. I
have no clue why I'm all of the sudden receiving abuse reports when this
non-exit relay has been online for months without issues. In
1. Asking all relay operators to list their email addresses in the public relay list is
largely equivalent to asking them to invite tens of thousands of spam emails into their
inboxes and having to either ignore most of them or set up aggressive filtering rules
which can easily bounce
the ball. Alas. […]
Is there any data available that sheds light on why operators run
outdated versions, so the situation could be addressed not only
reactively, but also in a preventive manner?
mpan
OpenPGP_signature
Description: OpenPGP digital signature
: including people, who use that to
protect children. By doing so you may be placing yourself in the role of
a judge or — worse — trying to use the technology to introduce policing
based on your own beliefs.
Thanks for running a node, mpan
OpenPGP_signature
Description: OpenPGP digital signature
How would I continuously monitor the incoming traffic to my relay,
both what's supposed to be there and what isn't.
I’m don’t know, what do you mean by “supposed to be there and what
isn’t”, but in general you can use nyx⁽¹⁾ to monitor your Tor node.
If that’s for some research and
I have a question and I don't know were I have to look at. I am running
a relay (compiled from source) on Raspberry Pi OS Buster. Tor is runs
under the user "pi", so the tor logfile has also the user permission
(chown pi logfile).
Tor starts via crontab (@reboot) but after a reboot the user
I am hosting 3 VM's limited at 10Mbps all together. Each VM is limited
to 1Mbps via proxmox. I have noticed if i have these relays running it
kills a 10Gbps fiber optic line. All the way down to 50Mbps or worse
depending on what the time of day. Any idea what i can try? I noticed
this happen
Today I received a message from PayPal that paying for Tor relay server leases
was a direct violation of my usage agreement. I have been paying off-shore VPS
hosts for my Tor server leases with PayPal for at least ten years. Very
interesting that they act now.
How comes they determined what
> It's even public! See:
> https://lists.torproject.org/pipermail/tor-consensus-health/2020-November/011602.html
>
> Those nodes triggered an alarm on our side for being a potential sybil
> attack. So, we kicked them out.
Isn’t there a time correlation with the “Possible compression bomb;
A similar observation on a middle+guard (times in UTC). Nothing since
then, no other issues observed:
--
Nov 02 04:11:12: Possible compression bomb; abandoning stream.
Nov 02 04:12:09: Possible zlib bomb; abandoning stream.
Nov 02
> I'm also fine with making it optional in the upcoming version 2
> to lower the barrier for adoption.
My goal is not to make contact info optional. I do understand value of
such information. The problem is choosing one specific means of
communication as mandatory, instead of letting the
or poorly
designed websites), but are those really the argument for making this
specific information trivially harvestable?
As long as this is optional, it’s not a huge problem. But I do not
believe in ignoring stuff simply because temporarily it does not affect
me personally.
mpan
signature.asc
> I see the Authority Nodes are located only in North America and Europe.
> I would like to contribute to the TOR network as much as possible. I am
> currently running a node and I would like to make it an Authority Node as
> well.
> I am from Brazil and I believe it would possibly be a good idea
> I keep getting NYX_NOTICEs about "Relay unresponsive". They happen every
> few hours, and last for minutes or sometimes a couple of hours before I get
> a "relay resumed" message.
As Damian Johnson has said, it is hard to guess the cause without more
clues. But keep in mind that 2MB/s with 7k
> TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies.
> Check
> SNMP counters.
> what it can mean? also my 2 relays go offline for a few hours once a day,
> then
> are restored.
The TCP protocol builds a new connection by the client sending a SYN
packet to the server,
> Is a really with a dynamic IP address useful at all?
I’m running a node like that for over 5 years. Currently it is a guard
too. The IP address is relatively stable and the major interruptions are
due to kernel/tor upgrades or modem losing connection without the
address change. Even after
19 matches
Mail list logo
