[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-talk] 'How to report bad relays' (blog entry)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
quoting from [1].
> If it's reproducible, we attempt to get in touch with the relay
> operator
Does this imply that you try to fix the issue with an confirmed "bad
relay" before assigning them the badexit flag?
(opposed to flagging them first - which means protecting users first and
then trying to get this fixed? - removing the flags after recovery)
> In severe cases, we [(currently Roger, Peter, Damian, Karsten, and
> I)] are also able to remove the relay descriptor from the network
> consensus which effectively makes the relay disappear.
from the comment reply to this sentence:
> If a sufficient number of directory authority operators agree
> (which is not always the case), then they are able to disable a
> selected relay. This happens every other day or week when we
> discover a malicious or broken relay. Also, our directory authority
> operators as well as their servers are in different jurisdiction
> which makes political attacks harder.
(yes, "a sufficient number of directory authority operators" is
probably more accurate than "we")
..but are you really saying that "every other day or week" the
majority of dir auth. operators are "removing a relay descriptor from
the network consensus"?
(making them "disappear" opposed to giving them i.e. the badexit flag)
If the removal rate is so high ("every other day or week") where can
we find a list of all relays that have been removed from the consensus
in the past so far?
This process should be transparent, no?
I tried to find 'rejected' flagged relays on the following page but
wasn't successful.
https://consensus-health.torproject.org/
thanks!
[1] https://blog.torproject.org/blog/how-report-bad-relays
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJT2XmnAAoJEDcK3SCCSvoeWLkP/233jyGRCEM5wPQ3wdGVuLgf
sGCoteLcflBkjFkYkKZGY3VJ1iLZL5gZ3i31VpVNrigQ6/kIpywnXUJGyrYNOkHF
SHeO8SUSxLnrconiFgdiwWjrXS5J/g/oxbfo7hyiVbLEqv9RKxjB4qlN0e13zJLh
IobhSF2HP/62sfx1k16ZFlmszWz3uioWAunha7Iqe1OSHf9PY7u72ecLE9M4ptp/
O20LScP9dfo7cA3FXM0ZqqkY1MBD80C4dzx5ukjtf2SsdqtrH8xnewP4bJoI6w1n
UQC8RuYIpfXWwR+UnZbZlyU8RqQxVmK6hiz9EyAIrtP7TvFEUTEmjbrMksHALKiK
vMELiuIC+KkpApvtrrhyqFMjKoix+HgmC4ET/60xJuJJacCcupu/ZVJuqdcyjvhV
OCoTNDqpj7og4m4RNWHygxgRxXwb3WzxZIdF5mWjrQ+Kiloup5fwVeCaDRP3xEqw
p/+zkbXfH83PTgQQggCh7OUGFuq2icZ9mJYcBHdDnEl8xReXV5wlJJxkyS3hsS04
p3G4Ze7rIieqdpHVuYBudFqyMeP3SDBSRxCGoeHS4GZhVzxXyqD1TFut0hUOhvmF
SJeQw4bPAf4ZRTvkxdpP/0GNz3c7Ldj+rigtTN9bKbHISXhmH/1MBv66rSS2iDPE
nI6aIh1Hpmnou77UD6DI
=Xv0C
-----END PGP SIGNATURE-----
--
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk