[TWN team] Recent changes to the wiki pages

Lunar lunar at torproject.org
Tue Oct 22 15:00:29 UTC 2013


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

version 36
Author: asn
Date:   2013-10-22T14:14:10+00:00

   credit where it's due always

--- version 35
+++ version 36
@@ -186,7 +186,7 @@
 
 
 This issue of Tor Weekly News has been assembled by Lunar, Matt Pagan,
-dope457 and George Kadianakis.
+dope457, George Kadianakis and velope.
 
 Want to continue reading TWN? Please help us create this newsletter.
 We still need more volunteers to watch the Tor community and report

version 35
Author: phw
Date:   2013-10-22T14:02:39+00:00

   Fix a set of minor syntactical and semantical issues.

--- version 34
+++ version 35
@@ -36,20 +36,20 @@
 much effort into making it easy [5] for researchers to analyze Tor.” In
 his writing Roger highlights the finding of three papers. Two of them
 published at WPES 2012 and Oakland 2013, and another upcoming at
-CCS2013.
+CCS 2013.
 
-These research efforts highlighted several deffiencies way Tor handles
+These research efforts highlighted several issues in the way Tor handles
 entry guards. Roger details five complementary fixes: using fewer
 guards, keeping the same guards for longer, better handling of brief
 unreachability of a guard, making the network bigger, and smarter
 assignment of the guard flag to relays. Some will require further
-research to identify the best solution. There’s also other aspects
+research to identify the best solution. There are also other aspects
 regarding systems which don’t currently record guards such as Tails, how
-pluggable transports could prevent attackers from recognizing Tor users,
+pluggable transports could prevent attackers from recognising Tor users,
 or enhancing measurements from the bandwidth authorities…
 
 The whole blog post is insightful and is a must read for everyone who
-wish to better understand some of Tor’s risk mitigation strategies. It
+wishes to better understand some of Tor’s risk mitigation strategies. It
 is also full of little and big things where you could make a difference!
 
    [1] https://blog.torproject.org/blog/improving-tors-anonymity-changing-guard-parameters
@@ -61,10 +61,10 @@
 Hidden Service research
 -----------------------
 
-George Kadianakis posted a list of items that need work on the Hidden
-Service area [6]. I Despite not exhaustive, the list contains many items
-that might help with upgrading the Hidden Service design, be it around
-security, performance, guard issues or “petname” systems.
+George Kadianakis posted a list of items that need work in the Hidden
+Service area [6]. Despite not being exhaustive, the list contains many
+items that might help with upgrading the Hidden Service design, be it
+around security, performance, guard issues or “petname” systems.
 
 Help and comments are welcome!
 
@@ -83,8 +83,8 @@
 thus a good time to gather usability issues in existing OTR clients.
 
 Mike Perry kicked off the discussion [10] by pointing out several
-defiencies regarding problems with multiple clients, key management
-issues, and other sub-optimal behaviours.
+deficiencies regarding problems with multiple clients, key management
+issues, and other sub-optimal behaviour.
 
 Ian Goldberg — original author of the pervasive OTR plugin for Pidgin —
 pointed out [11] that at least one of the behaviour singled out by Mike
@@ -128,7 +128,7 @@
 Tails has issued a call for testing [12] of its upcoming 0.21 release.
 The new version contains two security fixes regarding access to the Tor
 control port and persistent settings [13] among other improvements and
-package updates [14]. “Test wildly!” as the Tails team wrote it.
+package updates [14]. “Test wildly!” as the Tails team wrote.
 
   [12] https://tails.boum.org/news/test_0.21-rc1/
   [13] https://git-tails.immerda.ch/tails/plain/wiki/src/doc/first_steps/persistence/upgrade.mdwn?h=bugfix/safer-persistence
@@ -147,7 +147,7 @@
 
 Ximin Luo has been the first to create a ticket with 5 digits [18] on
 Tor tracker. At the current rate, ticket #20000 should happen by the end
-of 2015… Or will the project continued growth make this happen sooner?
+of 2015… Or will the project’s continued growth make this happen sooner?
 
   [18] https://bugs.torproject.org/10000
 

version 34
Author: lunar
Date:   2013-10-22T13:35:31+00:00

   FREEZE

