Changes between Version 23 and Version 24 of TorWeeklyNews/2014/31


Ignore:
Timestamp:
Aug 4, 2014, 1:17:47 PM (5 years ago)
Author:
lunar
Comment:

write about bad-relays

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews/2014/31

    v23 v24  
    1919
    2020 [XXX]:
     21
     22Why is bad-relays a closed mailing list?
     23----------------------------------------
     24
     25Damian Johnson and Philipp Winter have been working on improving the
     26process of reporting bad relays [XXX]. The process starts by having
     27users report odd behaviors to the bad-relays mailing list.
     28
     29Only a few trusted volunteers receive and review these reports. Nusenu
     30started a discussion on tor-talk [XXX] advocating for more transparency.
     31Nusenu argues that an open list would “likely get more confirm/can't
     32confirm feedback for a given badexit candidate”, and that it would allow
     33worried users to act faster than operators of directory authorities.
     34
     35Despite being “usually on the side of transparency”, Roger Dingledine
     36udescribe [XXX] being “stuck” on the issue, “because the arms race is so
     37lopsidedly against us”.
     38
     39Roger explains: “we can scan for whether exit relays handle certain
     40websites poorly, but if the list that we scan for is public, then exit
     41relays can mess with other websites and know they'll get away with it.
     42We can scan for incorrect behavior on various ports, but if the list of
     43ports and the set of behavior we do is public, then again relays are
     44free to mess with things we don't look for.”
     45
     46A better future and more transparency probably lies in adaptative test
     47systems run by multiple volunteer groups. Until they come to existence,
     48as a small improvement, Philipp Winter wrote [XXX] it was probably safe
     49to publish why relays were disabled, through “short sentence along the
     50lines of ‘running HTTPS MitM’ or ‘running sslstrip’”.
     51
     52 [XXX]: https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays
     53 [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-July/034198.html
     54 [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-July/034219.html
     55 [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-July/034216.html
    2156
    2257Monthly status reports for July 2014
     
    105140 * Call for testing: isohybrid vs. Tails 1.1 https://mailman.boum.org/pipermail/tails-testers/2014-July/000059.html https://mailman.boum.org/pipermail/tails-testers/2014-July/000060.html
    106141 * Proposal 236 and the guardiness of a guard https://lists.torproject.org/pipermail/tor-dev/2014-July/007269.html
    107  * Why make bad-relays a closed mailing list? https://lists.torproject.org/pipermail/tor-talk/2014-July/034198.html https://lists.torproject.org/pipermail/tor-talk/2014-July/034216.html https://lists.torproject.org/pipermail/tor-talk/2014-July/034219.html
    108142 * Tor Browser Weekly IRC meetings moved to 18:00 UTC Mondays https://lists.torproject.org/pipermail/tbb-dev/2014-August/000100.html
    109143 * carml 'super-alpha' https://lists.torproject.org/pipermail/tor-dev/2014-August/007295.html