Changes between Version 53 and Version 54 of TorWeeklyNews/2014/8


Ignore:
Timestamp:
Feb 26, 2014, 12:29:57 PM (5 years ago)
Author:
lunar
Comment:

sent!

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews/2014/8

    v53 v54  
    33'''Editor:''' Lunar
    44
    5 '''Status:''' FROZEN! New items should go to [wiki:TorWeeklyNews/2014/9 next week's edition]. Expected publication time: 2014-02-26 12:00 UTC.
    6 
    7 '''Subject:''' Tor Weekly News — February 26th, 2014
    8 
    9 {{{
    10 ========================================================================
    11 Tor Weekly News                                      February 26th, 2014
    12 ========================================================================
    13 
    14 Velkomin to the eighth issue of Tor Weekly News in 2014, the weekly
    15 newsletter that covers what is happening in the Tor community.
    16 
    17 News from the 2014 Winter Developers’ Meeting in Reykjavík
    18 ----------------------------------------------------------
    19 
    20 Since 2010, the Tor Project’s core contributors have tried to meet twice
    21 a year to enjoy the pleasure of each other’s company and move projects
    22 forward through face-to-face discussions and hacking time. This year,
    23 close to forty people attended the “2014 winter dev. meeting” [1], which
    24 was held in Reykjavík, Iceland.
    25 
    26 The team discussed over forty topics ranging from organizational matters
    27 to highly technical design decisions. Among the highlights: many
    28 sessions were focused on discussing and producing roadmaps — a mid-term
    29 vision for the Tor Browser [2], a step-by-step plan for the Tor
    30 Instant Messaging Bundle [3], detailed ideas for new bridge bundles [4],
    31 ways to solve the research problems around guard nodes [5], and how to
    32 plan little-t tor releases [6].
    33 
    34 The meeting also enabled cross-team communication: pluggable transports
    35 developers were able to discuss integration into the Tor Browser [7] and
    36 the lifecycle of recommended transports [8], while the Tor Browser group
    37 and the support teams met to see how to improve communications on both
    38 sides [9]. One outcome is a plan to remix existing documentation to
    39 create the Tor Browser User Manual [10].
    40 
    41 Two days of intense discussion were followed by hands-on sessions which
    42 saw their fair share of hacking and write-ups [11].
    43 
    44 Some of the minutes are still missing, but there is already plenty to
    45 read. Now that the developers have had to stop contemplating the
    46 Northern Lights [12], some discussions [13] are already continuing on
    47 the project’s various mailing lists. Stay tuned!
    48 
    49    [1]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting
    50    [2]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorBrowserPlan
    51    [3]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/RoadmapTIMB
    52    [4]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeBundles
    53    [5]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/GuardDesign
    54    [6]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorReleaseProcess
    55    [7]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/PTTBB
    56    [8]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeProtocolsAndTBB
    57    [9]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/SupportAndTorBrowserTeamsMeeting
    58   [10]: https://bugs.torproject.org/10974
    59   [11]: https://trac.torproject.org/projects/tor/timeline?from=Feb+21%2C+2014&daysback=2&authors=&ticket=on&ticket_details=on&changeset=on&update=Update
    60   [12]: https://en.wikipedia.org/wiki/Aurora_(astronomy)
    61   [13]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006288.html
    62 
    63 Miscellaneous news
    64 ------------------
    65 
    66 Karsten Loesing announced [14] an IRC meeting to discuss the next steps for
    67 the rewrite of Tor Weather, to be held on the OFTC #tor-dev channel on
    68 Wednesday 26th February at 18:00 UTC. “Topics include reporting progress
    69 made since the last meeting two weeks ago, making plans for the next
    70 week, and possibly turning this project into a GSoC project”.
    71 
    72   [14]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006299.html
    73 
    74 Nick Mathewson announced [15] the start of a weekly Tor developer’s meeting,
    75 to be held on the OFTC #tor-dev channel, “for working on the program
    76 ‘tor’. (This won’t cover all the other programs developed under the Tor
    77 umbrella.)”.
    78 
    79   [15]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006282.html
    80 
    81 The Tails developers will be holding [16] their next contributors’ meeting on
    82 the OFTC #tails-dev channel at 9pm UTC on March 5th; “everyone
    83 interested in contributing to Tails is welcome.”.
    84 
    85   [16]: https://mailman.boum.org/pipermail/tails-dev/2014-February/004934.html
    86 
    87 Andrew Lewman submitted his monthly status report for January [17], and
    88 also wrote up a report of his involvement in the recent Boston
    89 CryptoParty [18].
    90 
    91   [17]: https://lists.torproject.org/pipermail/tor-reports/2014-February/000462.html
    92   [18]: https://lists.torproject.org/pipermail/tor-reports/2014-February/000463.html
    93 
    94 Alexander Dietrich published [19] a multi-instance init script for Tor
    95 (“basically the current official init script and torservers.net’s
    96 “instances” mechanism frankensteined together”, in Alexander’s words) in
    97 response to a recent discussion on tor-relays [20].
    98 
    99   [19]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003942.html
    100   [20]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003913.html
    101 
    102 Responding to a message from someone interested in writing a DNS-based
    103 pluggable transport, George Kadianakis suggested [21] several ways in which
    104 the existing obfsproxy code could be reworked to accommodate this.
    105 
    106   [21]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006250.html
    107 
    108 George also recommended [22] that operators of obfs3 or ScrambleSuit bridges
    109 install the python-gmpy package on their relays, as it can significantly
    110 increase the speed of some cryptographic operations.
    111 
    112   [22]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003951.html
    113 
    114 Jens Kubieziel wrote up [23] the results of an attempt to determine whether
    115 the recent transition between the TAP and NTor handshake protocols is
    116 connected to some users’ reports of hidden service unavailability.
    117 
    118   [23]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006260.html
    119 
    120 Max Jakob Maass published [24] the preliminary results of a test in which the
    121 RIPE Atlas measurement API was used to retrieve the SSL certificate of
    122 torproject.org from as many countries as possible in order to detect
    123 attempted attacks or censorship, and wondered whether it might be worth
    124 running such a test on a regular basis.
    125 
    126   [24]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032173.html
    127 
    128 With regard to a coming redesign of the “Volunteers” section on the Tor
    129 Project’s website, Moritz Bartl wrote up a list of proposed volunteer
    130 categories that was the fruit of a brainstorming session at the Tor
    131 developers’ meeting, and asked for suggestions [25] of “obvious” missing
    132 sections, as well as “acceptably-licensed” graphics that could serve as
    133 icons for each category.
    134 
    135   [25]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032176.html
    136 
    137 Nathan Freitas wrote [26] from the Tor developers’ meeting with a
    138 request for help in compiling “user stories” on the Tor wiki: that is,
    139 stories of the form “a <type of Tor user> wants to <some feature of a
    140 Tor app> in order to <some reason related to security, privacy,
    141 etc>” [27]. If you have any to add, please write them up on the
    142 dedicated wiki page!
    143 
    144   [26]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032174.html
    145   [27]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/UserStories
    146 
    147 Yawning Angel sent out [28] a draft of a proposal to “extend the SOCKS5
    148 protocol when communicating with pluggable transports to allow passing
    149 more per-bridge meta-data to the transport and returning more meaningful
    150 connection failure response codes back to Tor”.
    151 
    152   [28]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006300.html
    153 
    154 Josh Ayers wrote [29] to the Tor-ramdisk list suggesting possible ways to
    155 ensure that sufficient entropy is available to the kernel by the time
    156 tor-ramdisk generates its long-term keys.
    157 
    158   [29]: http://opensource.dyc.edu/pipermail/tor-ramdisk/2014-February/000119.html
    159 
    160 Tor help desk roundup
    161 ---------------------
    162 
    163 A common question the help desk receives is how to respond to the Tor
    164 Browser Bundle’s download warning message. The message indicates that
    165 the Tor Browser Bundle only routes browser traffic through Tor, not
    166 traffic from any other application. For example, a PDF file that
    167 connects automatically to a URL will not route its traffic through Tor
    168 if the file is opened with an external application. An open bug ticket
    169 for improving this warning message has more information about the
    170 issue [30].
    171 
    172   [30]: https://bugs.torproject.org/7439
    173 
    174 Upcoming events
    175 ---------------
    176 
    177 Feb 26 18:00 UTC | Tor Weather development meeting
    178                  | #tor-dev, irc.oftc.net
    179                  |
    180 Feb 28 17:00 UTC | Pluggable Transports development meeting
    181                  | #tor-dev, irc.oftc.net
    182                  |
    183 Mar 01 10:00 EST | Andrew @ Boston/Cambridge Countersurveillance DiscoTech
    184                  | Boston, Massachusetts, USA
    185                  | https://surveillance.hackpad.com/BostonCambridge-Countersurveillance-DiscoTech-lpF9SgcyhR2
    186                  |
    187 Mar 03-07        | Tor @ Financial Cryptography and Data Security 2014
    188                  | Barbados
    189                  | http://fc14.ifca.ai/
    190                  |
    191 Mar 05 21:00 UTC | Tails contributors’ meeting
    192                  | #tails-dev, oftc.net
    193                  |
    194 Mar 22-23        | Tor @ LibrePlanet 2014
    195                  | Cambridge, Massachusetts, USA
    196                  | http://libreplanet.org/2014/
    197 
    198 
    199 This issue of Tor Weekly News has been assembled by Lunar, harmony,
    200 Matt Pagan, Nicolas Vigier, Roger Dingledine, and George Kadianakis.
    201 
    202 Want to continue reading TWN? Please help us create this newsletter.
    203 We still need more volunteers to watch the Tor community and report
    204 important news. Please see the project page [31], write down your
    205 name and subscribe to the team mailing list [32] if you want to
    206 get involved!
    207 
    208   [31]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
    209   [32]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
    210 }}}
     5'''Status:''' [https://lists.torproject.org/pipermail/tor-news/2014-February/000034.html Sent]