--- version 33
+++ version 34
@@ -1,6 +1,8 @@
 ''Seventeenth issue of Tor Weekly News. Covering what's happening from October 15th, 2013 to October 22th, 2013. To be released on October 23th, 2013.''
 
 '''Editor:''' Lunar
+
+'''Status:''' FROZEN! Publication expected around 2013-05-22 12:00 UTC. New items are for [wiki:TorWeeklyNews/2013/17 next week's edition].
 
 '''Subject:''' Tor Weekly News — October 23th, 2013
 

version 33
Author: lunar
Date:   2013-10-22T13:34:13+00:00

   word wrap

--- version 32
+++ version 33
@@ -12,42 +12,42 @@
 Welcome to the seventeenth issue of Tor Weekly News, the weekly
 newsletter that covers what is happening in the guarding Tor community.
 
-Tor's anonymity and guards parameters
+Tor’s anonymity and guards parameters
 -------------------------------------
 
 In a lengthly blog post [1], Roger Dingledine looked back on three
 research papers published in the past year. Some of them have been
-covered and most of the time misunderstood by the press. A good recap
-of the research problems, what the findings mean and possible solutions
+covered and most of the time misunderstood by the press. A good recap of
+the research problems, what the findings mean and possible solutions
 hopefully will help everyone understand better.
 
-Introduced in 2005 [2], entry guards were added to recognise that
-“some circuits are going to be compromised, but it's better to increase
-your probability of having no compromised circuits at the expense of
-also increasing the proportion of your circuits that will be compromised
-if any of them are.” Roger “originally picked ‘one or two months’ for
-guard rotation” but the initial parameters called for more in-depth
+Introduced in 2005 [2], entry guards were added to recognise that “some
+circuits are going to be compromised, but it’s better to increase your
+probability of having no compromised circuits at the expense of also
+increasing the proportion of your circuits that will be compromised if
+any of them are.” Roger “originally picked ‘one or two months’ for guard
+rotation” but the initial parameters called for more in-depth
 research [3].
 
-That call was heard by “the Tor research community [4], and it's great
+That call was heard by “the Tor research community [4], and it’s great
 that Tor gets such attention. We get this attention because we put so
-much effort into making it easy [5] for researchers to analyze Tor.”
-In his writing Roger highlights the finding of three papers. Two of them
+much effort into making it easy [5] for researchers to analyze Tor.” In
+his writing Roger highlights the finding of three papers. Two of them
 published at WPES 2012 and Oakland 2013, and another upcoming at
 CCS2013.
 
 These research efforts highlighted several deffiencies way Tor handles
 entry guards. Roger details five complementary fixes: using fewer
-guards, keeping the same guards for longer, better handling of
-brief unreachability of a guard, making the network bigger, and smarter
+guards, keeping the same guards for longer, better handling of brief
+unreachability of a guard, making the network bigger, and smarter
 assignment of the guard flag to relays. Some will require further
-research to identify the best solution. There's also other aspects
-regarding systems which don't currently record guards such as Tails, how
+research to identify the best solution. There’s also other aspects
+regarding systems which don’t currently record guards such as Tails, how
 pluggable transports could prevent attackers from recognizing Tor users,
 or enhancing measurements from the bandwidth authorities…
 
 The whole blog post is insightful and is a must read for everyone who
-wish to better understand some of Tor's risk mitigation strategies. It
+wish to better understand some of Tor’s risk mitigation strategies. It
 is also full of little and big things where you could make a difference!
 
    [1] https://blog.torproject.org/blog/improving-tors-anonymity-changing-guard-parameters
@@ -60,9 +60,9 @@
 -----------------------
 
 George Kadianakis posted a list of items that need work on the Hidden
-Service area [6]. I Despite not exhaustive, the list contains many
-items that might help with upgrading the Hidden Service design, be it
-around security, performance, guard issues or “petname” systems.
+Service area [6]. I Despite not exhaustive, the list contains many items
+that might help with upgrading the Hidden Service design, be it around
+security, performance, guard issues or “petname” systems.
 
 Help and comments are welcome!
 
@@ -72,9 +72,9 @@
 ----------------------------------------
 
 The consensus after the first round of discussions and research done in
-the prospect of providing a new secure instant-messaging Tor bundle [7] is to
-use Mozilla Instantbird at its core. Arlo Breault sent out a
-draft plan [8] on how to do so.
+the prospect of providing a new secure instant-messaging Tor bundle [7]
+is to use Mozilla Instantbird at its core. Arlo Breault sent out a draft
+plan [8] on how to do so.
 
 Instantbird currently lacks a core feature to turn it into the Tor
 Messenger: support for the OTR [9] protocol for encrypted chat. Now is
@@ -86,12 +86,12 @@
 
 Ian Goldberg — original author of the pervasive OTR plugin for Pidgin —
 pointed out [11] that at least one of the behaviour singled out by Mike
-was “done on purpose. The thing it's trying to prevent is that Alice
-and Bob are chatting, and Bob ends OTR just before Alice hits Enter on
-her message. If Alice's client went to "Not private" instead of
-"Finished", Alice's message would be sent in the clear, which is
-undesirable.  Switching to "Finished" makes Alice have to actively
-acknowledge that the conversation is no longer secure.”
+was “done on purpose. The thing it’s trying to prevent is that Alice and
+Bob are chatting, and Bob ends OTR just before Alice hits Enter on her
+message. If Alice’s client went to ‘Not private’ instead of ‘Finished’,
+Alice’s message would be sent in the clear, which is undesirable.
+Switching to ‘Finished’ makes Alice have to actively acknowledge that
+the conversation is no longer secure.”
 
 This tradeoff is a good example of how designing usable and secure user
 interfaces can be hard. Usability, in itself, is an often overlooked
@@ -106,68 +106,71 @@
 Tor Help Desk Roundup
 ---------------------
 
-The Tor Help Desk continues to be bombarded with help requests from users
-behind university proxies who cannot use ORPort bridges or the Pluggable 
-Transports Browser to circumvent their network's firewall. Although the 
-cases are not all the same, bridges on port 443 or port 80 do not always 
-suffice to circumvent such proxies. 
+The Tor Help Desk continues to be bombarded with help requests from
+users behind university proxies who cannot use ORPort bridges or the
+Pluggable Transports Browser to circumvent their network’s firewall.
+Although the cases are not all the same, bridges on port 443 or port 80
+do not always suffice to circumvent such proxies. 
 
-Ubuntu 13.10 (Saucy Salamander) was released this week. One user reported 
-their Tor Browser Bundle behaving unusually after updating their Ubuntu 
-operating system. This issue was resolved by switching to the Tor Browser 
-Bundle 3. Another user asked when Tor APT repositories would have packages 
-for Saucy Salamander. Since then, packages for the latest version of
-Ubuntu have been made available from the usual deb.torproject.org. 
+Ubuntu 13.10 (Saucy Salamander) was released this week. One user
+reported their Tor Browser Bundle behaving unusually after updating
+their Ubuntu operating system. This issue was resolved by switching to
+the Tor Browser Bundle 3. Another user asked when Tor APT repositories
+would have packages for Saucy Salamander. Since then, packages for the
+latest version of Ubuntu have been made available from the usual
+deb.torproject.org. 
 
 Miscellaneous news
 ------------------
 
-Tails has issued a call for testing [12] of its upcoming 0.21 release. The
-new version contains two security fixes regarding access to the Tor control
-port and persistent settings [13] among other improvements and package
-updates [14]. “Test wildly!” as the Tails team wrote it.
+Tails has issued a call for testing [12] of its upcoming 0.21 release.
+The new version contains two security fixes regarding access to the Tor
+control port and persistent settings [13] among other improvements and
+package updates [14]. “Test wildly!” as the Tails team wrote it.
 
   [12] https://tails.boum.org/news/test_0.21-rc1/
   [13] https://git-tails.immerda.ch/tails/plain/wiki/src/doc/first_steps/persistence/upgrade.mdwn?h=bugfix/safer-persistence
   [14] https://git-tails.immerda.ch/tails/plain/debian/changelog?id=0.21-rc1
 
-Andrew Lewman was invited to speak at SECURE Poland 2013 [15] and sent
-a report on his trip [16] to Warsaw.
+Andrew Lewman was invited to speak at SECURE Poland 2013 [15] and sent a
+report on his trip [16] to Warsaw.
 
   [15] http://www.secure.edu.pl/
   [16] https://lists.torproject.org/pipermail/tor-reports/2013-October/000364.html
 
-Tails developers are looking for Mac and PC hardware with UEFI [17]. If you have
-some spare hardware, please consider a donation!
+Tails developers are looking for Mac and PC hardware with UEFI [17]. If
+you have some spare hardware, please consider a donation!
 
   [17] https://tails.boum.org/news/Mac_and_PC_UEFI_hardware_needed/index.en.html
 
-Ximin Luo has been the first to create a ticket with 5 digits [18] on Tor
-tracker. At the current rate, ticket #20000 should happen by the end of 2015…
-Or will the project continued growth make this happen sooner?
+Ximin Luo has been the first to create a ticket with 5 digits [18] on
+Tor tracker. At the current rate, ticket #20000 should happen by the end
+of 2015… Or will the project continued growth make this happen sooner?
 
   [18] https://bugs.torproject.org/10000
 
-Roger Dingledine reported [19] on his activities for September and October.
-Arturo Filastò also reported [20] on his September.
+Roger Dingledine reported [19] on his activities for September and
+October.  Arturo Filastò also reported [20] on his September.
 
   [19] https://lists.torproject.org/pipermail/tor-reports/2013-October/000365.html
   [20] https://lists.torproject.org/pipermail/tor-reports/2013-October/000366.html
 
-Runa Sandvik continues her work on the new, more comprehensible Tor User Manual [21].
-The first draft is already out [22]. Please review and contribute.
+Runa Sandvik continues her work on the new, more comprehensible Tor User
+Manual [21]. The first draft is already out [22]. Please review and
+contribute.
 
   [21] https://lists.torproject.org/pipermail/tor-dev/2013-October/005649.html
   [22] https://trac.torproject.org/projects/tor/ticket/5811
 
-Aaron published a branch with his work on a Tor exit scanner based on OONI [23].
+Aaron published a branch with his work on a Tor exit scanner based on
+OONI [23].
 
   [23] https://github.com/TheTorProject/ooni-probe/tree/feature/tor_test_template
 
 Upcoming events
 ---------------
 
-Oct 25    | Matt @ EPIC and Public Citizen's CryptoParty 
+Oct 25    | Matt @ EPIC and Public Citizen’s CryptoParty 
           | Washington, DC, USA
           | https://epic.org/events/cryptoparty/
           |
@@ -185,10 +188,9 @@
 
 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 [24], write down your
-name and subscribe to the team mailing list [25] if you want to
-get involved!
+important news. Please see the project page [24], write down your name
+and subscribe to the team mailing list [25] if you want to get involved!
 
   [24] https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
   [25] https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
-}}}+}}}

