| ... | ... | @@ -4,17 +4,40 @@ The following is a page to help with GSoC / SoP / Outreachy coordination. |
|
|
|
|
|
|
|
The following 4 projects are the ones we have in 2023 for students from Google Summer of Code. You can[ read about how to contact us and apply](https://gitlab.torproject.org/tpo/team/-/wikis/How-To-Apply-to-Google-Summer-of-Code).
|
|
|
|
|
|
|
|
## 1.
|
|
|
|
## 1. Relay to relay connectivity in the Tor network
|
|
|
|
|
|
|
|
- Mentor:
|
|
|
|
- Hours required:
|
|
|
|
- Skills required:
|
|
|
|
- Skills preferred:
|
|
|
|
- Expected outcome:
|
|
|
|
- Difficulty:
|
|
|
|
- Mentor: juga, GeKo
|
|
|
|
- Hours required: 175 hours
|
|
|
|
- Skills required: Rust
|
|
|
|
- Expected outcome: A tool scanning the Tor network for partitions is ready to be deployed
|
|
|
|
- Difficulty: medium
|
|
|
|
|
|
|
|
### Problem
|
|
|
|
|
|
|
|
In an ideal world, any Tor relay would be able to reach any other Tor relay when trying to build paths through the network, as partitioning in the Tor network is bad for Tor's anonymity guarantees. While we might be lucky and there are no partitions in the network right now (which is very unlikely), we currently have no means to monitor that property of our network and detect if that changes in the future.
|
|
|
|
|
|
|
|
### Proposal
|
|
|
|
|
|
|
|
This project would involve the implementation of a relay to relay connectivity checking tool written in Rust to make use of our arti Tor client (which is written in Rust, too).
|
|
|
|
|
|
|
|
There have been many attempts in the past to write such a tool. However, none of them succeeded in producing one that we can use for keeping track of relay connectivity on a regular basis, which is an important network health goal. There are resources below pointing to past attempts and issues encountered which should be considered when designing the relay to relay connectivity checker in this project. Particular focus should be placed on a sound scanning strategy taking an additional load onto the network into account and how to store the results so we can use them in follow-up work for further visualization, e.g. on a dashboard, making the partitions in the network visible over time.
|
|
|
|
|
|
|
|
*Resources:*
|
|
|
|
|
|
|
|
For arti:
|
|
|
|
- https://gitlab.torproject.org/tpo/core/arti
|
|
|
|
|
|
|
|
For general information about past work on relay to relay connectivity scanning:
|
|
|
|
- https://gitlab.torproject.org/tpo/network-health/analysis/-/issues/1
|
|
|
|
- https://gitlab.torproject.org/tpo/core/tor/-/issues/19068
|
|
|
|
- https://gitlab.torproject.org/tpo/network-health/metrics/ideas/-/issues/25775
|
|
|
|
- https://gitlab.torproject.org/tpo/network-health/team/-/issues/16
|
|
|
|
- https://lists.torproject.org/pipermail/tor-project/2017-October/001492.html
|
|
|
|
- https://lists.torproject.org/pipermail/network-health/2021-March/000668.html
|
|
|
|
- https://github.com/teor2345/onion-graph
|
|
|
|
- https://bitbucket.org/ra_/tor-relay-connectivity.git
|
|
|
|
- https://github.com/david415/tor_partition_scanner
|
|
|
|
- https://github.com/sachaservan/ShorTor
|
|
|
|
|
|
|
|
## 2.
|
|
|
|
|
| ... | ... | @@ -27,6 +50,7 @@ The following 4 projects are the ones we have in 2023 for students from Google S |
|
|
|
|
|
|
|
### Problem
|
|
|
|
|
|
|
|
### Proposal
|
|
|
|
|
|
|
|
|
|
|
|
## 3.
|
| ... | ... | @@ -40,6 +64,7 @@ The following 4 projects are the ones we have in 2023 for students from Google S |
|
|
|
|
|
|
|
### Problem
|
|
|
|
|
|
|
|
### Proposal
|
|
|
|
|
|
|
|
|
|
|
|
## 4.
|
| ... | ... | @@ -53,6 +78,7 @@ The following 4 projects are the ones we have in 2023 for students from Google S |
|
|
|
|
|
|
|
### Problem
|
|
|
|
|
|
|
|
### Proposal
|
|
|
|
|
|
|
|
---
|
|
|
|
|
| ... | ... | |
