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


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

fix refs

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews/2014/8

    v52 v53  
    6464------------------
    6565
    66 Karsten Loesing announced an IRC meeting to discuss the next steps for
     66Karsten Loesing announced [14] an IRC meeting to discuss the next steps for
    6767the rewrite of Tor Weather, to be held on the OFTC #tor-dev channel on
    6868Wednesday 26th February at 18:00 UTC. “Topics include reporting progress
    6969made since the last meeting two weeks ago, making plans for the next
    70 week, and possibly turning this project into a GSoC project” [14].
     70week, and possibly turning this project into a GSoC project”.
    7171
    7272  [14]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006299.html
    7373
    74 Nick Mathewson announced the start of a weekly Tor developer’s meeting,
     74Nick Mathewson announced [15] the start of a weekly Tor developer’s meeting,
    7575to be held on the OFTC #tor-dev channel, “for working on the program
    7676‘tor’. (This won’t cover all the other programs developed under the Tor
    77 umbrella.)” [15].
     77umbrella.)”.
    7878
    7979  [15]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006282.html
    8080
    81 The Tails developers will be holding their next contributors’ meeting on
     81The Tails developers will be holding [16] their next contributors’ meeting on
    8282the OFTC #tails-dev channel at 9pm UTC on March 5th; “everyone
    83 interested in contributing to Tails is welcome.” [16].
     83interested in contributing to Tails is welcome.”.
    8484
    8585  [16]: https://mailman.boum.org/pipermail/tails-dev/2014-February/004934.html
     
    101101
    102102Responding to a message from someone interested in writing a DNS-based
    103 pluggable transport, George Kadianakis suggested several ways in which
    104 the existing obfsproxy code could be reworked to accommodate this [21].
     103pluggable transport, George Kadianakis suggested [21] several ways in which
     104the existing obfsproxy code could be reworked to accommodate this.
    105105
    106106  [21]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006250.html
    107107
    108 George also recommended that operators of obfs3 or ScrambleSuit bridges
     108George also recommended [22] that operators of obfs3 or ScrambleSuit bridges
    109109install the python-gmpy package on their relays, as it can significantly
    110 increase the speed of some cryptographic operations [22].
     110increase the speed of some cryptographic operations.
    111111
    112112  [22]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003951.html
    113113
    114 Jens Kubieziel wrote up the results of an attempt to determine whether
     114Jens Kubieziel wrote up [23] the results of an attempt to determine whether
    115115the recent transition between the TAP and NTor handshake protocols is
    116 connected to some users’ reports of hidden service unavailability [23].
     116connected to some users’ reports of hidden service unavailability.
    117117
    118118  [23]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006260.html
    119119
    120 Max Jakob Maass published the preliminary results of a test in which the
     120Max Jakob Maass published [24] the preliminary results of a test in which the
    121121RIPE Atlas measurement API was used to retrieve the SSL certificate of
    122122torproject.org from as many countries as possible in order to detect
    123123attempted attacks or censorship, and wondered whether it might be worth
    124 running such a test on a regular basis [24].
     124running such a test on a regular basis.
    125125
    126126  [24]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032173.html
     
    129129Project’s website, Moritz Bartl wrote up a list of proposed volunteer
    130130categories that was the fruit of a brainstorming session at the Tor
    131 developers’ meeting, and asked for suggestions of “obvious” missing
     131developers’ meeting, and asked for suggestions [25] of “obvious” missing
    132132sections, as well as “acceptably-licensed” graphics that could serve as
    133 icons for each category [25].
     133icons for each category.
    134134
    135135  [25]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032176.html
     
    145145  [27]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/UserStories
    146146
    147 Yawning Angel sent out a draft of a proposal to “extend the SOCKS5
     147Yawning Angel sent out [28] a draft of a proposal to “extend the SOCKS5
    148148protocol when communicating with pluggable transports to allow passing
    149149more per-bridge meta-data to the transport and returning more meaningful
    150 connection failure response codes back to Tor” [28].
     150connection failure response codes back to Tor”.
    151151
    152152  [28]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006300.html
    153153
    154 Josh Ayers wrote to the Tor-ramdisk list suggesting possible ways to
     154Josh Ayers wrote [29] to the Tor-ramdisk list suggesting possible ways to
    155155ensure that sufficient entropy is available to the kernel by the time
    156 tor-ramdisk generates its long-term keys [29].
     156tor-ramdisk generates its long-term keys.
    157157
    158158  [29]: http://opensource.dyc.edu/pipermail/tor-ramdisk/2014-February/000119.html