version 32
Author: lunar
Date:   2013-10-22T13:31:44+00:00

   add adjective for this week

--- version 31
+++ version 32
@@ -10,7 +10,7 @@
 ========================================================================
 
 Welcome to the seventeenth issue of Tor Weekly News, the weekly
-newsletter that covers what is happening in the XXX Tor community.
+newsletter that covers what is happening in the guarding Tor community.
 
 Tor's anonymity and guards parameters
 -------------------------------------

version 31
Author: lunar
Date:   2013-10-22T13:23:43+00:00

   move postponed items out of the way

--- version 30
+++ version 31
@@ -191,8 +191,4 @@
 
   [24] https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
   [25] https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
-}}}
-
-Possible items:
-
- * looks like the botnet is declining… needs more information https://metrics.torproject.org/users.html
+}}}
version 30
Author: lunar
Date:   2013-10-22T13:22:27+00:00

   add numbers

--- version 29
+++ version 30
@@ -15,23 +15,23 @@
 Tor's anonymity and guards parameters
 -------------------------------------
 
-In a lengthly blog post [XXX], Roger Dingledine looked back on three
+In a lengthly blog post [1], Roger Dingledine looked back on three
 research papers published in the past year. Some of them have been
 covered and most of the time misunderstood by the press. A good recap
 of the research problems, what the findings mean and possible solutions
 hopefully will help everyone understand better.
 
-Introduced in 2005 [XXX], entry guards were added to recognise that
+Introduced in 2005 [2], entry guards were added to recognise that
 “some circuits are going to be compromised, but it's better to increase
 your probability of having no compromised circuits at the expense of
 also increasing the proportion of your circuits that will be compromised
 if any of them are.” Roger “originally picked ‘one or two months’ for
 guard rotation” but the initial parameters called for more in-depth
-research [XXX].
+research [3].
 
-That call was heard by “the Tor research community [XXX], and it's great
+That call was heard by “the Tor research community [4], and it's great
 that Tor gets such attention. We get this attention because we put so
-much effort into making it easy [XXX] for researchers to analyze Tor.”
+much effort into making it easy [5] for researchers to analyze Tor.”
 In his writing Roger highlights the finding of three papers. Two of them
 published at WPES 2012 and Oakland 2013, and another upcoming at
 CCS2013.
@@ -50,42 +50,42 @@
 wish to better understand some of Tor's risk mitigation strategies. It
 is also full of little and big things where you could make a difference!
 
- [XXX] https://blog.torproject.org/blog/improving-tors-anonymity-changing-guard-parameters
- [XXX] https://blog.torproject.org/blog/top-changes-tor-2004-design-paper-part-2
- [XXX] https://blog.torproject.org/blog/research-problem-better-guard-rotation-parameters
- [XXX] http://freehaven.net/anonbib/
- [XXX] https://research.torproject.org/
+   [1] https://blog.torproject.org/blog/improving-tors-anonymity-changing-guard-parameters
+   [2] https://blog.torproject.org/blog/top-changes-tor-2004-design-paper-part-2
+   [3] https://blog.torproject.org/blog/research-problem-better-guard-rotation-parameters
+   [4] http://freehaven.net/anonbib/
+   [5] https://research.torproject.org/
 
 Hidden Service research
 -----------------------
 
 George Kadianakis posted a list of items that need work on the Hidden
