This would help us to add some more meaning to that metric again:
https://gitlab.torproject.org/tpo/core/tor/-/issues/40934
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello,
today we saw yet another outbound flooding affecting our exit relays
and we were eager to see the effect of
https://gitlab.torproject.org/tpo/core/tor/-/issues/40736
but we did not see any
and according to metric
tor_relay_dos_total{type="stream_rejected"}
the protection did not trigger.
According to the logs this feature is currently disabled.
We will enable this protection on our exits via torrc settings.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello,
is the upstream C tor client implementation (in git main) aware of the
DoSStreamCreation consensus parameters and defaults thresholds and
respects them to avoid triggering these exit relay defenses?
If that is currently not the case yet, would it make sense to make it
aware so it will
I was wondering if you had disabled conflux for any of your relays, and
if this was the case what we could do to help you and have you re-enable
it again.
Conflux was disabled on some exits but is currently enabled on all our
exit relays.
best regards,
t...@appliedprivacy.net
_
