[TWN team] Recent changes to the wiki pages
Lunar
lunar at torproject.org
Tue May 20 08:40:20 UTC 2014
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/20 ===
===========================================================================
version 34
Author: lunar
Date: 2014-05-20T08:08:38+00:00
I'll be the editor!
--- version 33
+++ version 34
@@ -1,6 +1,6 @@
''46th issue of Tor Weekly News. Covering what's happening from May 13th, 2014 to May 20th, 2014. To be released on May 21st, 2014.''
-'''Editor:'''
+'''Editor:''' Lunar
'''Subject:''' Tor Weekly News — May 21st, 2014
version 33
Author: lunar
Date: 2014-05-20T08:08:24+00:00
add events
--- version 32
+++ version 33
@@ -204,13 +204,21 @@
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
+May 21 19:00 UTC | little-t tor development meeting
+ | #tor-dev, irc.oftc.net
+ | https://lists.torproject.org/pipermail/tor-dev/2014-March/006616.html
+ |
+May 23 15:00 UTC | Tor Browser online meeting
+ | #tor-dev, irc.oftc.net
+ | https://lists.torproject.org/pipermail/tbb-dev/2014-April/000049.html
+ |
+May 23 16:00 UTC | Pluggable transports online meeting
+ | #tor-dev, irc.oftc.net
+ | https://lists.torproject.org/pipermail/tor-dev/2014-April/006764.html
+ |
+May 27-28 | Tor @ Stockholm Internet Forum
+ | Stockholm, Sweden
+ | http://www.stockholminternetforum.se/
This issue of Tor Weekly News has been assembled by XXX, XXX, and
version 32
Author: lunar
Date: 2014-05-20T08:06:27+00:00
write about Firefox and DRM
--- version 31
+++ version 32
@@ -31,6 +31,36 @@
[XXX]: https://gitweb.torproject.org/tor.git/blob_plain/2ee56e4c2:/ChangeLog
[XXX]: https://www.torproject.org/dist/
[XXX]: http://packages.qa.debian.org/t/tor/news/20140517T102023Z.html
+
+Digital Restrictions Management and Firefox
+-------------------------------------------
+
+Mozilla's decisions to support playing media with digital restrictions [XXX]
+in Firefox by implementing W3C EME specification has raised a good amount
+of controversy. Paul Crable wanted to know [XXX] what it meant for the
+Tor Browser.
+
+Mike Perry answered that, “simply removing the DRM will be trivial, and it
+will be high on our list of tasks”.
+
+But he also explained his worries regarding a “per-device unique identifier”
+that Firefox would provide as part of the implementation: “it is likely
+that this identifier will soon be abused by all sorts of entities, […]
+quickly moving on to the advertising industry (why not play a short
+device-linked DRM video with your banner ad? You get a persistent,
+device-specific tracking identifier as part of the deal!). I think
+it is also quite likely that many arbitrary sites will actually deny
+access to users who do not provide them with such a device-id,
+if only due to ease of increased revenue generation from a fully
+identified userbase.”
+
+“It seems that neither Mozilla nor Google have fully thought through the
+social effects of giving a unique device-id to arbitrary websites” as
+Mike concludes.
+
+ [XXX]: https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/
+ [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032947.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
Miscellaneous news
------------------
@@ -197,5 +227,3 @@
}}}
Possible items:
-
- * Firefox and DRM worries https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
version 31
Author: lunar
Date: 2014-05-20T07:51:07+00:00
write about ICANN and .onion
--- version 30
+++ version 31
@@ -105,6 +105,20 @@
[XXX]: https://atlas.torproject.org/#details/44EFAF942314F756FC7EA50292D5B383E568A9BD
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004563.html
+Now that ICANN is “selling” top-level domain name, Anders Andersson raised
+worries [XXX] about the .onion extension used by Tor. Fortunately,
+RFC6761 [XXX] defines a process regarding special-use domain names. Last
+November, Christian Grothoff, Matthias Wachs, Hellekin O. Wolf, and
+Jacob Appelbaum submitted a request to reserve several TLDs used in
+peer-to-peer systems. Hellekin sent an update [XXX] about the procedure:
+“the current status quo from the IETF so far is that this issue is not
+a priority”.
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html
+ [XXX]: https://tools.ietf.org/html/rfc6761
+ [XXX]: https://tools.ietf.org/html/draft-grothoff-iesg-special-use-p2p-names-02
+ [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
+
Tor help desk roundup
---------------------
@@ -184,5 +198,4 @@
Possible items:
- * ICANN and .onion https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html IETF process https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
* Firefox and DRM worries https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
version 30
Author: lunar
Date: 2014-05-20T07:40:26+00:00
write about extra connections from the Tor Browser
--- version 29
+++ version 30
@@ -80,6 +80,12 @@
[XXX]: https://bugs.torproject.org/9701
[XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
+
+Nicolas Vigier has been investigating [XXX] some extra connections made
+by the Tor Browser on startup to the local resolver and the default
+port or the SOCKS proxy.
+
+ [XXX]: https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
Shawn Nock proved us once more that talking to ISP is key to run Tor
relays on high-speed links. Shawn's exit node was abruptly shut down by
@@ -178,6 +184,5 @@
Possible items:
- * Looking at tor browser connections https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
* ICANN and .onion https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html IETF process https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
* Firefox and DRM worries https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
version 29
Author: lunar
Date: 2014-05-20T07:38:36+00:00
write about unhappy ISP and DNS port
--- version 28
+++ version 29
@@ -90,12 +90,14 @@
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004553.html
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
-Although, it appears that some providers are now giving troubles to
-operators of non-exit relays [XXX] because part of Tor traffic is
-carried on the same port as DNS [XXX].
+Although, dope457 reported that their provider is now giving them troubles
+as an operator of a non-exit relays [XXX] due to a high amount of
+traffic on the DNS port (53). A port used by a recently setup Tor relay [XXX],
+as pointed [XXX] by Roman Mamedov.
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
[XXX]: https://atlas.torproject.org/#details/44EFAF942314F756FC7EA50292D5B383E568A9BD
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004563.html
Tor help desk roundup
---------------------
version 28
Author: lunar
Date: 2014-05-20T07:32:57+00:00
write about unhappy ISP
--- version 27
+++ version 28
@@ -90,6 +90,13 @@
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004553.html
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
+Although, it appears that some providers are now giving troubles to
+operators of non-exit relays [XXX] because part of Tor traffic is
+carried on the same port as DNS [XXX].
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
+ [XXX]: https://atlas.torproject.org/#details/44EFAF942314F756FC7EA50292D5B383E568A9BD
+
Tor help desk roundup
---------------------
@@ -170,6 +177,5 @@
Possible items:
* Looking at tor browser connections https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
- * ISP unhappy about high number of DNS requests on a relay… https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
* ICANN and .onion https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html IETF process https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
* Firefox and DRM worries https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
version 27
Author: lunar
Date: 2014-05-20T07:26:04+00:00
write about the digitalocean case
--- version 26
+++ version 27
@@ -81,6 +81,15 @@
[XXX]: https://bugs.torproject.org/9701
[XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
+Shawn Nock proved us once more that talking to ISP is key to run Tor
+relays on high-speed links. Shawn's exit node was abruptly shut down by
+its provider [XXX] on May 15th. After a well-crafted plea explaining how
+Tor was important, the provider restored the service [XXX] on the very
+same day!
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004553.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
+
Tor help desk roundup
---------------------
@@ -160,7 +169,6 @@
Possible items:
- * Talking to ISP is important when setting up exits https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
* Looking at tor browser connections https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
* ISP unhappy about high number of DNS requests on a relay… https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
* ICANN and .onion https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html IETF process https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
version 26
Author: lunar
Date: 2014-05-20T07:19:54+00:00
write about clipboard leak
--- version 25
+++ version 26
@@ -72,6 +72,14 @@
[XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000589.html
[XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000592.html
[XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000594.html
+
+Michael Schloh von Bennewitz has been busy analyzing a disk leak [XXX] in
+Tor Browser: when one copy a significant chunk of text in the clipboard,
+a temporary file is created with its content. Michael found a possible fix
+and is welcoming reviews [XXX].
+
+ [XXX]: https://bugs.torproject.org/9701
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
Tor help desk roundup
---------------------
@@ -152,7 +160,6 @@
Possible items:
- * Code review request for bug #9701 https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
* Talking to ISP is important when setting up exits https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
* Looking at tor browser connections https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
* ISP unhappy about high number of DNS requests on a relay… https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
version 25
Author: lunar
Date: 2014-05-20T07:12:55+00:00
metrics was already covered, mention percentage
--- version 24
+++ version 25
@@ -61,7 +61,7 @@
Karsten also notified [XXX] the community of a change in the compression
format used for the tarballs of archived metrics data, which has reduced
-their total size from 212 gigabytes to 33.
+their total size from 212 gigabytes to 33 — an 85% gain!
[XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006884.html
@@ -155,7 +155,6 @@
* Code review request for bug #9701 https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
* Talking to ISP is important when setting up exits https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
* Looking at tor browser connections https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
- * 85% reduction in metrics archive size https://lists.torproject.org/pipermail/tor-dev/2014-May/006884.html
* ISP unhappy about high number of DNS requests on a relay… https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
* ICANN and .onion https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html IETF process https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
* Firefox and DRM worries https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
version 24
Author: lunar
Date: 2014-05-20T07:10:40+00:00
write about Knock NAT tester
--- version 23
+++ version 24
@@ -46,6 +46,18 @@
research and development.
[XXX]: https://blog.torproject.org/blog/10-years-collecting-tor-directory-data
+
+Knock [XXX] is a variant of port-knocking that might be useful in the
+future for pluggable transports. “As Knock uses two fields in the
+TCP header in order to hide information and we explicitly want to
+be compatible with machines sitting in typical home networks”, write [XXX]
+Julian Kirsch, “we thus created a program which tests if Knock would
+work in your environment.” Please give it a try to help the team figure
+out if Knock could be deployed in the wild.
+
+ [XXX]: https://gnunet.org/knock
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006873.html
+ [XXX]: https://gnunet.org/knock_nat_tester
Karsten also notified [XXX] the community of a change in the compression
format used for the tarballs of archived metrics data, which has reduced
@@ -140,7 +152,6 @@
Possible items:
- * Collecting data to demonstrate TCP ISN-based port knocking https://lists.torproject.org/pipermail/tor-dev/2014-May/006873.html
* Code review request for bug #9701 https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
* Talking to ISP is important when setting up exits https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
* Looking at tor browser connections https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
version 23
Author: lunar
Date: 2014-05-20T07:00:41+00:00
write about Tor 0.2.4.22
--- version 22
+++ version 23
@@ -12,12 +12,25 @@
Welcome to the twentieth issue of Tor Weekly News in 2014, the weekly
newsletter that covers what is happening in the XXX Tor community.
-Feature XXX
------------
+Tor 0.2.4.22 is out
+-------------------
-Feature 1 with cited source [XXX]
+A new version of Tor stable branch has been released [XXX] on May 16th:
+“Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
+alpha release series. These include blocking all authority signing
+keys that may have been affected by the OpenSSL "heartbleed" bug,
+choosing a far more secure set of TLS ciphersuites by default, closing
+a couple of memory leaks that could be used to run a target relay out
+of RAM, and several others.”
- [XXX]:
+For more details, look at the full changelog [XXX]. The source is
+available at the usual location [XXX]. Packages should be coming shortly,
+when not already available [XXX].
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032956.html
+ [XXX]: https://gitweb.torproject.org/tor.git/blob_plain/2ee56e4c2:/ChangeLog
+ [XXX]: https://www.torproject.org/dist/
+ [XXX]: http://packages.qa.debian.org/t/tor/news/20140517T102023Z.html
Miscellaneous news
------------------
@@ -127,7 +140,6 @@
Possible items:
- * New stable Tor 0.2.4.22. Please test? https://lists.torproject.org/pipermail/tor-talk/2014-May/032956.html
* Collecting data to demonstrate TCP ISN-based port knocking https://lists.torproject.org/pipermail/tor-dev/2014-May/006873.html
* Code review request for bug #9701 https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
* Talking to ISP is important when setting up exits https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
@@ -135,4 +147,4 @@
* 85% reduction in metrics archive size https://lists.torproject.org/pipermail/tor-dev/2014-May/006884.html
* ISP unhappy about high number of DNS requests on a relay… https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
* ICANN and .onion https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html IETF process https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
- * Firefox and DRM worries https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
+ * Firefox and DRM worries https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
--
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