Changes between Version 51 and Version 52 of TorWeeklyNews/2014/18


Ignore:
Timestamp:
May 7, 2014, 12:55:21 PM (5 years ago)
Author:
lunar
Comment:

sent

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews/2014/18

    v51 v52  
    33'''Editor:''' Lunar
    44
    5 '''Status:''' Frozen. Only technical and language fixes accepted. New items should go on [wiki:TorWeeklyNews/2014/19 next week's edition].  Expected publication time: 2014-05-07 12:00 UTC.
    6 
    7 '''Subject:''' Tor Weekly News — May 7th, 2014
    8 
    9 {{{
    10 ========================================================================
    11 Tor Weekly News                                            May 7th, 2014
    12 ========================================================================
    13 
    14 Welcome to the eighteenth issue of Tor Weekly News in 2014, the weekly
    15 newsletter that covers what is happening in the Tor community.
    16 
    17 Tor Browser 3.6 is released
    18 ---------------------------
    19 
    20 The long-awaited Tor Browser 3.6 was finally declared stable [1] on
    21 April 29th. Tor Browser 3.6 is the first version to fully integrate
    22 pluggable transports, enabling easier access to the Tor network on
    23 censored networks. The browser is based on the latest Firefox ESR 24.5.0
    24 and includes a new round of security fixes [2].
    25 
    26 When configuring how to access the Tor network, users can now select one
    27 of the included list of “obfs3“ [3] or “fte” [4] bridges. Using
    28 Flashproxy is also an option, but often requires further
    29 configuration [5] on the local firewall and router. Manually specifying
    30 bridges [6] is still an option, now with support for the aforementioned
    31 pluggable transports.
    32 
    33 Many small usability enhancements have been made: Tor error messages are
    34 translated, the wording on several dialog windows has been improved
    35 based on user feedback, and Mac users now install the browser from the
    36 usual disk image format. Turkish localization has also been enabled.
    37 
    38 Read the release announcement for a complete changelog. Be sure to
    39 upgrade [7]!
    40 
    41    [1]: https://blog.torproject.org/blog/tor-browser-36-released
    42    [2]: https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html#firefox24.5
    43    [3]: https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/refs/heads/master:/doc/obfs3/obfs3-protocol-spec.txt
    44    [4]: https://fteproxy.org/
    45    [5]: https://trac.torproject.org/projects/tor/wiki/FlashProxyHowto
    46    [6]: https://bridges.torproject.org/
    47    [7]: https://www.torproject.org/download/download-easy.html
    48 
    49 Tails 1.0 is out
    50 ----------------
    51 
    52 “Version 1.0 is often an important milestone that denotes the maturity
    53 of a free software project. The first public version of what would
    54 become Tails was released on June 23 2009 […]. That was almost five
    55 years ago. Tails 1.0 marks the 36th stable release since then.”
    56 
    57 The release announcement [8] could have not said it better. On top of
    58 the simple idea of having a system entirely running in memory that
    59 guarantees Tor usage for all network connections, Tails has been
    60 extended with an USB installer, automatic upgrades, persistence, support
    61 for Tor bridges, MAC address spoofing, an extensive and translated
    62 documentation and many more features [9].
    63 
    64 Over Tails 0.23, the new version brings security fixes from Firefox and
    65 Tor [10], an updated I2P, several enhancements to the Tor configuration
    66 interface, and the appearance of the new Tails logo [11].
    67 
    68 More details are in the release announcement. For those who have not
    69 made use of the integrated updater, time to download [12] the new
    70 version!
    71 
    72    [8]: https://tails.boum.org/news/version_1.0/
    73    [9]: https://tails.boum.org/doc/about/features/index.en.html
    74   [10]: https://trac.torproject.org/projects/tor/ticket/11464
    75   [11]: https://tails.boum.org/promote/logo/
    76   [12]: https://tails.boum.org/download/
    77 
    78 Monthly status reports for April 2014
    79 -------------------------------------
    80 
    81 The wave of regular monthly reports from Tor project members for the
    82 month of April has begun. Georg Koppen released his report first [13],
    83 followed by reports from Arthur D. Edelstein [14], Sherief Alaa [15],
    84 Karsten Loesing [16], Lunar [17], Nick Mathewson [18], Matt Pagan [19],
    85 Damian Johnson [20], George Kadianakis [21], Pearl Crescent [22], Colin
    86 C. [23], Kevin Dyer [24], Isis Lovecruft [25], Kelley Misata [26], Arlo
    87 Breault [27], and Andrew Lewman [28].
    88 
    89 Lunar also reported on behalf of the help desk [29], Mike Perry for the
    90 Tor Browser team [30], and Arturo Filastò for the OONI team [31].
    91 
    92   [13]: https://lists.torproject.org/pipermail/tor-reports/2014-April/000511.html
    93   [14]: https://lists.torproject.org/pipermail/tor-reports/2014-April/000513.html
    94   [15]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000514.html
    95   [16]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000515.html
    96   [17]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000516.html
    97   [18]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000517.html
    98   [19]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000518.html
    99   [20]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000520.html
    100   [21]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000521.html
    101   [22]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000523.html
    102   [23]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000524.html
    103   [24]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000525.html
    104   [25]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000527.html
    105   [26]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000528.html
    106   [27]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000529.html
    107   [28]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000530.html
    108   [29]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000512.html
    109   [30]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000522.html
    110   [31]: https://lists.torproject.org/pipermail/tor-reports/2014-May/000526.html
    111 
    112 Miscellaneous news
    113 ------------------
    114 
    115 The Tails developers warned [32] that two fake public keys have been
    116 found bearing email addresses associated with the project; do not trust
    117 these keys, or anything they may have been used to sign. You can check
    118 the real keys used to sign Tails software on the Tails website [33].
    119 
    120   [32]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032838.html
    121   [33]: https://tails.boum.org/doc/about/openpgp_keys/
    122 
    123 Erinn Clark alerted [34] users of the Trac-based Tor wiki [35] to the
    124 fact that a bug (now fixed) made it possible to register an account with
    125 an already-taken username, “overwriting the existing user’s password and
    126 thereby taking over the account”. “We recommend users try to login and
    127 if you find you are unable to do so, you can reset your password” on the
    128 appropriate Trac page [36].
    129 
    130   [34]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006809.html
    131   [35]: https://trac.torproject.org
    132   [36]: https://trac.torproject.org/projects/tor/reset_password
    133 
    134 Following up on previous discussions [37] and a proposal [38] on the
    135 topic of how to make hidden services scale, Christopher Baines went on
    136 and implemented a prototype [39], “for one possible design of how to
    137 allow distribution in hidden services”. The code and concrete design is
    138 up for feedback.
    139 
    140   [37]: https://lists.torproject.org/pipermail/tor-dev/2013-October/005556.html
    141   [38]: https://lists.torproject.org/pipermail/tor-dev/2013-October/005674.html
    142   [39]: https://lists.torproject.org/pipermail/tor-dev/2014-April/006788.html
    143 
    144 Daniel Martí sent out [40] a list of proposed revisions — arrived at in
    145 discussion with other developers on IRC — to the now slightly outdated
    146 proposal 140, which forms the basis of his upcoming Google Summer of
    147 Code project to implement consensus diffs and so reduce the amount of
    148 information downloaded hourly by Tor clients. Among the proposals are
    149 support for microdescriptor consensus diffs and a time limit to prevent
    150 the leak of information about when Tor was last used; “ideas about what
    151 might be missing or needing an update are welcome”, wrote Daniel.
    152 
    153   [40]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006792.html
    154 
    155 Alpha releases of Orbot v14 are now available [41] for testing. They
    156 include support for the obfs3 and ScrambleSuit protocols, thanks to
    157 obfsclient [42].
    158 
    159   [41]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032847.html
    160   [42]: https://github.com/yawning/obfsclient
    161 
    162 Griffin Boyce solicited feedback on the first release of Satori [43], an
    163 “app for Google Chrome that distributes circumvention software in a
    164 difficult-to-block way and makes it easy for users to check if it’s been
    165 tampered with in-transit.”
    166 
    167   [43]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032866.html
    168 
    169 Kelley Misata announced on the Tor Blog [44] that this year’s Tor Summer
    170 Dev Meeting will be held between June 29th and July 4th at the French
    171 offices of Mozilla in Paris.
    172 
    173   [44]: https://blog.torproject.org/blog/tor-summer-2014-dev-meeting-hosted-mozilla
    174 
    175 Also on the blog, Andrew Lewman announced [45] that the temporary limit
    176 on donations to the Tor Project through Paypal has now been lifted.
    177 
    178   [45]: https://blog.torproject.org/blog/paypal-account-limits-now-resolved
    179 
    180 Nicolas Vigier announced [46] that the Tor Browser test suite will now
    181 be run automatically when a new build is ready. The results will be
    182 emailed to the tor-qa mailing list.
    183 
    184   [46]: https://lists.torproject.org/pipermail/tor-qa/2014-May/000405.html
    185 
    186 Nick Mathewson suggested [47] that proposal 236 [48], which deals with
    187 the proposed transition to single guard nodes for Tor clients, should
    188 include the retention of multiple guards for directory requests, since
    189 “trusting a single source for the completeness and freshness of your
    190 directory info is suboptimal.”
    191 
    192   [47]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006820.html
    193   [48]: https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/proposals/236-single-guard-node.txt
    194 
    195 Jacob H. Haven, Mikhail Belous, and Noah Rahman each introduced their
    196 Tor-related projects for this year’s Google Summer of Code: Jacob’s
    197 project [49] is titled “A Lightweight Censorship Analyzer for Tor”, and
    198 aims to “allow non-technical users to monitor censorship of Tor
    199 occurring in their country/network”; Mikhail [50] will work to implement
    200 a multicore version of the tor daemon; and Noah plans [51] on
    201 “refactoring Stegotorus more along DRY lines as well as enhancing and
    202 updating various handshaking protocols, and getting it ready to merge in
    203 upstream changes from its originators at SRI.”
    204 
    205   [49]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006808.html
    206   [50]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006817.html
    207   [51]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006821.html
    208 
    209 Thanks to NetCologne [52] and fr33tux [53] for running mirrors of the
    210 Tor Project website!
    211 
    212   [52]: https://lists.torproject.org/pipermail/tor-mirrors/2014-April/000556.html
    213   [53]: https://lists.torproject.org/pipermail/tor-mirrors/2014-April/000553.html
    214 
    215 Frederic Jacobs invited comments [54] on an alternative Tor icon
    216 designed by a friend “for fun”.
    217 
    218   [54]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032839.html
    219 
    220 Tor help desk roundup
    221 ---------------------
    222 
    223 Many users alerted the help desk to a new bug [55] in Tor Browser 3.6
    224 that prevents users from setting a proxy. Developers have said this bug
    225 is related to the introduction of Pluggable Transport support; a new Tor
    226 Browser release addressing this issue is expected this week.
    227 
    228   [55]: https://bugs.torproject.org/11658
    229 
    230 News from Tor StackExchange
    231 ---------------------------
    232 
    233 Tom Ritter wonders how the Exit Probability is calculated [56] and wants
    234 to know if all values add up to 100 %. If anyone knows a good answer,
    235 please don’t hesitate to add it to the question.
    236 
    237   [56]: https://tor.stackexchange.com/q/2041/88
    238 
    239 user1698 wants to extend the number of Tor relays in a circuit, and asks
    240 if it is possible to have one with 5 or 6 nodes [57]. Tom Ritter
    241 suggests that this is only possible when one changes the source code.
    242 There is another question which deals with extending the number of nodes
    243 in a circuit [58]: Steven Murdoch warns the user in his answer that
    244 under some circumstances it might be possible to de-anonymize a person
    245 who is using this technique.  Furthermore alaf discusses the
    246 performance, throughput and anonymity of longer circuits.
    247 
    248   [57]: https://tor.stackexchange.com/q/2039/88
    249   [58]: https://tor.stackexchange.com/q/103/88
    250 
    251 Upcoming events
    252 ---------------
    253 
    254 May  7 19:00 UTC | little-t tor development meeting
    255                  | #tor-dev, irc.oftc.net
    256                  | https://lists.torproject.org/pipermail/tor-dev/2014-March/006616.html
    257                  |
    258 May  8 18:00 CET | “Create a Tor relay!” presentation at Linuxwochen
    259                  | FH Technikum Wien, Vienna, Austria
    260                  | https://cfp.linuxwochen.at/de/LWW14/public/events/108
    261                  |
    262 May  8 20:00 UTC | Tails contributors meeting
    263                  | #tails-dev, irc.oftc.net
    264                  | https://mailman.boum.org/pipermail/tails-dev/2014-May/005654.html
    265                  |
    266 May  9 15:00 UTC | Tor Browser online meeting
    267                  | #tor-dev, irc.oftc.net
    268                  | https://lists.torproject.org/pipermail/tbb-dev/2014-April/000049.html
    269                  |
    270 May  9 16:00 UTC | Pluggable transports online meeting
    271                  | #tor-dev, irc.oftc.net
    272                  | https://lists.torproject.org/pipermail/tor-dev/2014-April/006764.html
    273                  |
    274 May 27-28        | Tor @ Stockholm Internet Forum
    275                  | Stockholm, Sweden
    276                  | http://www.stockholminternetforum.se/
    277 
    278 This issue of Tor Weekly News has been assembled by Lunar, harmony,
    279 Matt Pagan, qbi and the Tails team.
    280 
    281 Want to continue reading TWN? Please help us create this newsletter.
    282 We still need more volunteers to watch the Tor community and report
    283 important news. Please see the project page [59], write down your
    284 name and subscribe to the team mailing list [60] if you want to
    285 get involved!
    286 
    287   [59]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
    288   [60]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
    289 }}}
     5'''Status:''' [https://lists.torproject.org/pipermail/tor-news/2014-May/000044.html Sent]