-Service area [XXX]. I Despite not exhaustive, the list contains many
+Service area [6]. I Despite not exhaustive, the list contains many
 items that might help with upgrading the Hidden Service design, be it
 around security, performance, guard issues or “petname” systems.
 
 Help and comments are welcome!
 
-  [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-October/005637.html
+   [6] https://lists.torproject.org/pipermail/tor-dev/2013-October/005637.html
 
 Usability issues in existing OTR clients
 ----------------------------------------
 
 The consensus after the first round of discussions and research done in
-the prospect of providing a new secure instant-messaging Tor bundle
-[XXX] is to use Mozilla Instantbird at its core. Arlo Breault sent out a
-draft plan [XXX] on how to do so.
+the prospect of providing a new secure instant-messaging Tor bundle [7] is to
+use Mozilla Instantbird at its core. Arlo Breault sent out a
+draft plan [8] on how to do so.
 
 Instantbird currently lacks a core feature to turn it into the Tor
-Messenger: support for the OTR [XXX] protocol for encrypted chat. Now is
+Messenger: support for the OTR [9] protocol for encrypted chat. Now is
 thus a good time to gather usability issues in existing OTR clients.
 
-Mike Perry kicked off the discussion [XXX] by pointing out several
+Mike Perry kicked off the discussion [10] by pointing out several
 defiencies regarding problems with multiple clients, key management
 issues, and other sub-optimal behaviours.
 
 Ian Goldberg — original author of the pervasive OTR plugin for Pidgin —
-pointed out [XXX] that at least one of the behaviour singled out by Mike
+pointed out [11] that at least one of the behaviour singled out by Mike
 was “done on purpose. The thing it's trying to prevent is that Alice
 and Bob are chatting, and Bob ends OTR just before Alice hits Enter on
 her message. If Alice's client went to "Not private" instead of
@@ -97,11 +97,11 @@
 interfaces can be hard. Usability, in itself, is an often overlooked
 security feature. Now is a good time to contribute your ideas!
 
- [XXX] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Otter/Attentive
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-October/005616.html
- [XXX] https://otr.cypherpunks.ca/
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-October/005636.html
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-October/005640.html
+   [7] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Otter/Attentive
+   [8] https://lists.torproject.org/pipermail/tor-dev/2013-October/005616.html
+   [9] https://otr.cypherpunks.ca/
+  [10] https://lists.torproject.org/pipermail/tor-dev/2013-October/005636.html
+  [11] https://lists.torproject.org/pipermail/tor-dev/2013-October/005640.html
 
 Tor Help Desk Roundup
 ---------------------
@@ -122,47 +122,47 @@
 Miscellaneous news
 ------------------
 
-Tails has issued a call for testing [XXX] of its upcoming 0.21 release. The
+Tails has issued a call for testing [12] of its upcoming 0.21 release. The
 new version contains two security fixes regarding access to the Tor control
-port and persistent settings [XXX] among other improvements and package
-updates [XXX]. “Test wildly!” as the Tails team wrote it.
+port and persistent settings [13] among other improvements and package
+updates [14]. “Test wildly!” as the Tails team wrote it.
 
- [XXX] https://tails.boum.org/news/test_0.21-rc1/
- [XXX] https://git-tails.immerda.ch/tails/plain/wiki/src/doc/first_steps/persistence/upgrade.mdwn?h=bugfix/safer-persistence
- [XXX] https://git-tails.immerda.ch/tails/plain/debian/changelog?id=0.21-rc1
+  [12] https://tails.boum.org/news/test_0.21-rc1/
+  [13] https://git-tails.immerda.ch/tails/plain/wiki/src/doc/first_steps/persistence/upgrade.mdwn?h=bugfix/safer-persistence
+  [14] https://git-tails.immerda.ch/tails/plain/debian/changelog?id=0.21-rc1
 
-Andrew Lewman was invited to speak at SECURE Poland 2013 [XXX] and sent
-a report on his trip [XXX] to Warsaw.
+Andrew Lewman was invited to speak at SECURE Poland 2013 [15] and sent
+a report on his trip [16] to Warsaw.
 
- [XXX] http://www.secure.edu.pl/
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-October/000364.html
+  [15] http://www.secure.edu.pl/
+  [16] https://lists.torproject.org/pipermail/tor-reports/2013-October/000364.html
 
-Tails developers are looking for Mac and PC hardware with UEFI [XXX]. If you have
+Tails developers are looking for Mac and PC hardware with UEFI [17]. If you have
 some spare hardware, please consider a donation!
 
- [XXXX] https://tails.boum.org/news/Mac_and_PC_UEFI_hardware_needed/index.en.html
+  [17] https://tails.boum.org/news/Mac_and_PC_UEFI_hardware_needed/index.en.html
 
-Ximin Luo has been the first to create a ticket with 5 digits [XXX] on Tor
+Ximin Luo has been the first to create a ticket with 5 digits [18] on Tor
 tracker. At the current rate, ticket #20000 should happen by the end of 2015…
 Or will the project continued growth make this happen sooner?
 
- [XXX] https://bugs.torproject.org/10000
+  [18] https://bugs.torproject.org/10000
 
-Roger Dingledine reported [XXX] on his activities for September and October.
-Arturo Filastò also reported [XXX] on his September.
+Roger Dingledine reported [19] on his activities for September and October.
+Arturo Filastò also reported [20] on his September.
 
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-October/000365.html
- [XXX] https://lists.torproject.org/pipermail/tor-reports/2013-October/000366.html
+  [19] https://lists.torproject.org/pipermail/tor-reports/2013-October/000365.html
+  [20] https://lists.torproject.org/pipermail/tor-reports/2013-October/000366.html
 
-Runa Sandvik continues her work on the new, more comprehensible Tor User Manual [XXX].
-The first draft is already out [XXX]. Please review and contribute.
+Runa Sandvik continues her work on the new, more comprehensible Tor User Manual [21].
+The first draft is already out [22]. Please review and contribute.
 
- [XXX] https://lists.torproject.org/pipermail/tor-dev/2013-October/005649.html
- [XXX] https://trac.torproject.org/projects/tor/ticket/5811
+  [21] https://lists.torproject.org/pipermail/tor-dev/2013-October/005649.html
+  [22] https://trac.torproject.org/projects/tor/ticket/5811
 
-Aaron published a branch with his work on a Tor exit scanner based on OONI [XXX].
+Aaron published a branch with his work on a Tor exit scanner based on OONI [23].
 
- [XXX] https://github.com/TheTorProject/ooni-probe/tree/feature/tor_test_template
+  [23] https://github.com/TheTorProject/ooni-probe/tree/feature/tor_test_template
 
 Upcoming events
 ---------------
@@ -185,12 +185,12 @@
 
 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 [24], write down your
+name and subscribe to the team mailing list [25] 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
+  [24] https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+  [25] https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
 }}}
 
 Possible items:

