[TWN team] Recent changes to the wiki pages
Lunar
lunar at torproject.org
Tue Sep 10 14:40:07 UTC 2013
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2013/10 ===
===========================================================================
version 68
Author: karsten
Date: 2013-09-10T13:53:20+00:00
Minor language fixes.
--- version 67
+++ version 68
@@ -19,8 +19,8 @@
There are now confirmations [1] that the sudden influx of Tor clients
which started mid-August [2] is indeed coming from a botnet. “I guess
-all that work we’ve been doing on scalability was a good idea” wrote
-Roger Dingledine wrote in a blog post about “how to handle millions of
+all that work we’ve been doing on scalability was a good idea,” wrote
+Roger Dingledine in a blog post about “how to handle millions of
new Tor clients” [3].
On September 5th, Roger Dingledine announced the release of the third
@@ -67,12 +67,12 @@
tor-talk mailing list to discuss Tor cryptography.
A lot of what has been written is speculative at this point. But some
-have raised concerns [12] about 1024 bit Diffie-Helmank key
-exchange [13]. This has already been adressed with the introduction of
+have raised concerns [12] about 1024 bit Diffie-Hellman key
+exchange [13]. This has already been addressed with the introduction of
the “ntor” handshake [14] in 0.2.4 and Nick Mathewson encourages
everybody to upgrade [15].
-Another thread [16] prompted Nick to summarize [17] its views on the
+Another thread [16] prompted Nick to summarize [17] his views on the
future of Tor cryptography. Regarding public keys, “with Tor 0.2.4,
forward secrecy uses 256-bit ECC, which is certainly better, but
RSA-1024 is still used in some places for signatures. I want to fix all
@@ -91,8 +91,8 @@
here before implementation.
A third question was raised [22] regarding the trust in algorithms
-certified by the US NIST [23]. Nick speculations put aside, he also
-emphasised that several NIST algorithms were “hard to implement
+certified by the US NIST [23]. Nick's speculations put aside, he also
+emphasized that several NIST algorithms were “hard to implement
correctly” [24].
Nick also plans to change more algorithms [25]: “Over the 0.2.5 series,
@@ -138,7 +138,7 @@
makes it neither very user-friendly to set up and run, nor extensible to
cover new use cases.”
-The specification lay out the various requirements for the new tool, and
+The specification lays out the various requirements for the new tool, and
details several experiments like visiting high profile websites with an
automated graphical web browser, downloading static files, crafting a
canonical web page, measuring hidden service performance, and checking
@@ -186,7 +186,7 @@
Not all new Tor users are computer programs! According to their latest
report [42], Tails is now booted twice as much as six months ago (from
-100 865 to 190 521 connections to the security feed).
+100,865 to 190,521 connections to the security feed).
[42] https://lists.torproject.org/pipermail/tor-reports/2013-September/000336.html
@@ -207,7 +207,7 @@
[47] https://lists.torproject.org/pipermail/tor-dev/2013-September/005409.html
[48] https://lists.torproject.org/pipermail/tor-dev/2013-September/005412.html
-Damian Johnson anounced [49] he had completed the rewrite of DocTor in
+Damian Johnson announced [49] he had completed the rewrite of DocTor in
Python [50], “a service that pulls hourly consensus information and
checks it for a host of issues (directory authority outages, expiring
certificates, etc). In the case of a problem it notifies
@@ -236,7 +236,7 @@
For the upgrade of tor to the 0.2.4.x series in Tails, a tester spotted
a regression while “playing with an ISO built from experimental, thanks
-to our Jenkins autobuilder” [56]. This mark a significant milestone in
+to our Jenkins autobuilder” [56]. This marks a significant milestone in
the work on automated builds [57] done by the several member of the
Tails team in the course of the last year!
@@ -255,7 +255,7 @@
[60] https://crypto.stanford.edu/flashproxy/
Marek Majkowski reported [61] on how one can use his fluxcapacitor
-tool [62] to get a test Tor network started with Chutney [63] ready is
+tool [62] to get a test Tor network started with Chutney [63] ready in
only 6.5 seconds. A vast improvement over the 5 minutes he initially had
to wait [64]!
@@ -265,7 +265,7 @@
[64] https://lists.torproject.org/pipermail/tor-dev/2013-September/005413.html
Eugen Leitl drew attention [65] to a new research paper which aims to
-analyse content and popularity of Hidden Services by Alex Biryukov, Ivan
+analyze content and popularity of Hidden Services by Alex Biryukov, Ivan
Pustogarov, and Ralf-Philipp Weinmann from University of
Luxembourg [66].
@@ -299,11 +299,11 @@
-----------------------
Tor is about protecting everyone’s freedom and privacy. There are many
-way to help [69] but getting involved in such a busy community can be
+ways to help [69] but getting involved in such a busy community can be
daunting. Here’s a selection of tasks on which one can get started:
Get tor to log the source of control port connection [70]. It would help
-developping controller applications or libraries (like Stem [71]) to
+developing controller applications or libraries (like Stem [71]) to
know which program is responsible for a given access to the control
facilities of the tor daemon. Knowledge required: C programming, basic
understanding of network sockets.
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2013/10 ===
===========================================================================
version 68
Author: karsten
Date: 2013-09-10T13:53:20+00:00
Minor language fixes.
--- version 67
+++ version 68
@@ -19,8 +19,8 @@
There are now confirmations [1] that the sudden influx of Tor clients
which started mid-August [2] is indeed coming from a botnet. “I guess
-all that work we’ve been doing on scalability was a good idea” wrote
-Roger Dingledine wrote in a blog post about “how to handle millions of
+all that work we’ve been doing on scalability was a good idea,” wrote
+Roger Dingledine in a blog post about “how to handle millions of
new Tor clients” [3].
On September 5th, Roger Dingledine announced the release of the third
@@ -67,12 +67,12 @@
tor-talk mailing list to discuss Tor cryptography.
A lot of what has been written is speculative at this point. But some
-have raised concerns [12] about 1024 bit Diffie-Helmank key
-exchange [13]. This has already been adressed with the introduction of
+have raised concerns [12] about 1024 bit Diffie-Hellman key
+exchange [13]. This has already been addressed with the introduction of
the “ntor” handshake [14] in 0.2.4 and Nick Mathewson encourages
everybody to upgrade [15].
-Another thread [16] prompted Nick to summarize [17] its views on the
+Another thread [16] prompted Nick to summarize [17] his views on the
future of Tor cryptography. Regarding public keys, “with Tor 0.2.4,
forward secrecy uses 256-bit ECC, which is certainly better, but
RSA-1024 is still used in some places for signatures. I want to fix all
@@ -91,8 +91,8 @@
here before implementation.
A third question was raised [22] regarding the trust in algorithms
-certified by the US NIST [23]. Nick speculations put aside, he also
-emphasised that several NIST algorithms were “hard to implement
+certified by the US NIST [23]. Nick's speculations put aside, he also
+emphasized that several NIST algorithms were “hard to implement
correctly” [24].
Nick also plans to change more algorithms [25]: “Over the 0.2.5 series,
@@ -138,7 +138,7 @@
makes it neither very user-friendly to set up and run, nor extensible to
cover new use cases.”
-The specification lay out the various requirements for the new tool, and
+The specification lays out the various requirements for the new tool, and
details several experiments like visiting high profile websites with an
automated graphical web browser, downloading static files, crafting a
canonical web page, measuring hidden service performance, and checking
@@ -186,7 +186,7 @@
Not all new Tor users are computer programs! According to their latest
report [42], Tails is now booted twice as much as six months ago (from
-100 865 to 190 521 connections to the security feed).
+100,865 to 190,521 connections to the security feed).
[42] https://lists.torproject.org/pipermail/tor-reports/2013-September/000336.html
@@ -207,7 +207,7 @@
[47] https://lists.torproject.org/pipermail/tor-dev/2013-September/005409.html
[48] https://lists.torproject.org/pipermail/tor-dev/2013-September/005412.html
-Damian Johnson anounced [49] he had completed the rewrite of DocTor in
+Damian Johnson announced [49] he had completed the rewrite of DocTor in
Python [50], “a service that pulls hourly consensus information and
checks it for a host of issues (directory authority outages, expiring
certificates, etc). In the case of a problem it notifies
@@ -236,7 +236,7 @@
For the upgrade of tor to the 0.2.4.x series in Tails, a tester spotted
a regression while “playing with an ISO built from experimental, thanks
-to our Jenkins autobuilder” [56]. This mark a significant milestone in
+to our Jenkins autobuilder” [56]. This marks a significant milestone in
the work on automated builds [57] done by the several member of the
Tails team in the course of the last year!
@@ -255,7 +255,7 @@
[60] https://crypto.stanford.edu/flashproxy/
Marek Majkowski reported [61] on how one can use his fluxcapacitor
-tool [62] to get a test Tor network started with Chutney [63] ready is
+tool [62] to get a test Tor network started with Chutney [63] ready in
only 6.5 seconds. A vast improvement over the 5 minutes he initially had
to wait [64]!
@@ -265,7 +265,7 @@
[64] https://lists.torproject.org/pipermail/tor-dev/2013-September/005413.html
Eugen Leitl drew attention [65] to a new research paper which aims to
-analyse content and popularity of Hidden Services by Alex Biryukov, Ivan
+analyze content and popularity of Hidden Services by Alex Biryukov, Ivan
Pustogarov, and Ralf-Philipp Weinmann from University of
Luxembourg [66].
@@ -299,11 +299,11 @@
-----------------------
Tor is about protecting everyone’s freedom and privacy. There are many
-way to help [69] but getting involved in such a busy community can be
+ways to help [69] but getting involved in such a busy community can be
daunting. Here’s a selection of tasks on which one can get started:
Get tor to log the source of control port connection [70]. It would help
-developping controller applications or libraries (like Stem [71]) to
+developing controller applications or libraries (like Stem [71]) to
know which program is responsible for a given access to the control
facilities of the tor daemon. Knowledge required: C programming, basic
understanding of network sockets.
--
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.
More information about the news-team
mailing list