[TWN team] Recent changes to the wiki pages

Lunar lunar at torproject.org
Wed Sep 3 02:00:07 UTC 2014


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

version 43
Author: harmony
Date:   2014-09-03T01:18:25+00:00

   freeze

--- version 42
+++ version 43
@@ -3,6 +3,8 @@
 '''Editor:''' harmony
 
 '''Subject:''' Tor Weekly News — September 3rd, 2014
+
+'''Status:''' Frozen. Only technical and language fixes are welcome. New items should go in [wiki:TorWeeklyNews/2014/36 next week's edition]
 
 {{{
 ========================================================================
@@ -15,43 +17,42 @@
 Tor Browser 3.6.5 and 4.0-alpha-2 are out
 -----------------------------------------
 
-[Erinn Clark/Mike Perry] announced [XXX] new stable and alpha releases
-by the Tor Browser team. Among the major changes, version 3.6.5 upgrades
+[Erinn Clark/Mike Perry] announced [1] new stable and alpha releases by
+the Tor Browser team. Among the major changes, version 3.6.5 upgrades
 Firefox to 24.8.0esr, and includes an improved prompt to help users
-defend against HTML5 canvas image fingerprinting [XXX], following a
-patch by Isis Lovecruft [XXX]. Version 4.0-alpha-2 additionally includes
-the code for the forthcoming Tor Browser auto-updater (switched off by
-default) and “better hardening for Windows and Linux builds” [XXX].
-
-As ever, you can read the full changelog in [Erinn/Mike]’s post, and
+defend against HTML5 canvas image fingerprinting [2], following a patch
+by Isis Lovecruft [3]. Version 4.0-alpha-2 additionally includes the
+code for the forthcoming Tor Browser auto-updater (switched off by
+default) and “better hardening for Windows and Linux builds” [4].
+
+As ever, you can read the full changelog in [Erinn/Mike]’s post, and
 download the new releases along with their signature files from the Tor
-Project’s distribution directory [XXX]. Please upgrade as soon as you
-can.
-
- [XXX]: *add blog URL here*
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-July/033969.html
- [XXX]: https://bugs.torproject.org/12684
- [XXX]: https://lists.torproject.org/pipermail/tor-qa/2014-September/000458.html
- [XXX]: https://www.torproject.org/dist/torbrowser/
+Project’s distribution directory [5]. Please upgrade as soon as you can.
+
+  [1]: *add blog URL here*
+  [2]: https://lists.torproject.org/pipermail/tor-talk/2014-July/033969.html
+  [3]: https://bugs.torproject.org/12684
+  [4]: https://lists.torproject.org/pipermail/tor-qa/2014-September/000458.html
+  [5]: https://www.torproject.org/dist/torbrowser/
 
 Tails 1.1.1 is out
 ------------------
 
-The Tails team released [XXX] version 1.1.1 of the Debian- and Tor-based
+The Tails team released [6] version 1.1.1 of the Debian- and Tor-based
 live operating system. As well as upgrading key components like Tor,
 Iceweasel, and Linux, this release disables I2P by default when Tails is
 booted, in response to the vulnerability recently disclosed by Exodus
-Intelligence [XXX]. Like Truecrypt, “i2p” must now be specified as a
+Intelligence [7]. Like Truecrypt, “i2p” must now be specified as a
 parameter on booting by users who wish to use it.
 
 A number of other security fixes and routine improvements make this an
 important update for all Tails users. See the full changelog in the
 team’s announcement, then update from a running copy of Tails 1.1 if you
-have one, or head to the download page [XXX] if you don’t.
-
- [XXX]: https://tails.boum.org/news/version_1.1.1/
- [XXX]: https://tails.boum.org/security/Security_hole_in_I2P_0.9.13/
- [XXX]: https://tails.boum.org/download/
+have one, or head to the download page [8] if you don’t.
+
+  [6]: https://tails.boum.org/news/version_1.1.1/
+  [7]: https://tails.boum.org/security/Security_hole_in_I2P_0.9.13/
+  [8]: https://tails.boum.org/download/
 
 Helping Internet services accept anonymous users
 ------------------------------------------------
@@ -64,181 +65,181 @@
 
 However, Tor would become much less attractive to users if they found
 themselves unable to reach or interact with their favorite websites
-while using it, a situation that is unfortunately growing more common
-as site administrators and engineers react negatively to instances of
-abusive Tor traffic by banning anonymous connections outright. Tor
-users and developers, as well as members of other online communities
-(such as Wikimedia [XXX]), have tried to address the issue before,
-but real progress has yet to be made.
-
-Roger Dingledine wrote a “call to arms” [XXX] explaining the problem
-in detail and exploring possible paths to a solution: “Step one is
-to enumerate the set of websites and other Internet services that
-handle Tor connections differently from normal connections […]. Step
-two is to sort the problem websites based on how amenable they would
-be to our help”.
-
-Since the problem involves humans as much as it does machines,
-anyone working on it will have to be both “technical” but also
-”good at activism”. If you fit that description, OTF has expressed
-interest in funding work on this issue through their Information
-Controls Fellowship Program [XXX]. Please read Roger’s blog post in
-full for more details.
-
- [XXX]: https://meta.wikimedia.org/wiki/Grants:IdeaLab/Partnership_between_Wikimedia_community_and_Tor_community
- [XXX]: https://blog.torproject.org/blog/call-arms-helping-internet-services-accept-anonymous-users
- [XXX]: https://www.opentechfund.org/labs/fellowships
+while using it, a situation that is unfortunately growing more common as
+site administrators and engineers react negatively to instances of
+abusive Tor traffic by banning anonymous connections outright. Tor users
+and developers, as well as members of other online communities (such as
+Wikimedia [9]), have tried to address the issue before, but real
+progress has yet to be made.
+
+Roger Dingledine wrote a “call to arms” [10] explaining the problem in
+detail and exploring possible paths to a solution: “Step one is to
+enumerate the set of websites and other Internet services that handle
+Tor connections differently from normal connections […]. Step two is to
+sort the problem websites based on how amenable they would be to our
+help”.
+
+Since the problem involves humans as much as it does machines, anyone
+working on it will have to be both “technical” but also ”good at
+activism”. If you fit that description, OTF has expressed interest in
+funding work on this issue through their Information Controls Fellowship
+Program [11]. Please read Roger’s blog post in full for more details.
+
+  [9]: https://meta.wikimedia.org/wiki/Grants:IdeaLab/Partnership_between_Wikimedia_community_and_Tor_community
+ [10]: https://blog.torproject.org/blog/call-arms-helping-internet-services-accept-anonymous-users
+ [11]: https://www.opentechfund.org/labs/fellowships
 
 Monthly status reports for August 2014
 --------------------------------------
 
 The wave of regular monthly reports from Tor project members for the
 month of August has begun. Damian Johnson released his report
-first [XXX], followed by reports from Georg Koppen [XXX], Sherief
-Alaa [XXX], Noel Torres [XXX], Kevin P Dyer [XXX], Nick
-Mathewson [XXX], Lunar [XXX], Arthur D. Edelstein [XXX],
-Karsten Loesing [XXX], Andrew Lewman [XXX], Arlo Breault [XXX],
-Pearl Crescent [XXX], and Michael Schloh von Bennewitz [XXX].
-
-Lunar also reported on behalf of the help desk [XXX], and Mike Perry did
-the same for the Tor Browser team [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000626.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000627.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000628.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000629.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000630.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000633.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000635.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000636.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000637.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000638.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000639.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000640.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000641.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000634.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000642.html
+first [12], followed by reports from Georg Koppen [13], Sherief
+Alaa [14], Noel Torres [15], Kevin P Dyer [16], Nick Mathewson [17],
+Lunar [18], Arthur D. Edelstein [19], Karsten Loesing [20], Andrew
+Lewman [21], Arlo Breault [22], Pearl Crescent [23], and Michael Schloh
+von Bennewitz [24].
+
+Lunar also reported on behalf of the help desk [25], and Mike Perry did
+the same for the Tor Browser team [26].
+
+ [12]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000626.html
+ [13]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000627.html
+ [14]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000628.html
+ [15]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000629.html
+ [16]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000630.html
+ [17]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000633.html
+ [18]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000635.html
+ [19]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000636.html
+ [20]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000637.html
+ [21]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000638.html
+ [22]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000639.html
+ [23]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000640.html
+ [24]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000641.html
+ [25]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000634.html
+ [26]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000642.html
 
 Miscellaneous news
 ------------------
 
-Yawning Angel released [XXX] a new set of experimental Tor Browser
-builds containing the proposed obfs4 pluggable transport, along with a
+Yawning Angel released [27] a new set of experimental Tor Browser builds
+containing the proposed obfs4 pluggable transport, along with a
 changelog; “questions, comments, feedback” are welcome on the email
-thread or the bug ticket tracking the deployment of obfs4 [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007420.html
- [XXX]: https://bugs.torproject.org/12130
-
-Arturo Filastò announced [XXX] the release of version 1.1.0 of oonibackend,
-the tool “used by ooniprobe to discover the addresses of test helpers (via
-the bouncer) to submit reports to (via the collector) and to perform some
-measurements that require a backend system to talk to (via test
-helpers)” [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-September/007450.html
- [XXX]: https://pypi.python.org/pypi/oonibackend
-
-meejah posted [XXX] a list of tasks to be completed in order to bring
-Tor Weather to a deployable state, following the recent rewrite effort
-and the Google Summer of Code project by Sreenatha Bhatlapenumarthi.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007426.html
-
-Israel Leiva submitted a summary [XXX] of work completed as part of the
+thread or the bug ticket tracking the deployment of obfs4 [28].
+
+ [27]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007420.html
+ [28]: https://bugs.torproject.org/12130
+
+Arturo Filastò announced [29] the release of version 1.1.0 of
+oonibackend, the tool “used by ooniprobe to discover the addresses of
+test helpers (via the bouncer) to submit reports to (via the collector)
+and to perform some measurements that require a backend system to talk
+to (via test helpers)” [30].
+
+ [29]: https://lists.torproject.org/pipermail/tor-dev/2014-September/007450.html
+ [30]: https://pypi.python.org/pypi/oonibackend
+
+meejah posted [31] a list of tasks to be completed in order to bring Tor
+Weather to a deployable state, following the recent rewrite effort and
+the Google Summer of Code project by Sreenatha Bhatlapenumarthi.
+
+ [31]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007426.html
+
+Israel Leiva submitted a summary [32] of work completed as part of the
 “Revamp GetTor” Google Summer of Code project: “The plan for now is to
 keep doing tests and deploy it asap (hopefully during September).”
 
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007427.html
-
-Mike Perry posted [XXX] an updated version [XXX] of the proposal for website
-fingerprinting countermeasures which he co-authored with Marc Juarez as
-part of the latter’s Google Summer of Code project.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007417.html
- [XXX]: https://gitweb.torproject.org/user/mikeperry/torspec.git/blob/refs/heads/multihop-padding-primitives:/proposals/ideas/xxx-multihop-padding-primitives.txt
-
-Lunar gave a talk [XXX] at this year’s DebConf on the effort to build
+ [32]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007427.html
+
+Mike Perry posted [33] an updated version [34] of the proposal for
+website fingerprinting countermeasures which he co-authored with Marc
+Juarez as part of the latter’s Google Summer of Code project.
+
+ [33]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007417.html
+ [34]: https://gitweb.torproject.org/user/mikeperry/torspec.git/blob/refs/heads/multihop-padding-primitives:/proposals/ideas/xxx-multihop-padding-primitives.txt
+
+Lunar gave a talk [35] at this year’s DebConf on the effort to build
 Debian packages deterministically, which is inspired in large part by
-Tor Browser’s use of the same technology [XXX]. Major progress was
-achieved during the conference [XXX].
-
- [XXX]: http://meetings-archive.debian.net/pub/debian-meetings/2014/debconf14/webm/Reproducible_Builds_for_Debian_a_year_later.webm
- [XXX]: https://blog.torproject.org/blog/deterministic-builds-part-one-cyberwar-and-global-compromise
- [XXX]: http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20140901/000198.html
-
-David Fifield submitted a breakdown [XXX] of the costs incurred by the
-infrastructure that supports the meek pluggable transport [XXX] since
-its introduction. The total to date from both the Google App Engine and
+Tor Browser’s use of the same technology [36]. Major progress was
+achieved during the conference [37].
+
+ [35]: http://meetings-archive.debian.net/pub/debian-meetings/2014/debconf14/webm/Reproducible_Builds_for_Debian_a_year_later.webm
+ [36]: https://blog.torproject.org/blog/deterministic-builds-part-one-cyberwar-and-global-compromise
+ [37]: http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20140901/000198.html
+
+David Fifield submitted a breakdown [38] of the costs incurred by the
+infrastructure that supports the meek pluggable transport [39] since its
+introduction. The total to date from both the Google App Engine and
 Amazon AWS front domains? $6.56.
 
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007429.html
- [XXX]: https://trac.torproject.org/projects/tor/wiki/doc/meek
-
-Thanks to P D [XXX] and Daniel Pajonzeck [XXX] for running mirrors of the
+ [38]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007429.html
+ [39]: https://trac.torproject.org/projects/tor/wiki/doc/meek
+
+Thanks to P D [40] and Daniel Pajonzeck [41] for running mirrors of the
 Tor Project website and software!
 
- [XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-August/000653.html
- [XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-August/000673.html
-
-Also on the subject of mirrors, Roger Dingledine alerted [XXX] the
+ [40]: https://lists.torproject.org/pipermail/tor-mirrors/2014-August/000653.html
+ [41]: https://lists.torproject.org/pipermail/tor-mirrors/2014-August/000673.html
+
+Also on the subject of mirrors, Roger Dingledine alerted [42] the
 tor-mirrors mailing list to the fact that the Tor Project website
 (specifically the distribution directory) will shortly be increasing in
-size to eight or nine gigabytes, as a result of the soon-to-be-implemented
-Tor Browser updater [XXX]. Mirror operators will need to ensure that they
-can provide enough disk space to accommodate the change.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-September/000675.html
- [XXX]: https://bugs.torproject.org/4234
-
-whonixqubes announced [XXX} the release of an integrated version of the
+size to eight or nine gigabytes, as a result of the
+soon-to-be-implemented Tor Browser updater [43]. Mirror operators will
+need to ensure that they can provide enough disk space to accommodate
+the change.
+
+ [42]: https://lists.torproject.org/pipermail/tor-mirrors/2014-September/000675.html
+ [43]: https://bugs.torproject.org/4234
+
+whonixqubes announced [44] the release of an integrated version of the
 Whonix and Qubes operating systems: “I look forward to helping make
 Qubes + Whonix integration even tighter and more seamless throughout the
 future.”
 
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-August/034562.html
+ [44]: https://lists.torproject.org/pipermail/tor-talk/2014-August/034562.html
 
 Tor help desk roundup
 ---------------------
 
-The help desk has been asked if Tor can make a website visit appear
-to come from China. Tor connections appear to originate from the
-country where the exit relay in use is located; since Tor is blocked
-in China, there are zero exit relays in China. A visualization of
-the different country-locations of exit relays can be found on Tor’s
-metrics page [XXX].
-
- [XXX]: https://metrics.torproject.org/bubbles.html#country-exits-only 
+The help desk has been asked if Tor can make a website visit appear to
+come from China. Tor connections appear to originate from the country
+where the exit relay in use is located; since Tor is blocked in China,
+there are zero exit relays in China. A visualization of the different
+country-locations of exit relays can be found on Tor’s metrics
+page [45].
+
+ [45]: https://metrics.torproject.org/bubbles.html#country-exits-only 
 
 News from Tor StackExchange
 ---------------------------
 
-Anony Mouse wanted to know why Facebook shows the location of the
-user’s last login over Tor as Baghdad or Dhaka [XXX], instead of
-the real location of the exit relay. qbi posted a screenshot
-showing this issue [XXX]. According to Facebook, this information
-is based on an approximation, so it is probably the case that it
-locates some Tor exit relays either in Baghdad or in Dhaka.
-
- [XXX]: https://tor.stackexchange.com/q/3364/88
- [XXX]: https://twitter.com/qbi/status/506550322308055040
+Anony Mouse wanted to know why Facebook shows the location of the user’s
+last login over Tor as Baghdad or Dhaka [46], instead of the real
+location of the exit relay. qbi posted a screenshot showing this
+issue [47]. According to Facebook, this information is based on an
+approximation, so it is probably the case that it locates some Tor exit
+relays either in Baghdad or in Dhaka.
+
+ [46]: https://tor.stackexchange.com/q/3364/88
+ [47]: https://twitter.com/qbi/status/506550322308055040
 
 user3500 wants to contribute to Tor and asks how this can be done as an
-inexperienced developer [XXX]. Jens Kubieziel replied with several
+inexperienced developer [48]. Jens Kubieziel replied with several
 possibilities, including reading the volunteer page and Tor Weekly News:
 in particular, the section containing easy development tasks might be a
 good start. Roya pointed out that any contribution is better than no
 contribution, and encouraged user3500 to just get started. Umut Seven
 recommended writing unit tests.
 
- [XXX]: https://tor.stackexchange.com/q/3961/88
-
-Kras wants to use FoxyProxy in connection with Tor Browser Bundle and asks
-if it is safe to do so [XXX]. At the moment, there is only an answer saying
-Yes, without any explanation. What is your experience? Is it safe for a user
-to install and use FoxyProxy?
-
- [XXX]: https://tor.stackexchange.com/q/3239/88
+ [48]: https://tor.stackexchange.com/q/3961/88
+
+Kras wants to use FoxyProxy in connection with Tor Browser Bundle and
+asks if it is safe to do so [49]. At the moment, there is only an answer
+saying Yes, without any explanation. What is your experience? Is it safe
+for a user to install and use FoxyProxy?
+
+ [49]: https://tor.stackexchange.com/q/3239/88
 
 Upcoming events
 ---------------
@@ -267,10 +268,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 [50], write down your
+name and subscribe to the team mailing list [51] 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
+ [50]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+ [51]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
 }}}

version 42
Author: harmony
Date:   2014-09-03T01:04:59+00:00

   more reports

--- version 41
+++ version 42
@@ -98,9 +98,10 @@
 Alaa [XXX], Noel Torres [XXX], Kevin P Dyer [XXX], Nick
 Mathewson [XXX], Lunar [XXX], Arthur D. Edelstein [XXX],
 Karsten Loesing [XXX], Andrew Lewman [XXX], Arlo Breault [XXX],
-and Perl Crescent [XXX].
-
-Lunar also reported on behalf of the help desk [XXX].
+Pearl Crescent [XXX], and Michael Schloh von Bennewitz [XXX].
+
+Lunar also reported on behalf of the help desk [XXX], and Mike Perry did
+the same for the Tor Browser team [XXX].
 
  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000626.html
  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000627.html
@@ -114,7 +115,9 @@
  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000638.html
  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000639.html
  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000640.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000641.html
  [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000634.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-September/000642.html
 
 Miscellaneous news
 ------------------

version 41
Author: harmony
Date:   2014-09-03T00:57:29+00:00

   add torbrowser item

--- version 40
+++ version 41
@@ -11,6 +11,28 @@
 
 Welcome to the thirty-fifth issue of Tor Weekly News in 2014, the weekly
 newsletter that covers what is happening in the Tor community.
+
+Tor Browser 3.6.5 and 4.0-alpha-2 are out
+-----------------------------------------
+
+[Erinn Clark/Mike Perry] announced [XXX] new stable and alpha releases
+by the Tor Browser team. Among the major changes, version 3.6.5 upgrades
+Firefox to 24.8.0esr, and includes an improved prompt to help users
+defend against HTML5 canvas image fingerprinting [XXX], following a
+patch by Isis Lovecruft [XXX]. Version 4.0-alpha-2 additionally includes
+the code for the forthcoming Tor Browser auto-updater (switched off by
+default) and “better hardening for Windows and Linux builds” [XXX].
+
+As ever, you can read the full changelog in [Erinn/Mike]’s post, and
+download the new releases along with their signature files from the Tor
+Project’s distribution directory [XXX]. Please upgrade as soon as you
+can.
+
+ [XXX]: *add blog URL here*
+ [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-July/033969.html
+ [XXX]: https://bugs.torproject.org/12684
+ [XXX]: https://lists.torproject.org/pipermail/tor-qa/2014-September/000458.html
+ [XXX]: https://www.torproject.org/dist/torbrowser/
 
 Tails 1.1.1 is out
 ------------------
@@ -24,8 +46,8 @@
 
 A number of other security fixes and routine improvements make this an
 important update for all Tails users. See the full changelog in the
-team’s announcement, then head to the download page [XXX] to get your
-copy.
+team’s announcement, then update from a running copy of Tails 1.1 if you
+have one, or head to the download page [XXX] if you don’t.
 
  [XXX]: https://tails.boum.org/news/version_1.1.1/
  [XXX]: https://tails.boum.org/security/Security_hole_in_I2P_0.9.13/
@@ -249,6 +271,3 @@
   [XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
   [XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
 }}}
-
-Possible items:
- * Tor Browser 3.6.5 should be released on Tuesday; changelog https://lists.torproject.org/pipermail/tor-qa/2014-September/000456.html


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

version 1
Author: harmony
Date:   2014-09-03T01:21:45+00:00

   create page

--- 
+++ version 1
@@ -0,0 +1,89 @@
+''62nd issue of Tor Weekly News. Covering what's happening from September 2nd, 2014 to September 9th, 2014. To be released on September 10th, 2014.''
+
+'''Editor:''' 
+
+'''Subject:''' Tor Weekly News — September 10th, 2014
+
+{{{
+========================================================================
+Tor Weekly News                                     September 10th, 2014
+========================================================================
+
+Welcome to the 36th issue of Tor Weekly News in 2014, the weekly
+newsletter that covers what is happening in the XXX Tor community.
+
+Feature XXX
+-----------
+
+Feature 1 with cited source [XXX]
+
+ [XXX]:
+
+Monthly status reports for XXX month 2014
+-----------------------------------------
+
+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. 
+
+News from Tor StackExchange
+---------------------------
+
+Text with cited source [XXX].
+
+ [XXX]:
+
+Easy development tasks to get involved with
+-------------------------------------------
+
+Text with cited source [XXX].
+
+ [XXX]: 
+
+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