Changes between Version 37 and Version 38 of TorWeeklyNews/2014/22


Ignore:
Timestamp:
Jun 4, 2014, 12:35:23 PM (5 years ago)
Author:
lunar
Comment:

sent!

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews/2014/22

    v37 v38  
    33'''Editor:''' Lunar
    44
    5 '''Status:''' Frozen. Only technical and language fixes allowed. New items should go to [wiki:TorWeeklyNews/2014/23 next week's edition]. Expected publication time 2014-06-04 12:00 UTC
    6 
    7 '''Subject:''' Tor Weekly News — June 4th, 2014
    8 
    9 {{{
    10 ========================================================================
    11 Tor Weekly News                                           June 4th, 2014
    12 ========================================================================
    13 
    14 Welcome to the twenty-second issue of Tor Weekly News in 2014, the
    15 weekly newsletter that covers what is happening in the Tor community.
    16 
    17 Tails moves to Wheezy
    18 ---------------------
    19 
    20 The Tails live system [1] is a Debian derivative [2] aiming at
    21 preserving the privacy and anonymity of its users.
    22 
    23 The first Tails releases were based on Debian Lenny [3] (2009-2012);
    24 since version 0.7, Tails has been based on Debian Squeeze [4] (2011-).
    25 Meanwhile, Debian has released a new stable version dubbed Wheezy [5],
    26 and the upcoming Tails 1.1 will be the first release to be based on the
    27 latter.
    28 
    29 The general set of features should not change much from the previous
    30 Tails release, but almost every software component has been updated. On
    31 May 30th, the Tails team released a beta image [6]; given the number of
    32 changes, testing is even more welcome than usual.
    33 
    34 Testers can also try out the new UEFI support, which enables Tails to
    35 boot on recent hardware and on Macs.
    36 
    37 Several issues [7] with the current beta image have already been
    38 identified, so be sure to have a look at the list before reporting [8].
    39 
    40 The details of the release schedule are still being discussed [9] at the
    41 time of writing, but Tails 1.1 is likely to be out by the end of July.
    42 Please help make it a great release!
    43 
    44    [1]: https://tails.boum.org/
    45    [2]: https://wiki.debian.org/Derivatives
    46    [3]: https://www.debian.org/releases/lenny/
    47    [4]: https://www.debian.org/releases/squeeze/
    48    [5]: https://www.debian.org/releases/wheezy/
    49    [6]: https://tails.boum.org/news/test_1.1-beta1/
    50    [7]: https://tails.boum.org/news/test_1.1-beta1/#index3h1
    51    [8]: https://tails.boum.org/doc/first_steps/bug_reporting/
    52    [9]: https://mailman.boum.org/pipermail/tails-dev/2014-May/005917.html
    53 
    54 Stem 1.2 brings interactive interaction with the Tor daemon
    55 -----------------------------------------------------------
    56 
    57 On June 1st, Damian Johnson announced [10] the release of Stem [11] 1.2.
    58 Stem is a Python library for interacting with the Tor daemon. It is now
    59 used by several applications [12] like the arm [13] status monitor and
    60 Philipp Winter’s exit scanner [14].
    61 
    62 The new version brings an interactive control interpreter, “a new method
    63 for interacting with Tor’s control interface that combines an
    64 interactive python interpreter with raw access similar to telnet”. This
    65 should make Tor hackers happy by saving them from having to manually
    66 poke the control port through telnet or create complete Stem
    67 scripts.
    68 
    69 For the complete list of changes, head over to the changelog [15].
    70 
    71   [10]: https://blog.torproject.org/blog/stem-release-12
    72   [11]: https://stem.torproject.org/
    73   [12]: https://stem.torproject.org/tutorials/double_double_toil_and_trouble.html
    74   [13]: https://www.atagar.com/arm/
    75   [14]: http://www.cs.kau.se/philwint/spoiled_onions/
    76   [15]: https://stem.torproject.org/change_log.html#version-1-2
    77 
    78 Monthly status reports for May 2014
    79 -----------------------------------
    80 
    81 The wave of regular monthly reports from Tor project members for the
    82 month of May has begun. Pearl Crescent released their report first [16],
    83 followed by Sherief Alaa [17], Damian Johnson [18], Nick Mathewson [19],
    84 Colin C. [20], Georg Koppen [21], Lunar [22], Arlo Breault [23], and
    85 Matt Pagan [24].
    86 
    87 Lunar also reported on behalf of the help desk [25], while Arturo
    88 Filastò did likewise for the OONI team [26], and Mike Perry for the Tor
    89 Browser team [27].
    90 
    91   [16]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000539.html
    92   [17]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000540.html
    93   [18]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000542.html
    94   [19]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000543.html
    95   [20]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000544.html
    96   [21]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000545.html
    97   [22]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000546.html
    98   [23]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000548.html
    99   [24]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000550.html
    100   [25]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000541.html
    101   [26]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000547.html
    102   [27]: https://lists.torproject.org/pipermail/tor-reports/2014-June/000549.html
    103 
    104 Miscellaneous news
    105 ------------------
    106 
    107 Pups, a chat system implemented by Sherief Alaa for real-time
    108 invitation-based user support, has gone live [28], and can now be used
    109 by Tor’s support assistants when that method promises a quicker
    110 resolution of an issue.
    111 
    112   [28]: https://bugs.torproject.org/11657
    113 
    114 In response to a question about the writing of unit tests for tor, Nick
    115 Mathewson shared [29] a brief guide to identifying lines in tor’s
    116 codebase that have not yet been covered by tests.
    117 
    118   [29]: https://lists.torproject.org/pipermail/tor-dev/2014-June/006933.html
    119 
    120 Nick also put out a call (relayed by Moritz Bartl [30]) for Tor relay
    121 operators running version 0.2.5.4-alpha or later to profile their
    122 relays, in order to identify potential bottlenecks. Basic instructions
    123 for doing so on Debian and Ubuntu can be found in the comments to the
    124 relevant ticket [31].
    125 
    126   [30]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004617.html
    127   [31]: https://bugs.torproject.org/11332
    128 
    129 During a discussion on the role of JavaScript hooks in Tor Browser, Mike
    130 Perry clarified [32] the merits of writing direct C++ Firefox patches
    131 over using such hooks, as well as the possibility of incorporating
    132 Torbutton’s privacy features into either Firefox itself or a dedicated
    133 add-on.
    134 
    135   [32]: https://lists.torproject.org/pipermail/tbb-dev/2014-June/000074.html
    136 
    137 Andrew Lewman reported [33] on his trip to Stockholm to address Sida and
    138 the Stockholm Internet Forum.
    139 
    140   [33]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000538.html
    141 
    142 Juha Nurmi sent the second weekly report for the ahmia.fi Google Summer
    143 of Code project [34].
    144 
    145   [34]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000537.html
    146 
    147 Marc Juarez is working on website fingerprinting countermeasures in the
    148 form of a pluggable transport. Marc wants to “implement a set of
    149 primitives that any link padding-based defense would benefit of” and is
    150 looking for feedback [35] on the envisaged primitives.
    151 
    152   [35]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006918.html
    153 
    154 Philipp Winter announced [36] that Atlas [37], the web application to
    155 learn about currently running Tor relays, will now display information
    156 about a relay’s IPv6 exit policy, as well as the already-existing IPv4
    157 exit summary.
    158 
    159   [36]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004620.html
    160   [37]: https://atlas.torproject.org
    161 
    162 Tor help desk roundup
    163 ---------------------
    164 
    165 Sometimes users with no network obstacles will email the help desk to
    166 ask how to configure their Tor Browser. Often these users will not need
    167 to configure anything, and clicking “Connect” is all that is necessary.
    168 Discussion on this problem is taking place on the bug tracker [38].
    169 
    170   [38]: https://bugs.torproject.org/12164
    171 
    172 Easy development tasks to get involved with
    173 -------------------------------------------
    174 
    175 The bridge distributor BridgeDB [39] populates its database from the
    176 cached descriptor files copied over from the bridge authority. There’s a
    177 small bug in BridgeDB where a line that is included in two different
    178 cached descriptor files gets added twice to the database [40]. The
    179 ticket says this bug is easily reproducible and even contains commands
    180 for reproducing it. If you enjoy digging into unknown Python/Twisted
    181 codebases to find the few spots that need fixing, this bug may be for
    182 you. Be sure to comment on the ticket when you have a fix!
    183 
    184   [39]: https://bridges.torproject.org/
    185   [40]: https://bugs.torproject.org/11216
    186 
    187 Upcoming events
    188 ---------------
    189 
    190 June  4 18:00 UTC | Tor Weather development meeting
    191                   | #tor-dev, irc.oftc.net
    192                   | https://lists.torproject.org/pipermail/tor-dev/2014-June/006937.html
    193                   |
    194 June  4 19:00 UTC | little-t tor development meeting
    195                   | #tor-dev, irc.oftc.net
    196                   | https://lists.torproject.org/pipermail/tor-dev/2014-June/006938.html
    197                   |
    198 June  6 15:00 UTC | Tor Browser online meeting
    199                   | #tor-dev, irc.oftc.net
    200                   | https://lists.torproject.org/pipermail/tbb-dev/2014-April/000049.html
    201                   |
    202 June  6 16:00 UTC | Pluggable transports online meeting
    203                   | #tor-dev, irc.oftc.net
    204                   | https://lists.torproject.org/pipermail/tor-dev/2014-April/006764.html
    205                   |
    206 June  7 19:00 CDT | Colin @ CryptoParty, Winnipeg
    207                   | SkullSpace, Winnipeg, MB, Canada
    208                   | http://wiki.skullspace.ca/index.php/CryptoParty
    209                   |
    210 June 11 19:00 UTC | Tails contributors meeting
    211                   | #tails-dev, irc.oftc.net
    212                   | https://mailman.boum.org/pipermail/tails-dev/2014-May/005818.html
    213 
    214 
    215 This issue of Tor Weekly News has been assembled by harmony, Lunar,
    216 Matt Pagan and Karsten Loesing.
    217 
    218 Want to continue reading TWN? Please help us create this newsletter.
    219 We still need more volunteers to watch the Tor community and report
    220 important news. Please see the project page [41], write down your
    221 name and subscribe to the team mailing list [42] if you want to
    222 get involved!
    223 
    224   [41]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
    225   [42]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
    226 }}}
     5'''Status:''' [https://lists.torproject.org/pipermail/tor-news/2014-June/000048.html Sent]