[TWN team] Recent changes to the wiki pages
Lunar
lunar at torproject.org
Tue Dec 3 12:40:09 UTC 2013
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2013/22 ===
===========================================================================
version 44
Author: lunar
Date: 2013-12-03T11:58:34+00:00
FREEZE
--- version 43
+++ version 44
@@ -1,6 +1,8 @@
''23rd issue of Tor Weekly News. Covering what's happening from November 26th, 2013 to December 3rd, 2013. To be released on December 4th, 2013.''
'''Editor:''' Lunar
+
+'''Status:''' Frozen! New items should go to [wiki:TorWeeklyNews/2013/23 next week's page]. Expected publication time: 2013-12-04 12:00 UTC.
'''Subject:''' Tor Weekly News — December 4th, 2013
version 43
Author: lunar
Date: 2013-12-03T11:56:14+00:00
add numbers, wrap and minor fixes
--- version 42
+++ version 43
@@ -9,191 +9,191 @@
Tor Weekly News December 4th, 2013
========================================================================
-Welcome to the twenty-third issue of Tor Weekly News, the weekly newsletter that
-covers what is happening in the XXX Tor community.
+Welcome to the twenty-third issue of Tor Weekly News, the weekly
+newsletter that covers what is happening in the Tor community.
Next-Generation Hidden Services reached draft proposal state
------------------------------------------------------------
Nick Mathewson has been working on turning a “revamp of the hidden
-services protocol” into a formal proposal [XXX]. Last Saturday, Nick
+services protocol” into a formal proposal [1]. Last Saturday, Nick
blessed the tor-dev mailing list with a post of the current draft for
-proposal 224 [XXX], dubbed “Next-Generation Hidden Services in Tor”.
+proposal 224 [2], dubbed “Next-Generation Hidden Services in Tor”.
Nick currently lists 25 different people who made writing new proposal
possible, and they will be probably some more to add before the proposal
-reach completion. We will spare the
-full list to the reader, but Tor Weekly News' archives [XXX] can attest that
-George Kadianakis deserves a special mention for his repeated efforts to
-move things forward.
-
-The proposal aims to replace “the current rend-spec.txt [XXX], rewritten
-for clarity and for improved design.” The most user visible change
-from the current hidden services is the new address format. In order
-to prevent the enumeration of hidden services, the new protocol uses
-a derives “blinded key” (section 1.3) from Ed25519 master identity
-key. The blinding operation requires to operate on the full key material
-(and not just a truncated hash, as before). With a base 32 encoding of the
+reach completion. We will spare the full list to the reader, but Tor
+Weekly News' archives [3] can attest that George Kadianakis deserves a
+special mention for his repeated efforts to move things forward.
+
+The proposal aims to replace “the current rend-spec.txt [4], rewritten
+for clarity and for improved design.” The most user visible change from
+the current hidden services is the new address format. In order to
+prevent the enumeration of hidden services, the new protocol uses a
+derives “blinded key” (section 1.3) from Ed25519 master identity key.
+The blinding operation requires to operate on the full key material (and
+not just a truncated hash, as before). With a base 32 encoding of the
entire 256 bits (section 1.2), “a new name following this specification
might look like:
a1uik0w1gmfq3i5ievxdm9ceu27e88g6o7pe0rffdw9jmntwkdsd.onion”. Other
encoding might still worth consideration as long as they make valid
hostnames.
-Less visible changes include the departure from RSA1024, DH1024,
-and SHA1 to prefer Ed25519, Curve25519, and SHA256 as the basic crypto
+Less visible changes include the departure from RSA1024, DH1024, and
+SHA1 to prefer Ed25519, Curve25519, and SHA256 as the basic crypto
blocks (section 0.3).
The selection of responsible directories for a hidden service now
-depends on a periodic “collaboratively generated random value”
-provided by the Tor directory authorities. This way the directories
-of a hidden service are not predictable in advance which prevents
-targeted denial of service attacks (see ticket #8244 [XXX] and
-proposal 225 for a possible scheme [XXX]).
+depends on a periodic “collaboratively generated random value” provided
+by the Tor directory authorities. This way the directories of a hidden
+service are not predictable in advance which prevents targeted denial of
+service attacks (see ticket #8244 [5] and proposal 225 for a possible
+scheme [6]).
The new proposal also introduces the possibility of keeping the master
identity key offline (section 1.7).
-The proposal is completely unfinished when it comes to scaling Hidden Services
-to multiple hosts (section 1.5). There have been discussions on this topic [XXX],
-but there is no final decision on what the final scheme should be.
-The problem with naive scaling schemes is that information about the
-number of Hidden Service nodes can get leaked to adversarial clients
-or Introduction Points.
+The proposal is completely unfinished when it comes to scaling Hidden
+Services to multiple hosts (section 1.5). There have been discussions on
+this topic [7], but there is no final decision on what the final scheme
+should be. The problem with naive scaling schemes is that information
+about the number of Hidden Service nodes can get leaked to adversarial
+clients or Introduction Points.
In order to move the proposal forward from the current draft, Nick
Mathewson told the readers: “I'd like to know what doesn't make sense,
-what I need to explain better, and what I need to design better.
-I'd like to fill in the gaps
-and turn this into a more full document. I'd like to answer the open
-questions. Comments are most welcome, especially if they grow into
-improvements.” The document is still sprinkled with many TODO items,
-so feel free to jump in if you want to help!
-
- [XXX] https://gitweb.torproject.org/torspec.git/blob_plain/HEAD:/proposals/001-process.txt
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-November/005877.html
- [XXX] https://blog.torproject.org/category/tags/tor-weekly-news
- [XXX] https://gitweb.torproject.org/torspec.git/blob/refs/heads/master:/rend-spec.txt
- [XXX] https://bugs.torproject.org/8244
- [XXX] https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/225-strawman-shared-rand.txt
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-October/005556.html
+what I need to explain better, and what I need to design better. I'd
+like to fill in the gaps and turn this into a more full document. I'd
+like to answer the open questions. Comments are most welcome, especially
+if they grow into improvements.” The document is still sprinkled with
+many TODO items, so feel free to jump in if you want to help!
+
+ [1] https://gitweb.torproject.org/torspec.git/blob_plain/HEAD:/proposals/001-process.txt
+ [2] https://lists.torproject.org/pipermail/tor-dev/2013-November/005877.html
+ [3] https://blog.torproject.org/category/tags/tor-weekly-news
+ [4] https://gitweb.torproject.org/torspec.git/blob/refs/heads/master:/rend-spec.txt
+ [5] https://bugs.torproject.org/8244
+ [6] https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/225-strawman-shared-rand.txt
+ [7] https://lists.torproject.org/pipermail/tor-dev/2013-October/005556.html
Tor relay operators meeting at 30C3
-----------------------------------
-Moritz Bartl announced [XXX] that a meeting of Tor relay operators and
+Moritz Bartl announced [8] that a meeting of Tor relay operators and
organizations will be held as part of the first day of the 30th Chaos
Communication Congress in Hamburg on the 27th December. He asked major
-relay operators and Torservers.net partner organizations to prepare
-some slides explaining their activities; the German partner
-organization, Zwiebelfreunde e.V., will hold its own meeting directly
-afterwards.
-
- [XXX] https://lists.torproject.org/pipermail/tor-relays/2013-December/003449.html
+relay operators and Torservers.net partner organizations to prepare some
+slides explaining their activities; the German partner organization,
+Zwiebelfreunde e.V., will hold its own meeting directly afterwards.
+
+ [8] https://lists.torproject.org/pipermail/tor-relays/2013-December/003449.html
Monthly status reports for November 2013
----------------------------------------
The wave of regular monthly reports from Tor project members for the
month of November has begun. Pearl Crescent released their report
-first [XXX], followed by reports from Sherief Alaa [XXX], Lunar [XXX],
-Colin C. [XXX], Nick Mathewson [XXX], George Kadianakis [XXX], Arlo Breault [XXX]
-and Ximin Luo [XXX].
-
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-November/000387.html
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-December/000388.html
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-December/000389.html
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-December/000390.html
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-December/000391.html
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-December/000393.html
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-December/000394.html
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-December/000395.html
+first [9], followed by reports from Sherief Alaa [10], Lunar [11], Colin
+C. [12], Nick Mathewson [13], George Kadianakis [14], Arlo Breault [15]
+and Ximin Luo [16].
+
+ [9] https://lists.torproject.org/pipermail/tor-reports/2013-November/000387.html
+ [10] https://lists.torproject.org/pipermail/tor-reports/2013-December/000388.html
+ [11] https://lists.torproject.org/pipermail/tor-reports/2013-December/000389.html
+ [12] https://lists.torproject.org/pipermail/tor-reports/2013-December/000390.html
+ [13] https://lists.torproject.org/pipermail/tor-reports/2013-December/000391.html
+ [14] https://lists.torproject.org/pipermail/tor-reports/2013-December/000393.html
+ [15] https://lists.torproject.org/pipermail/tor-reports/2013-December/000394.html
+ [16] https://lists.torproject.org/pipermail/tor-reports/2013-December/000395.html
Miscellaneous news
------------------
-The first release candidate for Tails 0.22 [XXX] is out. The new version features
-a browser based on Firefox 24 and has reached beta-stage for incremental updates,
-among other things. Tests are highly welcome as always!
-
- [XXX] https://tails.boum.org/news/test_0.22-rc1/
-
-The Tails team called for translators to help with the strings
-both for Tails 0.22 [XXX], as well as for the new
-incremental upgrade software [XXX]. The strings for translation are now
-available in the Tails git repository [XXX], and hopefully should also be
-up on Transifex [XXX] soon.
-
- [XXX] https://mailman.boum.org/pipermail/tails-l10n/2013-December/000774.html
- [XXX] https://mailman.boum.org/pipermail/tails-l10n/2013-November/000771.html
- [XXX] https://git-tails.immerda.ch/iuk/
- [XXX] https://www.transifex.com/projects/p/torproject/
+The first release candidate for Tails 0.22 [17] is out. The new version
+features a browser based on Firefox 24 and has reached beta-stage for
+incremental updates, among other things. Tests are highly welcome as
+always!
+
+ [17] https://tails.boum.org/news/test_0.22-rc1/
+
+The Tails team called for translators to help with the strings both for
+Tails 0.22 [18], as well as for the new incremental upgrade
+software [19]. The strings for translation are now available in the
+Tails git repository [20], and hopefully should also be up on
+Transifex [21] soon.
+
+ [18] https://mailman.boum.org/pipermail/tails-l10n/2013-December/000774.html
+ [19] https://mailman.boum.org/pipermail/tails-l10n/2013-November/000771.html
+ [20] https://git-tails.immerda.ch/iuk/
+ [21] https://www.transifex.com/projects/p/torproject/
Damian Johnson sent out a link to a recording of his talk on the Tor
-ecosystem at TA3M in Seattle [XXX].
-
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-November/005867.html
-
-David Goulet called for assistance with the code-review process for
-the Torsocks 2.0 release candidate, and offered some guidance on
-where to begin [XXX].
-
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-November/005870.html
-
-Erinn Clark and Weasel upgraded the Tor Bug Tracker & Wiki to Trac
-version 1.0 [XXX].
-
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-November/005871.html
-
-intrigeri began [XXX] the compilation of a glossary [XXX] of words that
+ecosystem at TA3M in Seattle [22].
+
+ [22] https://lists.torproject.org/pipermail/tor-dev/2013-November/005867.html
+
+David Goulet called for assistance with the code-review process for the
+Torsocks 2.0 release candidate, and offered some guidance on where to
+begin [23].
+
+ [23] https://lists.torproject.org/pipermail/tor-dev/2013-November/005870.html
+
+Erinn Clark and Peter Palfrader upgraded the Tor Bug Tracker & Wiki to
+Trac version 1.0 [24].
+
+ [24] https://lists.torproject.org/pipermail/tor-dev/2013-November/005871.html
+
+intrigeri began [25] the compilation of a glossary [26] of words that
Tails and its developers use for particular concepts, to assist
contributors who might not be familiar with these special meanings.
- [XXX] https://mailman.boum.org/pipermail/tails-dev/2013-November/004353.html
- [XXX] https://tails.boum.org/contribute/glossary/
+ [25] https://mailman.boum.org/pipermail/tails-dev/2013-November/004353.html
+ [26] https://tails.boum.org/contribute/glossary/
In order to remove “a full database of relays on our already overloaded
metrics machine”, Karsten Loesing is asking for those using the
-“relay-search service” to speak up [XXX] before decommissioning the service
-by the end of the year.
-
- [XXX] https://lists.torproject.org/pipermail/tor-talk/2013-December/031310.html
-
-Philipp Winter followed up on his experiments in exit scanning [XXX] and released
-exitmap [XXX] which uses Stem to control with the tor daemon in creating circuits
-to all exit nodes.
-
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-November/005863.html ;
- [XXX] https://github.com/NullHypothesis/exitmap
-
-A Tor client implementation written in pure Java, Orchid [XXX], has silently reached
-the 1.0 milestone on November 27th. Nathan Freitas looks for comment from the community [XXX]
-as he is “thinking about having Orbot use it by default, and then offering
-ARM and x86 binaries as add-on enhancements.” His main argument is that it
-“would make the core Tor on Android experience more lightweight for client only use.”
-
- [XXX] http://www.subgraph.com/orchid.html
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-November/005884.html
-
-The Electronic Frontier Foundation helped a student group in Iowa convince their
-university they should be allowed to hold discussions about Tor on campus.
-The EFF's open letter to universities [XXX] and their “Myths and Facts About
-Tor” [XXX] document make useful advocacy material.
-
- [XXX] https://www.eff.org/deeplinks/2013/12/open-letter-urging-universities-encourage-conversation-about-online-privacy
- [XXX] https://www.eff.org/document/tor-myths-and-facts
+“relay-search service” to speak up [27] before decommissioning the
+service by the end of the year.
+
+ [27] https://lists.torproject.org/pipermail/tor-talk/2013-December/031310.html
+
+Philipp Winter followed up on his experiments in exit scanning [28] and
+released exitmap [29] which uses Stem to control with the tor daemon in
+creating circuits to all exit nodes.
+
+ [28] https://lists.torproject.org/pipermail/tor-dev/2013-November/005863.html
+ [29] https://github.com/NullHypothesis/exitmap
+
+A Tor client implementation written in pure Java, Orchid [30], has
+silently reached the 1.0 milestone on November 27th. Nathan Freitas
+looks for comment from the community [31] as he is “thinking about
+having Orbot use it by default, and then offering ARM and x86 binaries
+as add-on enhancements.” His main argument is that it “would make the
+core Tor on Android experience more lightweight for client only use.”
+
+ [30] http://www.subgraph.com/orchid.html
+ [31] https://lists.torproject.org/pipermail/tor-dev/2013-November/005884.html
+
+The Electronic Frontier Foundation helped a student group in Iowa
+convince their university they should be allowed to hold discussions
+about Tor on campus. The EFF's open letter to universities [32] and
+their “Myths and Facts About Tor” [33] document make useful advocacy
+material.
+
+ [32] https://www.eff.org/deeplinks/2013/12/open-letter-urging-universities-encourage-conversation-about-online-privacy
+ [33] https://www.eff.org/document/tor-myths-and-facts
Tor help desk roundup
---------------------
-Multiple users asked about using Tor for PC gaming. Tor can only transport
-TCP, which is how web pages are transmitted. Many video games relay on UDP
-or other protocols to transport data because of the lower latency.
-Information these games transport over protocols besides TCP would not be
-sent over Tor. Also any software used with Tor needs to be tested for proxy
-obedience. Untested applications might send information without using
-Tor without the user realizing it even if they appear to be
-correctly configured.
+Multiple users asked about using Tor for PC gaming. Tor can only
+transport TCP, which is how web pages are transmitted. Many video games
+relay on UDP or other protocols to transport data because of the lower
+latency. Information these games transport over protocols besides TCP
+would not be sent over Tor. Also any software used with Tor needs to be
+tested for proxy obedience. Untested applications might send information
+without using Tor without the user realizing it even if they appear to
+be correctly configured.
Upcoming events
---------------
@@ -208,12 +208,10 @@
Want to continue reading TWN? Please help us create this newsletter.
We still need more volunteers to watch the Tor community and report
-important news. Please see the project page [XXX], write down your
-name and subscribe to the team mailing list [XXX] if you want to
+important news. Please see the project page [34], write down your
+name and subscribe to the team mailing list [35] if you want to
get involved!
- [XXX] https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
- [XXX] https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
-}}}
-
-Possible items:
+ [34] https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+ [35] https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
+}}}
version 42
Author: lunar
Date: 2013-12-03T11:52:59+00:00
minor rewording
--- version 41
+++ version 42
@@ -118,7 +118,7 @@
[XXX] https://tails.boum.org/news/test_0.22-rc1/
-intrigeri also called for translators to begin help with the strings
+The Tails team called for translators to help with the strings
both for Tails 0.22 [XXX], as well as for the new
incremental upgrade software [XXX]. The strings for translation are now
available in the Tails git repository [XXX], and hopefully should also be
version 41
Author: lunar
Date: 2013-12-03T11:52:03+00:00
credits
--- version 40
+++ version 41
@@ -203,8 +203,8 @@
| https://events.ccc.de/congress/2013/
-This issue of Tor Weekly News has been assembled by XXX, XXX, and
-XXX.
+This issue of Tor Weekly News has been assembled by Lunar, harmony,
+Matt Pagan, dope457, George Kadianakis and Nick Mathewson.
Want to continue reading TWN? Please help us create this newsletter.
We still need more volunteers to watch the Tor community and report
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2013/23 ===
===========================================================================
version 1
Author: lunar
Date: 2013-12-03T11:58:30+00:00
import template
---
+++ version 1
@@ -0,0 +1,86 @@
+''24th issue of Tor Weekly News. Covering what's happening from December 3rd, 2013 to December 10th, 2013. To be released on December 11th, 2013.''
+
+'''Editor:'''
+
+'''Subject:''' Tor Weekly News — December 11th, 2013
+
+{{{
+========================================================================
+Tor Weekly News December 11th, 2013
+========================================================================
+
+Welcome to the twenty-forth issue of Tor Weekly News, the weekly newsletter that
+covers what is happening in the XXX Tor community.
+
+New Release of XXX
+------------------
+
+XXX: cite specific release date, numbers, and developers responsible
+
+XXX: details about release
+
+ [XXX]
+
+Monthly status reports for XXX month 2013
+-----------------------------------------
+
+The wave of regular monthly reports from Tor project members for the
+month of XXX has begun. XXX released his report first [XXX], followed
+by reports from name 2 [XXX], name 3 [XXX], and name 4 [XXX].
+
+ [XXX]
+ [XXX]
+ [XXX]
+ [XXX]
+
+Miscellaneous news
+------------------
+
+Item 1 with cited source [XXX].
+
+Item 2 with cited source [XXX].
+
+Item 3 with cited source [XXX].
+
+ [XXX]
+ [XXX]
+ [XXX]
+
+Tor help desk roundup
+---------------------
+
+Summary of some questions sent to the Tor help desk.
+
+Vulnerabilities
+---------------
+
+XXX: Reported vulnerabilities [XXX].
+
+ [XXX] vulnerability report source
+
+Upcoming events
+---------------
+
+Jul XX-XX | Event XXX brief description
+ | Event City, Event Country
+ | Event website URL
+ |
+Jul XX-XX | Event XXX brief description
+ | Event City, Event Country
+ | Event website URL
+
+
+This issue of Tor Weekly News has been assembled by XXX, XXX, and
+XXX.
+
+Want to continue reading TWN? Please help us create this newsletter.
+We still need more volunteers to watch the Tor community and report
+important news. Please see the project page [XXX], write down your
+name and subscribe to the team mailing list [XXX] if you want to
+get involved!
+
+ [XXX] https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+ [XXX] https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
+}}}
+
+Possible items:
--
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