[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-project] SponsorR Status Report April 2017



Hello,

here is the April 2017 report for SponsorR:

- During April, we moved forward and resolved tons of tickets on prop224
  groundwork implementation that we hope to merge in tor-0.3.1:
     https://trac.torproject.org/projects/tor/ticket/21871
     https://trac.torproject.org/projects/tor/ticket/21889
     https://trac.torproject.org/projects/tor/ticket/21891
     https://trac.torproject.org/projects/tor/ticket/21919
     https://trac.torproject.org/projects/tor/ticket/21978
     https://trac.torproject.org/projects/tor/ticket/21980
     https://trac.torproject.org/projects/tor/ticket/22052

- Continued work on the service-side part of prop224:
     https://trac.torproject.org/projects/tor/ticket/20657
  We are currently testing the hidden service code using chutney, and
  splitting it into smaller branches to ease review.

- Lots of design discussion on protecting onion addresses against
  phishing attacks:
     https://lists.torproject.org/pipermail/tor-dev/2017-April/012123.html   

  Also research on validating ed25519 public keys to avoid equivalent onion
  addresses:
     https://lists.torproject.org/pipermail/tor-dev/2017-April/012225.html
  We posted our ed25519 pubkey validation code:
     https://trac.torproject.org/projects/tor/ticket/22006

- Published technical report about relays we found camping the HSDir
  hash ring to monitor directory activity of hidden services:
     https://lists.torproject.org/pipermail/tor-dev/2017-April/012161.html

- More discussion on the name system proposal (prop279):
     https://lists.torproject.org/pipermail/tor-dev/2017-April/012126.html
_______________________________________________
tor-project mailing list
tor-project@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project