135h is enough to submit a small, one-line change to get used to the tor patch process, and then do something more substantial with some testing. Understanding the code, and testing and documenting the fix can take more time than writing the patch. Your students could work on getting IPv6 bridges working with private IPv4 addresses. The bridge needs to include a placeholder IPv4 address in its descriptor, and then the bridge client needs to ignore this address. Or they could work out why Tor Browser often fails IPv6-only sites like We think it's because IPv4 exits don't resolve AAAA addresses. Failed addresses should've resolved and sent back to the client. And then the client can use the address to pick its next exit. We've made some progress on both of these issues, but then ran out of time.
Sorry, this was the wrong link. Please use: (We are still adding features to the matrix.)
|
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev