[TWN team] Recent changes to the wiki pages
Lunar
lunar at torproject.org
Tue Aug 12 17:00:19 UTC 2014
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/32 ===
===========================================================================
version 35
Author: lunar
Date: 2014-08-12T16:20:36+00:00
FREEZE
--- version 34
+++ version 35
@@ -1,6 +1,8 @@
''58th issue of Tor Weekly News. Covering what's happening from August 5th, 2014 to August 12th, 2014. To be released on August 13th, 2014.''
'''Editor:''' Lunar
+
+'''Status:''' Frozen. Only technical and language fixes are welcome. New items should go in [wiki:TorWeeklyNews/2014/33 next week's edition]
'''Subject:''' Tor Weekly News — August 13th, 2014
@@ -9,24 +11,23 @@
Tor Weekly News August 13th, 2014
========================================================================
-Welcome to the thirty-second issue of Tor Weekly News in 2014, the weekly
-newsletter that covers what is happening in the Tor community.
+Welcome to the thirty-second issue of Tor Weekly News in 2014, the
+weekly newsletter that covers what is happening in the Tor community.
Torsocks 2.0 is now considered stable
-------------------------------------
-Torsocks [XXX] is a wrapper program that will force network connections
-of an application to go through the Tor network. David Goulet
-released [XXX] version 2.0.0, blessing the new codebase as stable after
-more than a year of efforts [XXX].
-
-David's original email highlighted several reasons for a complete
+Torsocks [1] is a wrapper program that will force network connections of
+an application to go through the Tor network. David Goulet released [2]
+version 2.0.0, blessing the new codebase as stable after more than a
+year of efforts [3].
+
+David’s original email highlighted several reasons for a complete
rewrite of torsocks. Among the issues were maintanability, error
handling, thread safety, lack proper compatibility layer for multiple
architectures. The new implementation addresses all these issues while
-staying about the same size as the previous version (4000 lines
-of C according to sloccount), and test coverage has been vastly
-extended.
+staying about the same size as the previous version (4000 lines of C
+according to sloccount), and test coverage has been vastly extended.
Torsocks comes in handy when some piece of software does not natively
support using a SOCKS proxy. In most cases, the new version might be
@@ -38,9 +39,9 @@
applications might behave differently as more system calls are now
restricted.
- [XXX]: https://gitweb.torproject.org/torsocks.git/blob/HEAD:/README.md
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007330.html
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2013-June/004959.html
+ [1]: https://gitweb.torproject.org/torsocks.git/blob/HEAD:/README.md
+ [2]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007330.html
+ [3]: https://lists.torproject.org/pipermail/tor-dev/2013-June/004959.html
Next generation Hidden Services and Introduction Points
-------------------------------------------------------
@@ -52,132 +53,131 @@
circuits connecting to this freshly selected Tor node.
This general design is not subject to changes with the revision of
-hidden services [XXX] currently being worked on. But there are still
-some questions left unanswered on the best way to select Introduction
-Points. George Kadianakis summarized [XXX] them as: “How many IPs should
-an HS have? Which relays can be IPs? What's the lifetime of an IP?”
+hidden services [4] currently being worked on. But there are still some
+questions left unanswered on the best way to select Introduction Points.
+George Kadianakis summarized [5] them as: “How many IPs should an HS
+have? Which relays can be IPs? What’s the lifetime of an IP?”
For each of these questions, George collected possible answers and how
they could answer or not to several attacks identified in the past.
Anyone interested should help with the research needed and join the
discussion.
-In the meantime, Michael Rogers is also trying to find ways [XXX] to
+In the meantime, Michael Rogers is also trying to find ways [6] to
improve hidden services performance in mobile contexts. One way to do so
would be to “keep the set of introduction points as stable as possible”.
But a naive approach of doing so would ease the job of attackers trying
to locate a hidden service. The idea would be to always use the same
guard and middle node for a given introduction point. But this might
also open the doors to new attacks. Michael suggests experimenting with
-the recently published Java research framework [XXX] to get better
+the recently published Java research framework [7] to get better
understanding of the implications.
- [XXX]: https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/224-rend-spec-ng.txt
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007335.html
- [XXX]: https://fulpool.org/pipermail/hidden-services/2014-August/000019.html
- [XXX]: https://github.com/drgowen/tor-research-framework
+ [4]: https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/224-rend-spec-ng.txt
+ [5]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007335.html
+ [6]: https://fulpool.org/pipermail/hidden-services/2014-August/000019.html
+ [7]: https://github.com/drgowen/tor-research-framework
More status reports for July 2014
---------------------------------
The wave of regular monthly reports from Tor project members for the
-month of July continued, with submissions from Andrew Lewman [XXX],
-Colin C. [XXX], Damian Johnson [XXX]..
-
-Roger Dingledine sent out the report for SponsorF [XXX]. Arturo Filastò described
-what the OONI team was up to. The Tails team covered their activity for June
-and July [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000615.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000616.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000617.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000619.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000621.html
- [XXX]: https://tails.boum.org/news/report_2014_06-07/
+month of July continued, with submissions from Andrew Lewman [8], Colin
+C. [9], Damian Johnson [10]..
+
+Roger Dingledine sent out the report for SponsorF [11]. Arturo Filastò
+described what the OONI team [12] was up to. The Tails team covered
+their activity for June and July [13].
+
+ [8]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000615.html
+ [9]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000616.html
+ [10]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000617.html
+ [11]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000619.html
+ [12]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000621.html
+ [13]: https://tails.boum.org/news/report_2014_06-07/
Miscellaneous news
------------------
-Two Tor Browser releases are at QA stage: 4.0-alpha-1 [XXX] including
-meek and a new directory layout, and 3.6.4 [XXX] for security fixes.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-qa/2014-August/000436.html
- [XXX]: https://lists.torproject.org/pipermail/tor-qa/2014-August/000439.html
-
-The recent serious attack against Tor hidden services [XXX] was also a
+Two Tor Browser releases are at QA stage: 4.0-alpha-1 [14] including
+meek and a new directory layout, and 3.6.4 [15] for security fixes.
+
+ [14]: https://lists.torproject.org/pipermail/tor-qa/2014-August/000436.html
+ [15]: https://lists.torproject.org/pipermail/tor-qa/2014-August/000439.html
+
+The recent serious attack against Tor hidden services [16] was also a
Sybil attack: a large number of malicious nodes joined the network at
once. This renewed interest in detecting Sybil attacks against the Tor
-network better. Karsten Loesing published some code [XXX] computing
-similarity metrics, and David Fifield has explored visualizations [XXX] of
-the consensus that made the recent attack visible.
-
- [XXX]: https://blog.torproject.org/blog/tor-security-advisory-relay-early-traffic-confirmation-attack
- [XXX]: https://github.com/kloesing/SAD
- [XXX]: https://trac.torproject.org/projects/tor/ticket/12813
-
-Gareth Owen has sent an update [XXX] about the Java Tor Research
+network better. Karsten Loesing published some code [17] computing
+similarity metrics, and David Fifield has explored visualizations [18]
+of the consensus that made the recent attack visible.
+
+ [16]: https://blog.torproject.org/blog/tor-security-advisory-relay-early-traffic-confirmation-attack
+ [17]: https://github.com/kloesing/SAD
+ [18]: https://bugs.torproject.org/12813
+
+Gareth Owen has sent an update [19] about the Java Tor Research
Framework. This prompted a discussion with George Kadianakis and Tim
-about the best way to perform fuzz testing [XXX] on Tor. Have a look if
-you want to comment on Tim's approaches [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
- [XXX]: https://en.wikipedia.org/wiki/Fuzz_testing
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007334.html
-
-Thanks to Daniel Thill [XXX] for running a mirror of the Tor Project
+about the best way to perform fuzz testing [20] on Tor. Have a look if
+you want to comment on Tim’s approaches [21].
+
+ [19]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
+ [20]: https://en.wikipedia.org/wiki/Fuzz_testing
+ [21]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007334.html
+
+Thanks to Daniel Thill [22] for running a mirror of the Tor Project
website!
- [XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-August/000651.html
-
-ban mentioned [XXX] a new service collecting donations for the Tor
-network. OnionTip [XXX], set up by Donncha O'Cearbhaill, will collect
+ [22]: https://lists.torproject.org/pipermail/tor-mirrors/2014-August/000651.html
+
+ban mentioned [23] a new service collecting donations for the Tor
+network. OnionTip [24], set up by Donncha O’Cearbhaill, will collect
bitcoins and redistribute them to relay operators who put a bitcoin
address in their contact information. As the redistribution is currently
-done according to the consensus weight, Sebastian Hahn warned that this
-might encourage one to “cheat the consensus weight” because that now
-mans “more money from oniontip”.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html
- [XXX]: https://oniontip.com/
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
-
-Juha Nurmi sent another update [XXX] on the ahmia.fi GSoC.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
+done according to the consensus weight, Sebastian Hahn warned [25] that
+this might encourage one to “cheat the consensus weight” because that
+now mans “more money from oniontip”.
+
+ [23]: https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html
+ [24]: https://oniontip.com/
+ [25]: https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
+
+Juha Nurmi sent another update [26] on the ahmia.fi GSoC.
+
+ [26]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
News from Tor StackExchange
---------------------------
-arvee wants to redirect some TCP connections to a SOCKS proxy. Redsocks [XXX]
-should help to route packets for port 443 over Tor [XXX]. The user set the
-following line in the file pf.conf:
-`rdr pass on $src inet proto tcp from any to any port 443 -> 127.0.0.1 port 8888`
-mirimir explained that the setting 'SocksPort 8888' is needed.
-
- [XXX]: http://darkk.net.ru/redsocks/
- [XXX]: https://tor.stackexchange.com/q/3802/88
+arvee wants to redirect some TCP connections through Tor on OS X.
+Redsocks [27] should help to route packets for port 443 over Tor [28].
+mirimir explained that given the user's pf configuration, the setting
+“SocksPort 8888” was probably missing.
+
+ [27]: http://darkk.net.ru/redsocks/
+ [28]: https://tor.stackexchange.com/q/3802/88
meee asked a question and offered a bounty for an answer. The circuit handshake
-entry in Tor's log file has some numbers and meee wants to know what their
-meaning is [XXX]:
-`Circuit handshake stats since last time: 1833867/1833868 TAP, 159257/159257 NTor.`
-
- [XXX]: https://tor.stackexchange.com/q/3213/88
+entry in Tor’s log file has some numbers and meee wants to know what
+their meaning is [29]: “Circuit handshake stats since last time:
+1833867/1833868 TAP, 159257/159257 NTor.”
+
+ [29]: https://tor.stackexchange.com/q/3213/88
Easy development tasks to get involved with
-------------------------------------------
-The bridge distributor BridgeDB [XXX] usually gives out bridges by
+The bridge distributor BridgeDB [30] usually gives out bridges by
responding to user requests via HTTPS and email. A while ago, BridgeDB
also gave out bridges to a very small number of people who would then
-redistribute bridges using their social network. We would like to
-resume sending bridges to these people, but only if BridgeDB can be
-made to send them via GnuPG-encrypted emails [XXX]. If you'd like to
-dive into the BridgeDB code and add support for GnuPG-encrypted
-emails, please take a look at the ticket and give it a try.
-
- [XXX]: https://bridges.torproject.org/
- [XXX]: https://bugs.torproject.org/9332
+redistribute bridges using their social network. We would like to resume
+sending bridges to these people, but only if BridgeDB can be made to
+send them via GnuPG-encrypted emails [31]. If you’d like to dive into
+the BridgeDB code and add support for GnuPG-encrypted emails, please
+take a look at the ticket and give it a try.
+
+ [30]: https://bridges.torproject.org/
+ [31]: https://bugs.torproject.org/9332
Upcoming events
---------------
@@ -208,10 +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 [32], write down your
+name and subscribe to the team mailing list [33] 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
+ [32]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+ [33]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
}}}
version 34
Author: lunar
Date: 2014-08-12T16:09:28+00:00
clean up
--- version 33
+++ version 34
@@ -10,7 +10,7 @@
========================================================================
Welcome to the thirty-second issue of Tor Weekly News in 2014, the weekly
-newsletter that covers what is happening in the XXX Tor community.
+newsletter that covers what is happening in the Tor community.
Torsocks 2.0 is now considered stable
-------------------------------------
@@ -145,11 +145,6 @@
[XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
-Tor help desk roundup
----------------------
-
-Summary of some questions sent to the Tor help desk.
-
News from Tor StackExchange
---------------------------
@@ -220,5 +215,3 @@
[XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
[XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
}}}
-
-Possible items:
version 33
Author: lunar
Date: 2014-08-12T16:08:14+00:00
add credits
--- version 32
+++ version 33
@@ -208,8 +208,8 @@
| https://www.usenix.org/conference/usenixsecurity14
-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, qbi,
+Karsten Loesing, and harmony.
Want to continue reading TWN? Please help us create this newsletter.
We still need more volunteers to watch the Tor community and report
version 32
Author: lunar
Date: 2014-08-12T16:05:43+00:00
plug a bug
--- version 31
+++ version 32
@@ -172,9 +172,17 @@
Easy development tasks to get involved with
-------------------------------------------
-Text with cited source [XXX].
-
- [XXX]:
+The bridge distributor BridgeDB [XXX] usually gives out bridges by
+responding to user requests via HTTPS and email. A while ago, BridgeDB
+also gave out bridges to a very small number of people who would then
+redistribute bridges using their social network. We would like to
+resume sending bridges to these people, but only if BridgeDB can be
+made to send them via GnuPG-encrypted emails [XXX]. If you'd like to
+dive into the BridgeDB code and add support for GnuPG-encrypted
+emails, please take a look at the ticket and give it a try.
+
+ [XXX]: https://bridges.torproject.org/
+ [XXX]: https://bugs.torproject.org/9332
Upcoming events
---------------
version 31
Author: lunar
Date: 2014-08-12T16:04:14+00:00
write about ahmia.fi
--- version 30
+++ version 31
@@ -141,6 +141,10 @@
[XXX]: https://oniontip.com/
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
+Juha Nurmi sent another update [XXX] on the ahmia.fi GSoC.
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
+
Tor help desk roundup
---------------------
@@ -210,5 +214,3 @@
}}}
Possible items:
-
- * weekly ahmia.fi report https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
version 30
Author: lunar
Date: 2014-08-12T16:00:11+00:00
write about tor research framework and fuzzing
--- version 29
+++ version 30
@@ -115,6 +115,15 @@
[XXX]: https://github.com/kloesing/SAD
[XXX]: https://trac.torproject.org/projects/tor/ticket/12813
+Gareth Owen has sent an update [XXX] about the Java Tor Research
+Framework. This prompted a discussion with George Kadianakis and Tim
+about the best way to perform fuzz testing [XXX] on Tor. Have a look if
+you want to comment on Tim's approaches [XXX].
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
+ [XXX]: https://en.wikipedia.org/wiki/Fuzz_testing
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007334.html
+
Thanks to Daniel Thill [XXX] for running a mirror of the Tor Project
website!
@@ -202,5 +211,4 @@
Possible items:
- * Tor Research Framework update https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
* weekly ahmia.fi report https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
version 29
Author: lunar
Date: 2014-08-12T15:51:06+00:00
write about oniontip
--- version 28
+++ version 29
@@ -120,6 +120,18 @@
[XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-August/000651.html
+ban mentioned [XXX] a new service collecting donations for the Tor
+network. OnionTip [XXX], set up by Donncha O'Cearbhaill, will collect
+bitcoins and redistribute them to relay operators who put a bitcoin
+address in their contact information. As the redistribution is currently
+done according to the consensus weight, Sebastian Hahn warned that this
+might encourage one to “cheat the consensus weight” because that now
+mans “more money from oniontip”.
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html
+ [XXX]: https://oniontip.com/
+ [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
+
Tor help desk roundup
---------------------
@@ -190,6 +202,5 @@
Possible items:
- * OnionTip.com https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
* Tor Research Framework update https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
* weekly ahmia.fi report https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
version 28
Author: lunar
Date: 2014-08-12T15:34:27+00:00
the bot was killed by weasel, so let's not talk about it
--- version 27
+++ version 28
@@ -190,7 +190,6 @@
Possible items:
- * OFTC-i2p Relay Bot for #tor/#tor-dev https://lists.torproject.org/pipermail/tor-dev/2014-August/007316.html
* OnionTip.com https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
* Tor Research Framework update https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
* weekly ahmia.fi report https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
version 27
Author: lunar
Date: 2014-08-12T15:33:54+00:00
i'll do editing
--- version 26
+++ version 27
@@ -1,6 +1,6 @@
''58th issue of Tor Weekly News. Covering what's happening from August 5th, 2014 to August 12th, 2014. To be released on August 13th, 2014.''
-'''Editor:'''
+'''Editor:''' Lunar
'''Subject:''' Tor Weekly News — August 13th, 2014
version 26
Author: lunar
Date: 2014-08-12T15:32:55+00:00
write about sybil attacks detection
--- version 25
+++ version 26
@@ -104,6 +104,17 @@
[XXX]: https://lists.torproject.org/pipermail/tor-qa/2014-August/000436.html
[XXX]: https://lists.torproject.org/pipermail/tor-qa/2014-August/000439.html
+The recent serious attack against Tor hidden services [XXX] was also a
+Sybil attack: a large number of malicious nodes joined the network at
+once. This renewed interest in detecting Sybil attacks against the Tor
+network better. Karsten Loesing published some code [XXX] computing
+similarity metrics, and David Fifield has explored visualizations [XXX] of
+the consensus that made the recent attack visible.
+
+ [XXX]: https://blog.torproject.org/blog/tor-security-advisory-relay-early-traffic-confirmation-attack
+ [XXX]: https://github.com/kloesing/SAD
+ [XXX]: https://trac.torproject.org/projects/tor/ticket/12813
+
Thanks to Daniel Thill [XXX] for running a mirror of the Tor Project
website!
@@ -179,7 +190,6 @@
Possible items:
- * Sybil attack detection code by Karsten https://github.com/kloesing/SAD and visualization by dcf https://trac.torproject.org/projects/tor/ticket/12813
* OFTC-i2p Relay Bot for #tor/#tor-dev https://lists.torproject.org/pipermail/tor-dev/2014-August/007316.html
* OnionTip.com https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
* Tor Research Framework update https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
version 25
Author: lunar
Date: 2014-08-12T15:28:10+00:00
write about Tor Browser QA
--- version 24
+++ version 25
@@ -98,18 +98,16 @@
Miscellaneous news
------------------
-Item 1 with cited source [XXX].
+Two Tor Browser releases are at QA stage: 4.0-alpha-1 [XXX] including
+meek and a new directory layout, and 3.6.4 [XXX] for security fixes.
+
+ [XXX]: https://lists.torproject.org/pipermail/tor-qa/2014-August/000436.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-qa/2014-August/000439.html
Thanks to Daniel Thill [XXX] for running a mirror of the Tor Project
website!
[XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-August/000651.html
-
-Item 3 with cited source [XXX].
-
- [XXX]:
- [XXX]:
- [XXX]:
Tor help desk roundup
---------------------
@@ -181,7 +179,6 @@
Possible items:
- * Tor Browser alpha 1 ready for QA https://lists.torproject.org/pipermail/tor-qa/2014-August/000436.html
* Sybil attack detection code by Karsten https://github.com/kloesing/SAD and visualization by dcf https://trac.torproject.org/projects/tor/ticket/12813
* OFTC-i2p Relay Bot for #tor/#tor-dev https://lists.torproject.org/pipermail/tor-dev/2014-August/007316.html
* OnionTip.com https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
version 24
Author: lunar
Date: 2014-08-12T15:22:26+00:00
write events
--- version 23
+++ version 24
@@ -145,13 +145,25 @@
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
+ Aug. 13 13:30 UTC | little-t tor development meeting
+ | https://lists.torproject.org/pipermail/tor-dev/2014-August/007314.html
+ | #tor-dev, irc.oftc.net
+ |
+ Aug. 13 16:00 UTC | Pluggable transport online meeting
+ | https://lists.torproject.org/pipermail/tor-dev/2014-August/007317.html
+ | #tor-dev, irc.oftc.net
+ |
+ Aug. 18 18:00 UTC | Tor Browser online meeting
+ | #tor-dev, irc.oftc.net
+ | https://lists.torproject.org/pipermail/tbb-dev/2014-August/000100.html
+ |
+ August 18 | Roger @ FOCI ’14
+ | San Diego, California, USA
+ | https://www.usenix.org/conference/foci14
+ |
+ August 20-22 | Roger @ USENIX Security Symposium ’14
+ | San Diego, California, USA
+ | https://www.usenix.org/conference/usenixsecurity14
This issue of Tor Weekly News has been assembled by XXX, XXX, and
@@ -171,8 +183,6 @@
* Tor Browser alpha 1 ready for QA https://lists.torproject.org/pipermail/tor-qa/2014-August/000436.html
* Sybil attack detection code by Karsten https://github.com/kloesing/SAD and visualization by dcf https://trac.torproject.org/projects/tor/ticket/12813
- * next tor meeting https://lists.torproject.org/pipermail/tor-dev/2014-August/007314.html
- * new PT meeting time https://lists.torproject.org/pipermail/tor-dev/2014-August/007317.html
* OFTC-i2p Relay Bot for #tor/#tor-dev https://lists.torproject.org/pipermail/tor-dev/2014-August/007316.html
* OnionTip.com https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
* Tor Research Framework update https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
version 23
Author: lunar
Date: 2014-08-12T15:16:03+00:00
write about introduction points
--- version 22
+++ version 23
@@ -41,6 +41,41 @@
[XXX]: https://gitweb.torproject.org/torsocks.git/blob/HEAD:/README.md
[XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007330.html
[XXX]: https://lists.torproject.org/pipermail/tor-dev/2013-June/004959.html
+
+Next generation Hidden Services and Introduction Points
+-------------------------------------------------------
+
+When Tor clients need to connect to a Hidden Service, the first step is
+to create a circuit to its “Introduction Point”. There, the Tor client
+serving the Hidden Service will be waiting through another circuit to
+agree on a “Rendez-vous Point” and persue the communication through
+circuits connecting to this freshly selected Tor node.
+
+This general design is not subject to changes with the revision of
+hidden services [XXX] currently being worked on. But there are still
+some questions left unanswered on the best way to select Introduction
+Points. George Kadianakis summarized [XXX] them as: “How many IPs should
+an HS have? Which relays can be IPs? What's the lifetime of an IP?”
+
+For each of these questions, George collected possible answers and how
+they could answer or not to several attacks identified in the past.
+Anyone interested should help with the research needed and join the
+discussion.
+
+In the meantime, Michael Rogers is also trying to find ways [XXX] to
+improve hidden services performance in mobile contexts. One way to do so
+would be to “keep the set of introduction points as stable as possible”.
+But a naive approach of doing so would ease the job of attackers trying
+to locate a hidden service. The idea would be to always use the same
+guard and middle node for a given introduction point. But this might
+also open the doors to new attacks. Michael suggests experimenting with
+the recently published Java research framework [XXX] to get better
+understanding of the implications.
+
+ [XXX]: https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/224-rend-spec-ng.txt
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007335.html
+ [XXX]: https://fulpool.org/pipermail/hidden-services/2014-August/000019.html
+ [XXX]: https://github.com/drgowen/tor-research-framework
More status reports for July 2014
---------------------------------
@@ -142,5 +177,3 @@
* OnionTip.com https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
* Tor Research Framework update https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
* weekly ahmia.fi report https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
- * rebuilding introduction point https://fulpool.org/pipermail/hidden-services/2014-August/000019.html
- * On picking Introduction Points in Next Generation Hidden Services https://lists.torproject.org/pipermail/tor-dev/2014-August/007335.html
version 22
Author: lunar
Date: 2014-08-12T14:52:27+00:00
write about torsocks 2.0
--- version 21
+++ version 22
@@ -12,12 +12,35 @@
Welcome to the thirty-second issue of Tor Weekly News in 2014, the weekly
newsletter that covers what is happening in the XXX Tor community.
-Feature XXX
------------
+Torsocks 2.0 is now considered stable
+-------------------------------------
-Feature 1 with cited source [XXX]
+Torsocks [XXX] is a wrapper program that will force network connections
+of an application to go through the Tor network. David Goulet
+released [XXX] version 2.0.0, blessing the new codebase as stable after
+more than a year of efforts [XXX].
- [XXX]:
+David's original email highlighted several reasons for a complete
+rewrite of torsocks. Among the issues were maintanability, error
+handling, thread safety, lack proper compatibility layer for multiple
+architectures. The new implementation addresses all these issues while
+staying about the same size as the previous version (4000 lines
+of C according to sloccount), and test coverage has been vastly
+extended.
+
+Torsocks comes in handy when some piece of software does not natively
+support using a SOCKS proxy. In most cases, the new version might be
+safer as torsocks will prevent DNS requests and non-torrified
+connections from happening.
+
+Integrators and power users should watch their steps while migrating to
+the new version. The configuration file format has changed, and some
+applications might behave differently as more system calls are now
+restricted.
+
+ [XXX]: https://gitweb.torproject.org/torsocks.git/blob/HEAD:/README.md
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-August/007330.html
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2013-June/004959.html
More status reports for July 2014
---------------------------------
@@ -118,7 +141,6 @@
* OFTC-i2p Relay Bot for #tor/#tor-dev https://lists.torproject.org/pipermail/tor-dev/2014-August/007316.html
* OnionTip.com https://lists.torproject.org/pipermail/tor-relays/2014-August/005073.html https://lists.torproject.org/pipermail/tor-relays/2014-August/005077.html
* Tor Research Framework update https://lists.torproject.org/pipermail/tor-dev/2014-August/007328.html
- * Torsocks 2.0.0 stable https://lists.torproject.org/pipermail/tor-dev/2014-August/007330.html
* weekly ahmia.fi report https://lists.torproject.org/pipermail/tor-reports/2014-August/000620.html
* rebuilding introduction point https://fulpool.org/pipermail/hidden-services/2014-August/000019.html
* On picking Introduction Points in Next Generation Hidden Services https://lists.torproject.org/pipermail/tor-dev/2014-August/007335.html
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/33 ===
===========================================================================
version 1
Author: lunar
Date: 2014-08-12T16:22:30+00:00
import template
---
+++ version 1
@@ -0,0 +1,89 @@
+''59th issue of Tor Weekly News. Covering what's happening from August 12th, 2014 to August 19th, 2014. To be released on August 20th, 2014.''
+
+'''Editor:'''
+
+'''Subject:''' Tor Weekly News — August 20th, 2014
+
+{{{
+========================================================================
+Tor Weekly News August 20th, 2014
+========================================================================
+
+Welcome to the thirty-third 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