[TWN team] Recent changes to the wiki pages
Lunar
lunar at torproject.org
Tue Apr 22 09:20:10 UTC 2014
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/16 ===
===========================================================================
version 29
Author: lunar
Date: 2014-04-22T08:49:12+00:00
write about FOCI’14
--- version 28
+++ version 29
@@ -121,6 +121,15 @@
[XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-April/000510.html
+Philipp Winter relayed [XXX] the call for papers of the 4th USENIX Workshop on
+Free and Open Communications on the Internet [XXX]. The workshop will be held
+on August 18th and should bring together the larger community of researchers
+and practitioner interested in Tor and how other ways to study, detect, or
+circumvent censorship. Papers have to be submitted before May 13rd.
+
+ [XXX]: https://blog.torproject.org/blog/call-papers-foci14-workshop
+ [XXX]: https://www.usenix.org/conference/foci14/call-for-papers
+
Tor help desk roundup
---------------------
@@ -173,6 +182,5 @@
* Improving the structure of indirect-connection PTs (meek/flashproxy) https://lists.torproject.org/pipermail/tor-dev/2014-April/006689.html
* Starting Tor from Python using Ctypes improving Sandboxing? https://lists.torproject.org/pipermail/tor-dev/2014-April/006723.html (maybe)
- * Call for papers: FOCI'14 workshop https://blog.torproject.org/blog/call-papers-foci14-workshop
* Call for testing: UEFI support in Tails https://tails.boum.org/news/test_UEFI/index.en.html
* Call for testing: Tails 1.0~rc1 https://tails.boum.org/news/test_1.0-rc1/index.en.html
version 28
Author: lunar
Date: 2014-04-22T08:40:37+00:00
add events
--- version 27
+++ version 28
@@ -144,13 +144,16 @@
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
+Apr 23 19:00 UTC | little-t tor development meeting
+ | #tor-dev, irc.oftc.net
+ | https://lists.torproject.org/pipermail/tor-dev/2014-March/006616.html
+ |
+Apr 25 17:00 UTC | Pluggable transports online meeting
+ | #tor-dev, irc.oftc.net
+ |
+Apr 25 18:00 UTC | Tor Browser online meeting
+ | #tor-dev, irc.oftc.net
+ | https://lists.torproject.org/pipermail/tbb-dev/2014-March/000026.html
This issue of Tor Weekly News has been assembled by XXX, XXX, and
version 27
Author: lunar
Date: 2014-04-22T08:38:57+00:00
add another ref
--- version 26
+++ version 27
@@ -76,11 +76,12 @@
Andrea Shepard sent [XXX] a list of 1777 fingerprints for relays “which have
ever turned up as potentially exposed by Heartbleed”. It appears that enough
-directory authority operators rejects known problematic relays: sssheep
+directory authority operators rejects known problematic relays [XXX]: sssheep
reported [XXX] that the network was down to 0.01% of the consensus weight still
vulnerable.
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004340.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004362.html
[XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-April/032762.html
Mick drew attention [XXX] to the fact that in its current state,
version 26
Author: lunar
Date: 2014-04-22T08:37:39+00:00
write about heartbleed
--- version 25
+++ version 26
@@ -73,6 +73,15 @@
improvements to the transparent proxying iptables scripts”.
[XXX]: https://lists.mayfirst.org/pipermail/guardian-dev/2014-April/003436.html
+
+Andrea Shepard sent [XXX] a list of 1777 fingerprints for relays “which have
+ever turned up as potentially exposed by Heartbleed”. It appears that enough
+directory authority operators rejects known problematic relays: sssheep
+reported [XXX] that the network was down to 0.01% of the consensus weight still
+vulnerable.
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004340.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-April/032762.html
Mick drew attention [XXX] to the fact that in its current state,
arm [XXX] — the command-line relay status monitor — wrongly advises
@@ -159,9 +168,7 @@
Possible items:
* Improving the structure of indirect-connection PTs (meek/flashproxy) https://lists.torproject.org/pipermail/tor-dev/2014-April/006689.html
- * rejecting more relays affected by heartbleed https://lists.torproject.org/pipermail/tor-relays/2014-April/004340.html
- * most heartbleed vulnerable relays are out of the consensus https://lists.torproject.org/pipermail/tor-talk/2014-April/032762.html
* Starting Tor from Python using Ctypes improving Sandboxing? https://lists.torproject.org/pipermail/tor-dev/2014-April/006723.html (maybe)
* Call for papers: FOCI'14 workshop https://blog.torproject.org/blog/call-papers-foci14-workshop
* Call for testing: UEFI support in Tails https://tails.boum.org/news/test_UEFI/index.en.html
- * Call for testing: Tails 1.0~rc1 https://tails.boum.org/news/test_1.0-rc1/index.en.html+ * Call for testing: Tails 1.0~rc1 https://tails.boum.org/news/test_1.0-rc1/index.en.html
version 25
Author: lunar
Date: 2014-04-22T08:25:42+00:00
write about meek
--- version 24
+++ version 25
@@ -96,6 +96,17 @@
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004373.html
[XXX]: http://www.ansible.com/
+David Fifield continues his progress on meek [XXX], a pluggable transport “that
+routes your traffic through a third-party web service in a way that should be
+difficult to block”. David sent a call for wider testing [XXX] of experimental
+Tor Browser builds and a call for reviews of the code [XXX]. “There are a
+lot of components that make up the meek transport. […] This is your chance
+to get in on the ground floor of a new transport!”
+
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/doc/meek
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-April/006718.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-April/006719.html
+
Nicolas Vigier submitted his status report for March [XXX].
[XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-April/000510.html
@@ -150,7 +161,6 @@
* Improving the structure of indirect-connection PTs (meek/flashproxy) https://lists.torproject.org/pipermail/tor-dev/2014-April/006689.html
* rejecting more relays affected by heartbleed https://lists.torproject.org/pipermail/tor-relays/2014-April/004340.html
* most heartbleed vulnerable relays are out of the consensus https://lists.torproject.org/pipermail/tor-talk/2014-April/032762.html
- * test meek bundle https://lists.torproject.org/pipermail/tor-dev/2014-April/006718.html; review meek code https://lists.torproject.org/pipermail/tor-dev/2014-April/006719.html
* Starting Tor from Python using Ctypes improving Sandboxing? https://lists.torproject.org/pipermail/tor-dev/2014-April/006723.html (maybe)
* Call for papers: FOCI'14 workshop https://blog.torproject.org/blog/call-papers-foci14-workshop
* Call for testing: UEFI support in Tails https://tails.boum.org/news/test_UEFI/index.en.html
version 24
Author: lunar
Date: 2014-04-22T08:15:23+00:00
write about Ansible role
--- version 23
+++ version 24
@@ -87,6 +87,15 @@
[XXX]: https://bugs.torproject.org/10702
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004412.html
+On the tor-relays mailing list, David Stainton mentioned [XXX] his Tor role [XXX]
+for the Ansible [XXX] automation tool. David hope that “relay operators will
+find this useful for deploying and maintaining large numbers of Tor relays
+and bridges”. The documentation specifies that it currently works with Debian
+and Ubuntu systems and contain several configuration examples.
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-April/004373.html
+ [XXX]: http://www.ansible.com/
+
Nicolas Vigier submitted his status report for March [XXX].
[XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-April/000510.html
@@ -140,7 +149,6 @@
* Improving the structure of indirect-connection PTs (meek/flashproxy) https://lists.torproject.org/pipermail/tor-dev/2014-April/006689.html
* rejecting more relays affected by heartbleed https://lists.torproject.org/pipermail/tor-relays/2014-April/004340.html
- * ansible-tor https://lists.torproject.org/pipermail/tor-relays/2014-April/004373.html (or was it mentioned recently?)
* most heartbleed vulnerable relays are out of the consensus https://lists.torproject.org/pipermail/tor-talk/2014-April/032762.html
* test meek bundle https://lists.torproject.org/pipermail/tor-dev/2014-April/006718.html; review meek code https://lists.torproject.org/pipermail/tor-dev/2014-April/006719.html
* Starting Tor from Python using Ctypes improving Sandboxing? https://lists.torproject.org/pipermail/tor-dev/2014-April/006723.html (maybe)
version 23
Author: lunar
Date: 2014-04-22T08:07:04+00:00
arm is usually all lowercase
--- version 22
+++ version 23
@@ -75,7 +75,7 @@
[XXX]: https://lists.mayfirst.org/pipermail/guardian-dev/2014-April/003436.html
Mick drew attention [XXX] to the fact that in its current state,
-Arm [XXX] — the command-line relay status monitor — wrongly advises
+arm [XXX] — the command-line relay status monitor — wrongly advises
relay operators to run it with the same user as Tor, in order to access
information about the relay’s connections. This is in fact a very bad
idea, and a ticket [XXX] is already open to address this issue. Lunar
--
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