version 29
Author: lunar
Date:   2013-10-22T13:18:37+00:00

   reword

--- version 28
+++ version 29
@@ -115,9 +115,9 @@
 Ubuntu 13.10 (Saucy Salamander) was released this week. One user reported 
 their Tor Browser Bundle behaving unusually after updating their Ubuntu 
 operating system. This issue was resolved by switching to the Tor Browser 
-Bundle 3. Another user asked when Tor's deb page would have updated packages 
-for Saucy Salamander. The Tor Project website now has packages for the latest 
-version of Ubuntu. 
+Bundle 3. Another user asked when Tor APT repositories would have packages 
+for Saucy Salamander. Since then, packages for the latest version of
+Ubuntu have been made available from the usual deb.torproject.org. 
 
 Miscellaneous news
 ------------------

version 28
Author: lunar
Date:   2013-10-22T13:13:36+00:00

   add events

--- version 27
+++ version 28
@@ -167,13 +167,17 @@
 Upcoming events
 ---------------
 
-Jul XX-XX | Event XXX brief description
-          | Event City, Event Country
-          | Event website URL
+Oct 25    | Matt @ EPIC and Public Citizen's CryptoParty 
+          | Washington, DC, USA
+          | https://epic.org/events/cryptoparty/
           |
-Jul XX-XX | Event XXX brief description
-          | Event City, Event Country
-          | Event website URL
+Nov 04    | Workshop on Privacy in the Electronic Society
+          | Berlin, Germany
+          | http://wpes2013.di.unimi.it/
+          |
+Nov 04-05 | 20th ACM Conference on Computer and Communications Security
+          | Berlin, Germany
+          | http://www.sigsac.org/ccs/CCS2013/
 
 
 This issue of Tor Weekly News has been assembled by Lunar, Matt Pagan,

