... | ... | @@ -3,7 +3,7 @@ |
|
|
* Title: Bad relay work
|
|
|
* Facilitator: gus, gk
|
|
|
* Who: Bad relays working group (other folks are welcome as well)
|
|
|
* Not taker: arma
|
|
|
* Notetaker: arma
|
|
|
* Duration: 1 hour
|
|
|
* Description: In this session we will discuss the tools that keep the tor network safe and the working group capacity.
|
|
|
|
... | ... | @@ -117,7 +117,7 @@ for ssh fingerprints is a worthwhile checker too. |
|
|
- pairwise reachability between relays.
|
|
|
- "extendprobe" is a component of bermuda that tries to do this measurement. needs more people playing with it and gaining intuition.
|
|
|
- there's a tension between removing side channels and being able to diagnose anomalies on the network. For example, removing the "reason" byte from destroy cells made it harder to understand *why* relay A isn't able to reach relay B.
|
|
|
- see: https://gitlab.torproject.org/tpo/core/tor/-/issues/40623,https://gitlab.torproject.org/tpo/core/tor/-/issues/40655, and https://gitlab.torproject.org/tpo/core/tor/-/issues/40649
|
|
|
- see: https://gitlab.torproject.org/tpo/core/tor/-/issues/40623, https://gitlab.torproject.org/tpo/core/tor/-/issues/40655, and https://gitlab.torproject.org/tpo/core/tor/-/issues/40649
|
|
|
|
|
|
- idea: are there more ways we can be transparent about the bad-relays work? some things need to be secret but not everything does.
|
|
|
- for example, the fact that we have scanners is not secret. but a particular way to distinguish a bad relay is not a thing we should make public.
|
... | ... | |