[TWN team] Recent changes to the wiki pages

[Lunar]

===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/16 ===
===========================================================================

version 31
Author: lunar
Date:   2014-04-22T09:35:52+00:00

   improve on the ancient relays

--- version 30
+++ version 31
@@ -15,27 +15,33 @@
 Cutting out relays running version 0.2.2.x
 ------------------------------------------
 
-As a side note in the current heartbleed discussions Roger Dingledine
-mentioned [1] that besides rejecting heartbleed affected relays,
-also Tor relays running ancient Tor 0.2.2.x have been removed from
-the consensus (#11149) [2]. 
-
-XXX: clarifications at https://lists.torproject.org/pipermail/tor-relays/2014-April/004422.html
-
-Eventually also relays running version prior 0.2.3.16-alpha might be 
-removed from the consensus: "I think 0.2.3.16-alpha's fix of #6033 makes that 
-one a plausible 'not below this one' cutoff." Roger writes in the respective
-Trac entry [3].
-
-Relay operators should always make sure to run a recommended Tor version [4].
-The Tor Weather service [5] can be used by relay operators to get 
-email notifications if an outdated tor version is detected.
-
-[1] https://lists.torproject.org/pipermail/tor-relays/2014-April/004362.html
-[2] https://bugs.torproject.org/11149
-[3] https://bugs.torproject.org/11149#comment:7
-[4] https://consensus-health.torproject.org/#recommendedversions
-[5] https://weather.torproject.org/subscribe/
+Tor relays running ancient Tor 0.2.2.x are scheduled to be removed from
+the consensus [XXX]. The change has already been merged in the
+master branch and will be out with the next Tor 0.2.5 alpha.
+
+Even if most relay operators have been warned, the change has not been
+yet announced widely. But as three directory authorities are already
+not voting for the deprecated versions, the downtime of two others
+while cleaning up after the OpenSSL “heartbleed” issue was sufficient
+to get these relays removed from the consensus [XXX] explained [XXX] Roger
+Dingledine.
+
+Eventually relays running version prior 0.2.3.16-alpha might be removed
+from the consensus. “I think 0.2.3.16-alpha's fix of #6033 makes that
+one a plausible 'not below this one' cutoff”, Roger writes in the
+respective Trac entry [XXX].
+
+Relay operators should always make sure to run a recommended Tor
+version [XXX]. The Tor Weather service [XXX] can be used by relay
+operators to get email notifications if an outdated tor version is
+detected.
+
+ [XXX]: https://bugs.torproject.org/11149
+ [XXX]: https://metrics.torproject.org/network.html?graph=versions&start=2014-04-01&end=2014-04-23#versions
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004422.html
+ [XXX]: https://bugs.torproject.org/11149#comment:7
+ [XXX]: https://consensus-health.torproject.org/#recommendedversions
+ [XXX]: https://weather.torproject.org/subscribe/
 
 Feature XXX
 -----------

version 30
Author: lunar
Date:   2014-04-22T09:25:43+00:00

   write about meek/flashproxy… should probably have been a full entry but
   ENOTIME

--- version 29
+++ version 30
@@ -117,6 +117,18 @@
  [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-April/006718.html
  [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-April/006719.html
 
+Ximin Luo raised [XXX] several points regarding how “indirect” pluggable
+transports like flashproxy [XXX] or meek are currently handled by Tor. Whereas
+obfs3 or ScrambleSuit connect directly to the specified peer transforming the
+data flow along the way, Ximin describes meek and flashproxy as providing “the
+metaphor of connecting to a global homogeneous service”.  The latter being
+“incompatible with the metaphor of connecting to a specific endpoint”.
+Solutions on how to make the design, code, and configuration better are up for
+discussions.
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-April/006689.html
+ [XXX]: http://crypto.stanford.edu/flashproxy/
+
 Nicolas Vigier submitted his status report for March [XXX].
 
  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-April/000510.html
@@ -180,7 +192,6 @@
 
 Possible items:
 
- * Improving the structure of indirect-connection PTs (meek/flashproxy) https://lists.torproject.org/pipermail/tor-dev/2014-April/006689.html
  * Starting Tor from Python using Ctypes improving Sandboxing? https://lists.torproject.org/pipermail/tor-dev/2014-April/006723.html (maybe)
  * Call for testing: UEFI support in Tails https://tails.boum.org/news/test_UEFI/index.en.html
  * Call for testing: Tails 1.0~rc1 https://tails.boum.org/news/test_1.0-rc1/index.en.html



-- 
Your friendly TWN monitoring script

      In case of malfunction, please reach out for lunar at torproject.org
          or for the worst cases, tell weasel at torproject.org to kill me.