Changes between Version 51 and Version 52 of TorWeeklyNews/2013/11


Ignore:
Timestamp:
Sep 18, 2013, 7:03:18 AM (6 years ago)
Author:
lunar
Comment:

a few more nitpicks

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews/2013/11

    v51 v52  
    2727that might be managed through such an interface.
    2828
    29 Andrew Lewman posted an official response on the Tor Blog [6] in which
     29Andrew Lewman posted an official response on the Tor blog [6] in which
    3030he reiterated that “it’s not clear what the NSA or GCHQ can or cannot do”,
    3131and that well-known theoretical attacks against the Tor network are clearly
     
    3333
    3434He further added that the tool in question was more likely to involve
    35 “some “Tor flow detector” scripts that let them pick Tor flows out of a
     35“some ‘Tor flow detector’ scripts that let them pick Tor flows out of a
    3636set of flows they’re looking at” than “anything to do with deanonymizing
    3737Tor users, except insofar as they might have traffic flows from both sides
     
    8787In response to some confusion on the part of relay operators over the
    8888apparently slow growth in the use of newly-established nodes by clients,
    89 Roger Dingledine posted on the Tor Blog [11] a detailed account of how
     89Roger Dingledine posted on the Tor blog [11] a detailed account of how
    9090new relays, and the bandwidth they supply, are gradually integrated into
    9191the Tor network by directory authorities, bandwidth authorities, and clients
     
    132132
    133133  [14] https://trac.torproject.org/projects/tor/wiki/torbirdy#BeforeusingTorBirdy
    134   [15] https://www.torproject.org/docs/rpms.html.en
     134  [15] https://www.torproject.org/docs/rpms.html
    135135  [16] https://bugs.torproject.org/4389
    136136  [17] https://bugs.torproject.org/9718