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

Feb 3, 2015, 10:27:49 PM (5 years ago)

this week


  • TorWeeklyNews/2015/5

    v2 v3  
    11''83rd issue of Tor Weekly News. Covering what's happening from January 27th, 2015 to February 3rd, 2015. To be released on February 4th, 2015.''
    3 '''Editor:'''
     3'''Editor:''' Harmony
    55'''Subject:''' Tor Weekly News — February 4th, 2015
    1212Welcome to the fifth issue in 2015 of Tor Weekly News, the weekly
    13 newsletter that covers what’s happening in the XXX Tor community.
     13newsletter that covers what’s happening in the Tor community.
    15 Feature XXX
    16 -----------
     15Mozilla’s Tor relays go live
    18 Feature 1 with cited source [XXX]
     18Late last year, Mozilla announced [XXX] its partnership with the Tor
     19Project in the Polaris Privacy Initiative [XXX], a program aimed at
     20“giving users more control, awareness and protection in their Web
     21experiences”. One of the two Tor-related “experiments” Mozilla planned
     22to carry out was the operation of several high-capacity middle relays,
     23and last week Mozilla’s Network Engineering team announced that the new
     24nodes [XXX] had been running for several weeks, in a blog post [XXX]
     25that explores the technical decisions and challenges they faced in
     26setting them up.
    20  [XXX]:
     28The team discussed the hardware and infrastructure chosen for the
     29relays, configuration management using Ansible (publishing their
     30playbook [XXX] at the same time), and security practices, as well as
     31announcing their intention to continue posting about their experiences
     32and findings during the experiment.
    22 Monthly status reports for XXX month 2015
    23 -----------------------------------------
     34Thanks to Mozilla for this contribution to the Tor network!
     36 [XXX]:
     37 [XXX]:
     38 [XXX]:
     39 [XXX]:
     40 [XXX]:
     42Monthly status reports for January 2015
    2545The wave of regular monthly reports from Tor project members for the
    26 month of XXX has begun. XXX released his report first [XXX], followed
    27 by reports from name 2 [XXX], name 3 [XXX], and name 4 [XXX].
     46month of January has begun. Juha Nurmi released his report first [XXX],
     47followed by reports from Philipp Winter [XXX], Damian Johnson [XXX],
     48Sherief Alaa [XXX], Georg Koppen [XXX], and David Goulet [XXX].
    29  [XXX]:
    30  [XXX]:
    31  [XXX]:
    32  [XXX]:
     50 [XXX]:
     51 [XXX]:
     52 [XXX]:
     53 [XXX]:
     54 [XXX]:
     55 [XXX]:
    3457Miscellaneous news
    37 Item 1 with cited source [XXX].
     60meejah announced [XXX] version 0.12.0 of txtorcon, the Tor controller
     61client in Twisted; please see the announcement for a full list of
    39 Item 2 with cited source [XXX].
     64 [XXX]:
    41 Item 3 with cited source [XXX].
     66Nick Mathewson submitted a draft of proposal 241 [XXX], which aims to
     67protect users against adversaries who are able to attack their
     68connectivity to the Tor network and force them to use malicious guard
     69nodes. Roger Dingledine offered [XXX] some further thoughts.
    43  [XXX]:
    44  [XXX]:
    45  [XXX]:
     71 [XXX]:
     72 [XXX]:
    47 Tor help desk roundup
    48 ---------------------
     74Nick also set out the schedule for the Tor 0.2.6 feature freeze [XXX].
    50 Summary of some questions sent to the Tor help desk.
     76 [XXX]:
     78After reports from users that Tor Browser’s default obfs4 bridges are no
     79longer usable in China, David Fifield estimated [XXX] the time it takes
     80for the “Great Firewall” to react to new circumvention systems as lying
     81“between 2 and 10 weeks”, and asked for additional data to narrow the
     82range further.
     84 [XXX]:
     86Isis Lovecruft “would be super stoked if we could make it as easy and
     87seamless as possible for the bridge operators who are still running
     88obfs2 (!!) to move to supporting better, newer pluggable transports”,
     89such as obfs4, and wondered [XXX] how to make it possible for operators
     90running Debian stable to get the necessary dependencies onto their
     91system without extensive backporting: “If someone has done this, or has
     92another simple solution, would you mind writing up some short how-to on
     93the steps you took, please?”
     95 [XXX]:
     97The Tails team continued to discuss [XXX] the advantages and
     98disadvantages of removing AdBlock Plus from Tails’ version of Tor
     101 [XXX]:
     103Sadia Afroz compiled a timeline of Tor blocking events, and shared [XXX]
     104it with the ooni-dev mailing list, along with a request for missing data
     105points; Collin Anderson responded [XXX] with some additional
     108 [XXX]:
     109 [XXX]:
     111Patrick Schleizer announced [XXX] that the Whonix team is looking for “a
     112sponsor who is willing to donate a suitable sized virtual or root
     113server”, and gave a list of planned requirements. If you can meet this
     114need, please see Patrick’s message for next steps.
     116 [XXX]:
     118Konstantin Müller shared [XXX] a report written as part of a Master’s
     119degree, offering an introduction to “the past, present, and future” of
     120Tor hidden services.
     122 [XXX]:
    52124News from Tor StackExchange
    55127Windy wanted to know how often a client fetches consensus data from
    56 a directory authority [XXX]. Jens Kubieziel provided some information
    57 by walking through the source code. He conluded that "Every minute it
     128a directory server [XXX]. Jens Kubieziel provided some information
     129by walking through the source code, and concluded: “every minute it
    58130is checked if the consensus document is too old. If it is older than
    59 the current time a new one will be fetched."
     131the current time a new one will be fetched.
    61  [XXX]:
    63 Easy development tasks to get involved with
    64 -------------------------------------------
    66 Text with cited source [XXX].
    68  [XXX]:
    70 This week in Tor history
    71 ------------------------
    73 Text with cited source [XXX].
    75  [XXX]:
     133 [XXX]:
    77135Upcoming events
    80 Jul XX-XX | Event XXX brief description
    81           | Event City, Event Country
    82           | Event website URL
    83           |
    84 Jul XX-XX | Event XXX brief description
    85           | Event City, Event Country
    86           | Event website URL
     138  Feb 04 13:30 UTC | little-t tor development meeting
     139                   | #tor-dev,
     140                   |
     141  Feb 09 18:00 UTC | Tor Browser online meeting
     142                   | #tor-dev,
     143                   |
     144  Feb 09 18:00 UTC | OONI development meeting
     145                   | #ooni,
     146                   |
     147  Feb 10 18:00 UTC | little-t tor patch workshop
     148                   | #tor-dev,
    89 This issue of Tor Weekly News has been assembled by XXX, XXX, and
    90 XXX.
     151This issue of Tor Weekly News has been assembled by qbi and Harmony.
    92153Want to continue reading TWN? Please help us create this newsletter.