[TWN team] Recent changes to the wiki pages

[Lunar]

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

version 43
Author: arma
Date:   2014-04-16T04:56:57+00:00

   --

--- version 42
+++ version 43
@@ -96,7 +96,7 @@
 Nick Mathewson in proposal 231 [18].
 
 Finally, hidden service operators are also generating new keys [19].
-Unfortunately, this forces every users of the service to update the
+Unfortunately, this forces every user of the service to update the
 address in their bookmarks or configuration.
 
 As Roger summarized it: “fun times”.

version 42
Author: arma
Date:   2014-04-16T04:53:44+00:00

   send the relay reject mail

--- version 41
+++ version 42
@@ -76,7 +76,7 @@
 them. What is known though are relays that are unfortunately still
 vulnerable. Sina Rabbani has set up a visible list for guards and
 exits [14]. To protect Tor users, directory authority operators have
-started to remove the Valid flag for vulnerable relays [15].
+started to reject descriptors for vulnerable relays [15].
 
 The identity key for directory authorities are kept offline. But they
 are used to certify medium-term signing keys. Roger Dingledine's
@@ -111,7 +111,7 @@
   [12]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004259.html
   [13]: http://charon.persephoneslair.org/~andrea/private/tor-heartbleed-survey/
   [14]: https://encrypted.redteam.net/bleeding_edges/
-  [15]: (XXX -- Roger owes a mail about this ; plan B is to link to consusus-health).
+  [15]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004336.html
   [16]: https://lists.torproject.org/pipermail/tor-dev/2014-April/006663.html
   [17]: https://bugs.torproject.org/11464
   [18]: https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/231-migrate-authority-rsa1024-ids.txt

version 41
Author: arma
Date:   2014-04-16T04:21:21+00:00

   --

--- version 40
+++ version 41
@@ -63,7 +63,7 @@
 Directory authorities can currently tie relay's nickname to its identity
 key with the Named flag. That feature proved to be less helpful than it
 seemed and can subject its users to impersonation attacks. As relays
-switch to new identity key, those who keep the same name will loose
+switch to new identity keys, those who keep the same name will lose
 their Named flag for the next six months. So now seems a good time to
 “throw out the Named and Unnamed flags entirely” [10]. Sebastian Hahn
 acted on the idea and started a draft proposal [11]. 

version 40
Author: arma
Date:   2014-04-16T04:16:57+00:00

   --

--- version 39
+++ version 40
@@ -50,7 +50,7 @@
 “especially from the big relays, and we'll be happier tolerating a
 couple of bumpy days while the network recovers.” [6]. Switching to a
 new relay identity key means that the relay is seen as new [7] to the
-authorities again: they will loose their Guard status and bandwidth
+authorities again: they will lose their Guard status and bandwidth
 measurement. It seems that a number of operators followed the advice, as
 the network lost around 1 Gbit/s of advertised capacity between April
 7th and April 10th [8].



-- 
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.