version 27
Author: lunar
Date:   2013-10-22T13:09:00+00:00

   add credits

--- version 26
+++ version 27
@@ -59,10 +59,10 @@
 Hidden Service research
 -----------------------
 
-George posted a list of items that need work on the Hidden Service area [XXX].
-Despite not exhaustive, the list contains many items that might help with
-upgrading the Hidden Service design, be it around security, performance,
-guard issues or “petname” systems.
+George Kadianakis posted a list of items that need work on the Hidden
+Service area [XXX]. I Despite not exhaustive, the list contains many
+items that might help with upgrading the Hidden Service design, be it
+around security, performance, guard issues or “petname” systems.
 
 Help and comments are welcome!
 
@@ -176,8 +176,8 @@
           | Event website URL
 
 
-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, Matt Pagan,
+dope457 and George Kadianakis.
 
 Want to continue reading TWN? Please help us create this newsletter.
 We still need more volunteers to watch the Tor community and report
@@ -191,4 +191,4 @@
 
 Possible items:
 
- * looks like the botnet is declining… needs more information https://metrics.torproject.org/users.html+ * looks like the botnet is declining… needs more information https://metrics.torproject.org/users.html


===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2013/17 ===
===========================================================================

version 3
Author: lunar
Date:   2013-10-22T13:23:32+00:00

   report last week item

--- version 2
+++ version 3
@@ -76,4 +76,8 @@
 
   [XXX] https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
   [XXX] https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
-}}}+}}}
+
+Possible items:
+
+ * looks like the botnet is declining… needs more information https://metrics.torproject.org/users.html

version 2
Author: lunar
Date:   2013-10-22T13:23:10+00:00

   fix boilerplate

--- version 1
+++ version 2
@@ -1,4 +1,4 @@
-''XXXth issue of Tor Weekly News. Covering what's happening from October 22th, 2013 to October 29th, 2013. To be released on October 30th, 2013.''
+''18th issue of Tor Weekly News. Covering what's happening from October 22th, 2013 to October 29th, 2013. To be released on October 30th, 2013.''
 
 '''Editor:''' 
 

version 1
Author: lunar
Date:   2013-10-22T13:20:21+00:00

   import template

--- 
+++ version 1
@@ -0,0 +1,79 @@
+''XXXth issue of Tor Weekly News. Covering what's happening from October 22th, 2013 to October 29th, 2013. To be released on October 30th, 2013.''
+
+'''Editor:''' 
+
+'''Subject:''' Tor Weekly News — October 30th, 2013
+
+{{{
+========================================================================
+Tor Weekly News                                       October 30th, 2013
+========================================================================
+
+Welcome to the eighteenth 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]
+
+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
+}}}


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