[TWN team] Recent changes to the wiki pages

[Lunar]

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

version 50
Author: harmony
Date:   2014-08-19T16:20:53+00:00

   some other fixes

--- version 49
+++ version 50
@@ -76,23 +76,22 @@
 thinking using long strings of random bits. Initially, they made it
 possible to understand what was happening in the network more easily,
 and to designate a specific relay in an abbreviated way. Having two
-relays with the same nickname in the whole network is not really
-problematic when one is looking at nodes, or a list in Globe [10], as
-relays can always be differentiated by their IP addresses or identity
-keys.
+relays in the network with the same nickname is not really problematic
+when one is looking at nodes, or a list in Globe [10], as relays can
+always be differentiated by their IP addresses or identity keys.
 
 But complications arise when nicknames are used to specify one relay to
 the exclusion of another. If the wrong relay gets selected, it can
-become a security risk. Even if real efforts [11] have been made to
+become a security risk. Even though real efforts [11] have been made to
 improve the situation, properly enforcing uniqueness has always been
-problematic and a burden for the few directory authorities that handle
+problematic, and a burden for the few directory authorities that handle
 naming. 
 
 Back in April, the “Heartbleed” bug [12] forced many relays to switch to
 a new identity key, thus losing their “Named” flag. Because this meant
-that anyone addressing relays with nickname would now have a hard time
-continuing to do so, Sebastian Hahn decided to use the opportunity to
-get rid of the idea entirely [13].
+that anyone designating relays by their nickname would now have a hard
+time continuing to do so, Sebastian Hahn decided to use the opportunity
+to get rid of the idea entirely [13].
 
 This week, Sebastian wrote [14]: “Code review down to 0.2.3.x has shown
 that the naming-related code hasn’t changed much at all, and no issues
@@ -140,7 +139,7 @@
 
 Nick Mathewson asked for comments [18] on Trunnel, “a little tool to
 automatically generate binary encoding and parsing code based on C-like
-structure descriptions” intended to prevent Heartbleed-style
+structure descriptions” intended to prevent “Heartbleed”-style
 vulnerabilities from creeping into Tor’s binary-parsing code in C. “My
 open questions are: Is this a good idea? Is it a good idea to use this
 in Tor? Are there any tricky bugs left in the generated code? What am I


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

version 5
Author: lunar
Date:   2014-08-19T16:52:33+00:00

   add item

--- version 4
+++ version 5
@@ -98,3 +98,4 @@
   * ''I (dcf) didn't see this one, so I can't say anything about it.''\\
     [https://defcon.org/html/defcon-22/dc-22-speakers.html#Metacortex Touring the Darkside of the Internet. An Introduction to Tor, Darknets, and Bitcoin] by Metacortex and Grifter.
 * ooniprobe 1.1.0 is out https://lists.torproject.org/pipermail/ooni-dev/2014-August/000147.html
+* tips to exit relay operators offering port 25 https://lists.torproject.org/pipermail/tor-relays/2014-August/005168.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.