Changes between Version 3 and Version 4 of TorWeeklyNews/2015/5


Ignore:
Timestamp:
Feb 4, 2015, 11:52:56 AM (4 years ago)
Author:
harmony
Comment:

numbers

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews/2015/5

    v3 v4  
    1616----------------------------
    1717
    18 Late last year, Mozilla announced [XXX] its partnership with the Tor
    19 Project in the Polaris Privacy Initiative [XXX], a program aimed at
     18Late last year, Mozilla announced [1] its partnership with the Tor
     19Project in the Polaris Privacy Initiative [2], a program aimed at
    2020“giving users more control, awareness and protection in their Web
    2121experiences”. One of the two Tor-related “experiments” Mozilla planned
    2222to carry out was the operation of several high-capacity middle relays,
    2323and last week Mozilla’s Network Engineering team announced that the new
    24 nodes [XXX] had been running for several weeks, in a blog post [XXX]
    25 that explores the technical decisions and challenges they faced in
    26 setting them up.
     24nodes [3] had been running for several weeks, in a blog post [4] that
     25explores the technical decisions and challenges they faced in setting
     26them up.
    2727
    2828The team discussed the hardware and infrastructure chosen for the
    2929relays, configuration management using Ansible (publishing their
    30 playbook [XXX] at the same time), and security practices, as well as
     30playbook [5] at the same time), and security practices, as well as
    3131announcing their intention to continue posting about their experiences
    3232and findings during the experiment.
     
    3434Thanks to Mozilla for this contribution to the Tor network!
    3535
    36  [XXX]: https://lists.torproject.org/pipermail/tor-news/2014-November/000071.html
    37  [XXX]: https://blog.mozilla.org/privacy/2014/11/10/introducing-polaris-privacy-initiative-to-accelerate-user-focused-privacy-online/
    38  [XXX]: https://globe.torproject.org/#/search/query=mozilla
    39  [XXX]: https://blog.mozilla.org/it/2015/01/28/deploying-tor-relays/
    40  [XXX]: https://github.com/XioNoX/moz-tor-relays/
     36  [1]: https://lists.torproject.org/pipermail/tor-news/2014-November/000071.html
     37  [2]: https://blog.mozilla.org/privacy/2014/11/10/introducing-polaris-privacy-initiative-to-accelerate-user-focused-privacy-online/
     38  [3]: https://globe.torproject.org/#/search/query=mozilla
     39  [4]: https://blog.mozilla.org/it/2015/01/28/deploying-tor-relays/
     40  [5]: https://github.com/XioNoX/moz-tor-relays/
    4141
    4242Monthly status reports for January 2015
     
    4444
    4545The wave of regular monthly reports from Tor project members for the
    46 month of January has begun. Juha Nurmi released his report first [XXX],
    47 followed by reports from Philipp Winter [XXX], Damian Johnson [XXX],
    48 Sherief Alaa [XXX], Georg Koppen [XXX], and David Goulet [XXX].
     46month of January has begun. Juha Nurmi released his report first [6],
     47followed by reports from Philipp Winter [7], Damian Johnson [8], Sherief
     48Alaa [9], Georg Koppen [10], and David Goulet [11].
    4949
    50  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2015-January/000748.html
    51  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2015-January/000749.html
    52  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2015-February/000750.html
    53  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2015-February/000751.html
    54  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2015-February/000752.html
    55  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2015-February/000753.html
     50  [6]: https://lists.torproject.org/pipermail/tor-reports/2015-January/000748.html
     51  [7]: https://lists.torproject.org/pipermail/tor-reports/2015-January/000749.html
     52  [8]: https://lists.torproject.org/pipermail/tor-reports/2015-February/000750.html
     53  [9]: https://lists.torproject.org/pipermail/tor-reports/2015-February/000751.html
     54 [10]: https://lists.torproject.org/pipermail/tor-reports/2015-February/000752.html
     55 [11]: https://lists.torproject.org/pipermail/tor-reports/2015-February/000753.html
    5656
    5757Miscellaneous news
    5858------------------
    5959
    60 meejah announced [XXX] version 0.12.0 of txtorcon, the Tor controller
     60meejah announced [12] version 0.12.0 of txtorcon, the Tor controller
    6161client in Twisted; please see the announcement for a full list of
    6262improvements.
    6363
    64  [XXX]: https://lists.torproject.org/pipermail/tor-dev/2015-February/008227.html
     64 [12]: https://lists.torproject.org/pipermail/tor-dev/2015-February/008227.html
    6565
    66 Nick Mathewson submitted a draft of proposal 241 [XXX], which aims to
     66Nick Mathewson submitted a draft of proposal 241 [13], which aims to
    6767protect users against adversaries who are able to attack their
    6868connectivity to the Tor network and force them to use malicious guard
    69 nodes. Roger Dingledine offered [XXX] some further thoughts.
     69nodes. Roger Dingledine offered [14] some further thoughts.
    7070
    71  [XXX]: https://lists.torproject.org/pipermail/tor-dev/2015-February/008223.html
    72  [XXX]: https://lists.torproject.org/pipermail/tor-dev/2015-February/008226.html
     71 [13]: https://lists.torproject.org/pipermail/tor-dev/2015-February/008223.html
     72 [14]: https://lists.torproject.org/pipermail/tor-dev/2015-February/008226.html
    7373
    74 Nick also set out the schedule for the Tor 0.2.6 feature freeze [XXX].
     74Nick also set out the schedule for the Tor 0.2.6 feature freeze [15].
    7575
    76  [XXX]: https://lists.torproject.org/pipermail/tor-dev/2015-January/008216.html
     76 [15]: https://lists.torproject.org/pipermail/tor-dev/2015-January/008216.html
    7777
    7878After reports from users that Tor Browser’s default obfs4 bridges are no
    79 longer usable in China, David Fifield estimated [XXX] the time it takes
     79longer usable in China, David Fifield estimated [16] the time it takes
    8080for the “Great Firewall” to react to new circumvention systems as lying
    8181“between 2 and 10 weeks”, and asked for additional data to narrow the
    8282range further.
    8383
    84  [XXX]: https://lists.torproject.org/pipermail/tor-dev/2015-February/008222.html
     84 [16]: https://lists.torproject.org/pipermail/tor-dev/2015-February/008222.html
    8585
    8686Isis Lovecruft “would be super stoked if we could make it as easy and
    8787seamless as possible for the bridge operators who are still running
    8888obfs2 (!!) to move to supporting better, newer pluggable transports”,
    89 such as obfs4, and wondered [XXX] how to make it possible for operators
     89such as obfs4, and wondered [17] how to make it possible for operators
    9090running Debian stable to get the necessary dependencies onto their
    9191system without extensive backporting: “If someone has done this, or has
     
    9393the steps you took, please?”
    9494
    95  [XXX]: https://lists.torproject.org/pipermail/tor-relays/2015-February/006346.html
     95 [17]: https://lists.torproject.org/pipermail/tor-relays/2015-February/006346.html
    9696
    97 The Tails team continued to discuss [XXX] the advantages and
     97The Tails team continued to discuss [18] the advantages and
    9898disadvantages of removing AdBlock Plus from Tails’ version of Tor
    9999Browser.
    100100
    101  [XXX]: https://mailman.boum.org/pipermail/tails-dev/2015-February/008003.html
     101 [18]: https://mailman.boum.org/pipermail/tails-dev/2015-February/008003.html
    102102
    103 Sadia Afroz compiled a timeline of Tor blocking events, and shared [XXX]
     103Sadia Afroz compiled a timeline of Tor blocking events, and shared [19]
    104104it with the ooni-dev mailing list, along with a request for missing data
    105 points; Collin Anderson responded [XXX] with some additional
    106 information.
     105points; Collin Anderson responded [20] with some additional information.
    107106
    108  [XXX]: https://lists.torproject.org/pipermail/ooni-dev/2015-February/000241.html
    109  [XXX]: https://lists.torproject.org/pipermail/ooni-dev/2015-February/000242.html
     107 [19]: https://lists.torproject.org/pipermail/ooni-dev/2015-February/000241.html
     108 [20]: https://lists.torproject.org/pipermail/ooni-dev/2015-February/000242.html
    110109
    111 Patrick Schleizer announced [XXX] that the Whonix team is looking for “a
     110Patrick Schleizer announced [21] that the Whonix team is looking for “a
    112111sponsor who is willing to donate a suitable sized virtual or root
    113112server”, and gave a list of planned requirements. If you can meet this
    114113need, please see Patrick’s message for next steps.
    115114
    116  [XXX]: https://lists.torproject.org/pipermail/tor-talk/2015-February/036675.html
     115 [21]: https://lists.torproject.org/pipermail/tor-talk/2015-February/036675.html
    117116
    118 Konstantin Müller shared [XXX] a report written as part of a Master’s
     117Konstantin Müller shared [22] a report written as part of a Master’s
    119118degree, offering an introduction to “the past, present, and future” of
    120119Tor hidden services.
    121120
    122  [XXX]: https://lists.torproject.org/pipermail/tor-talk/2015-February/036709.html
     121 [22]: https://lists.torproject.org/pipermail/tor-talk/2015-February/036709.html
    123122
    124123News from Tor StackExchange
    125124---------------------------
    126125
    127 Windy wanted to know how often a client fetches consensus data from
    128 a directory server [XXX]. Jens Kubieziel provided some information
    129 by walking through the source code, and concluded: “every minute it
    130 is checked if the consensus document is too old. If it is older than
    131 the current time a new one will be fetched.”
     126Windy wanted to know how often a client fetches consensus data from a
     127directory server [23]. Jens Kubieziel provided some information by
     128walking through the source code, and concluded: “every minute it is
     129checked if the consensus document is too old. If it is older than the
     130current time a new one will be fetched.”
    132131
    133  [XXX]: https://tor.stackexchange.com/q/6087/88
     132 [23]: https://tor.stackexchange.com/q/6087/88
    134133
    135134Upcoming events
     
    153152Want to continue reading TWN? Please help us create this newsletter.
    154153We still need more volunteers to watch the Tor community and report
    155 important news. Please see the project page [XXX], write down your
    156 name and subscribe to the team mailing list [XXX] if you want to
     154important news. Please see the project page [24], write down your
     155name and subscribe to the team mailing list [25] if you want to
    157156get involved!
    158157
    159   [XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
    160   [XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
     158 [24]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
     159 [25]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
    161160}}}