[or-cvs] r22762: {website} get some work done on the new website. (in website/branches/web20: about/en en projects/en)
Andrew Lewman
andrew at torproject.org
Sun Aug 1 17:37:01 UTC 2010
Author: phobos
Date: 2010-08-01 17:37:01 +0000 (Sun, 01 Aug 2010)
New Revision: 22762
Added:
website/branches/web20/projects/en/hidserv.wml
Removed:
website/branches/web20/projects/en/hidserv.wml
Modified:
website/branches/web20/about/en/about.wml
website/branches/web20/about/en/board.wml
website/branches/web20/about/en/contact.wml
website/branches/web20/about/en/corepeople.wml
website/branches/web20/about/en/people.wml
website/branches/web20/about/en/sponsors.wml
website/branches/web20/en/home.wml
Log:
get some work done on the new website.
Modified: website/branches/web20/about/en/about.wml
===================================================================
--- website/branches/web20/about/en/about.wml 2010-08-01 14:44:18 UTC (rev 22761)
+++ website/branches/web20/about/en/about.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -2,7 +2,8 @@
# Revision: $Revision: 0 $
# Translation-Priority: 3-low
-#include "head.wmi" TITLE="Tor Project: Tor Overview" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
+#include "head.wmi" TITLE="Tor Project: Tor Overview" CHARSET="UTF-8"
+ANNOUNCE_RSS="yes"
<div id="content" class="clearfix">
<div id="breadcrumbs">
<a href="<page home>">Home » </a>
@@ -10,12 +11,42 @@
</div>
<div id="maincol">
<h1>Tor Overview</h1>
- <p>Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. It also enables software developers to create new communication tools with built-in privacy features. Tor provides the foundation for a range of applications that allow organizations and individuals to share information over public networks without compromising their privacy.</p>
- <p>Individuals use Tor to keep websites from tracking them and their family members, or to connect to news sites, instant messaging services, and the like when these are blocked by their local Internet providers. Tor's <a href="#">hidden services</a> let users publish web sites and other services without needing to reveal the location of the site. Individuals also use Tor for socially sensitive communication: chat rooms and web forums for rape and abuse survivors, or people with illnesses.</p>
- <p>Journalists use Tor to communicate more safely with whistleblowers and dissidents. Non-governmental organizations (NGOs) use Tor to allow their workers to connect to their home website while they're in a foreign country, without notifying everybody nearby that they're working with that organization.</p>
- <p>Groups such as Indymedia recommend Tor for safeguarding their members' online privacy and security. Activist groups like the <a href="http://www.eff.org/">Electronic Frontier Foundation</a> (EFF) recommend Tor as a mechanism for maintaining civil liberties online. Corporations use Tor as a safe way to conduct competitive analysis, and to protect sensitive procurement patterns from eavesdroppers. They also use it to replace traditional VPNs, which reveal the exact amount and timing of communication. Which locations have employees working late? Which locations have employees consulting job-hunting websites? Which research divisions are communicating with the company's patent lawyers?</p>
- <p>A branch of the U.S. Navy uses Tor for open source intelligence gathering, and one of its teams used Tor while deployed in the Middle East recently. Law enforcement uses Tor for visiting or surveilling web sites without leaving government IP addresses in their web logs, and for security during sting operations.</p>
- <p>The <a href="<page about/corepeople>">variety of people</a> who use Tor is actually part of <a href="<page about/overview>">what makes it so secure</a>. Tor hides you among the other users on the network, so the more populous and diverse the user base for Tor is, the more your anonymity will be protected.</p>
+ <p>Tor is a network of virtual tunnels that allows people and groups to
+improve their privacy and security on the Internet. It also enables software
+developers to create new communication tools with built-in privacy features. Tor
+provides the foundation for a range of applications that allow organizations and
+individuals to share information over public networks without compromising their
+privacy.</p>
+ <p>Individuals use Tor to keep websites from tracking them and their family
+members, or to connect to news sites, instant messaging services, and the like
+when these are blocked by their local Internet providers. Tor's <a
+href="<page docs/hidden-services>">hidden services</a> let users publish web sites and other services
+without needing to reveal the location of the site. Individuals also use Tor for
+socially sensitive communication: chat rooms and web forums for rape and abuse
+survivors, or people with illnesses.</p>
+ <p>Journalists use Tor to communicate more safely with whistleblowers and
+dissidents. Non-governmental organizations (NGOs) use Tor to allow their workers
+to connect to their home website while they're in a foreign country, without
+notifying everybody nearby that they're working with that organization.</p>
+ <p>Groups such as Indymedia recommend Tor for safeguarding their members'
+online privacy and security. Activist groups like the <a
+href="http://www.eff.org/">Electronic Frontier Foundation</a> (EFF) recommend
+Tor as a mechanism for maintaining civil liberties online. Corporations use Tor
+as a safe way to conduct competitive analysis, and to protect sensitive
+procurement patterns from eavesdroppers. They also use it to replace traditional
+VPNs, which reveal the exact amount and timing of communication. Which locations
+have employees working late? Which locations have employees consulting
+job-hunting websites? Which research divisions are communicating with the
+company's patent lawyers?</p>
+ <p>A branch of the U.S. Navy uses Tor for open source intelligence
+gathering, and one of its teams used Tor while deployed in the Middle East
+recently. Law enforcement uses Tor for visiting or surveilling web sites without
+leaving government IP addresses in their web logs, and for security during sting
+operations.</p>
+ <p>The <a href="<page about/corepeople>">variety of people</a> who use Tor
+is actually part of <a href="<page about/overview>">what makes it so secure</a>.
+Tor hides you among the other users on the network, so the more populous and
+diverse the user base for Tor is, the more your anonymity will be protected.</p>
</div>
<!-- END MAINCOL -->
<div id = "sidecol">
Modified: website/branches/web20/about/en/board.wml
===================================================================
--- website/branches/web20/about/en/board.wml 2010-08-01 14:44:18 UTC (rev 22761)
+++ website/branches/web20/about/en/board.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -14,50 +14,50 @@
<table>
<tr>
<td class="beige">
- <div class="name">Board Member Name</div>
- <div class="caps">Board Member Title</div>
- <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Roger Dingledine</div>
+ <div class="caps">President and Director</div>
+ <p>Original developer of Tor along with Nick Mathewson and Paul Syverson. Leading researcher in the anonymous communications field. Frequent speaker at conferences to advocate Tor, explain what Tor is and can do, and helps coordinate academic researchers.</p>
+ </td>
+ <td>
+ <div class="name">Meredith Hoban-Dunn</div>
+ <div class="caps">Audit Committee Chair</div>
+ <p>Meredith is an accomplished accountant, advisor, and banker. Her role is to help us make sure we're able to pass our upcoming corporate audits correctly, watch for internal fraud, tell us when we're doing things in a non-standard way, and so on.</p>
</td>
- <td>
- <div class="name">Board Member Name</div>
- <div class="caps">Board Member Title</div>
- <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
- </td>
</tr>
<tr>
<td>
- <div class="name">Board Member Name</div>
- <div class="caps">Board Member Title</div>
- <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Ian Goldberg</div>
+ <div class="caps">Chairman of the Board</div>
+ <p>Cryptographer, privacy expert, and professor; one of the designers of <a href="http://www.cypherpunks.ca/otr/">Off-the-Record Messaging</a>.</p>
</td>
- <td class="beige">
- <div class="name">Board Member Name</div>
- <div class="caps">Board Member Title</div>
- <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <td class="beige">
+ <div class="name">Andrew Lewman</div>
+ <div class="caps">Secretary, Treasurer, and Executive Director</div>
+ <p>Andrew is the Executive Director reponsible for all operations of The Tor Project, Inc. His current activities can be found at <a href="http://lewman.com">his website</a>.</p>
+ </td>
+ </tr>
+ <tr>
+ <td class="beige">
+ <div class="name">Nick Mathewson</div>
+ <div class="caps">Vice-President and Director</div>
+ <p>Nick is one of the original developers of Tor. He's the Chief Architect of The Tor Project, Inc.</p>
+ </td>
+ <td>
+ <div class="name">Xianghui (Isaac) Mao </div>
+ <div class="caps">Director</div>
+ <p>Chinese blogging and privacy activist. His current activities can be found at <a href="http://isaacmao.com/">his website</a>.</p>
</td>
</tr>
<tr>
- <td class="beige">
- <div class="name">Board Member Name</div>
- <div class="caps">Board Member Title</div>
- <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <td>
+ <div class="name">Frank Rieger</div>
+ <div class="caps">Director</div>
+ <p>CTO of <a href="http://www.gsmk.de/">GSMK Cryptophone</a>.</p>
</td>
- <td>
- <div class="name">Board Member Name</div>
- <div class="caps">Board Member Title</div>
- <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
- </td>
- </tr>
- <tr>
- <td>
- <div class="name">Board Member Name</div>
- <div class="caps">Board Member Title</div>
- <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
- </td>
<td class="beige">
- <div class="name">Board Member Name</div>
- <div class="caps">Board Member Title</div>
- <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Wendy Seltzer</div>
+ <div class="caps">Director</div>
+ <p>Lawyer, cyberlaw professor, and founder of <a href="http://chillingeffects.org/">ChillingEffects.org</a>.</p>
</td>
</tr>
</table>
@@ -71,5 +71,5 @@
<!-- END SIDECOL -->
</div>
<!-- END CONTENT -->
-#include <foot.wmi>
-
+#include <foot.wmi>
+
Modified: website/branches/web20/about/en/contact.wml
===================================================================
--- website/branches/web20/about/en/contact.wml 2010-08-01 14:44:18 UTC (rev 22761)
+++ website/branches/web20/about/en/contact.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -12,11 +12,11 @@
</div>
<div id="maincol">
<h2>Tor: Contact</h2>
-
+
<p>First, if you have a problem or question about using Tor, go look at the <a href="<page docs/documentation>#Support">Support section</a> for how to proceed. The Tor developers spend most of their time developing Tor, and there are no people devoted to user support, so try to help yourself before <a href="<page docs/faq>#SupportMail">politely trying to find a volunteer</a>.</p>
-
+
<p>If you really do need to reach us, here are some approaches. All of these addresses are @torproject.org. Note that in practice most of them go to the same small group of people, so please be patient and <a href="http://www.catb.org/~esr/faqs/smart-questions.html">helpful</a>, and please make sure to write your mail in English.</p>
-
+
<ul>
<li><tt>tor-assistants</tt> is the catch-all address for everything. If you'd like to ask a more directed question, please see the descriptions below.</li>
<li><tt>tor-ops</tt> gets to the people who manage the directory authorities. Use this if you run a Tor relay and have a question or problem with your relay.</li>
@@ -36,4 +36,4 @@
<!-- END SIDECOL -->
</div>
<!-- END CONTENT -->
-#include <foot.wmi>
+#include <foot.wmi>
Modified: website/branches/web20/about/en/corepeople.wml
===================================================================
--- website/branches/web20/about/en/corepeople.wml 2010-08-01 14:44:18 UTC (rev 22761)
+++ website/branches/web20/about/en/corepeople.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -9,56 +9,145 @@
<a href="<page about/corepeople>">Tor People</a>
</div>
<div id="maincol">
+
+ <p>The Tor Project is a 501(c)(3) non-profit based in
+ the United States. The official address of the organization is:
+ </p>
+
+ <address>
+ The Tor Project<br />
+ 969 Main Street, Suite 206<br />
+ Walpole, MA 02081-2972 USA<br /><br />
+ </address>
+
+ <p>The organization consists of many volunteers and a few employees.
+ Please don't contact us individually about Tor topics — if you
+ have a problem or question, please look through the <a href="<page
+ about/contact>">contact page</a> for appropriate addresses.</p>
+
<h1>Core Tor People</h1>
<table>
<tr>
<td class="beige">
- <div class="name">Staff Member Name</div>
- <div class="caps">Staff Member Title</div>
- <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Carolyn Anhalt</div>
+ <div class="caps">Community and Translation Coordinator</div>
+ <p>Responsible for growing Tor's community moderators and translators.</p>
</td>
<td>
- <div class="name">Staff Member Name</div>
- <div class="caps">Staff Member Title</div>
- <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Jacob Appelbaum</div>
+ <div class="caps">Developer, Advocate, and Security Researcher</div>
+ <p>Our main advocate. Speaks at conferences and gives trainings all over the world to get people excited about Tor, explain how Tor is used in real world situations, and generally explains why anonymity online matters to you. Original developer of ttdnsd, <a href="https://check.torproject.org/">Tor check</a>, <a href="https://exitlist.torproject.org/">Tor DNSEL</a>, and <a href="https://weather.torproject.org">Tor weather site.</p>
</td>
</tr>
<tr>
<td>
- <div class="name">Staff Member Name</div>
- <div class="caps">Staff Member Title</div>
- <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Erinn Clark</div>
+ <div class="caps">Packaging and Build Automation</div>
+ <p>Erinn is tackling the growing needs for easy to install and configure packages on a variety of operating systems. Also working on automating the build system and producing nightly builds for all operating systems we support.</p>
</td>
<td class="beige">
- <div class="name">Staff Member Name</div>
- <div class="caps">Staff Member Title</div>
- <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Christopher Davis</div>
+ <div class="caps">Libevent hacker and Polipo maintainer</div>
+ <p>Worked during Google Summer of Code 2009 on porting Polipo to Windows and on helping with the libevent bufferevent code. Now he's the Polipo maintainer.</p>
</td>
</tr>
<tr>
<td class="beige">
- <div class="name">Staff Member Name</div>
- <div class="caps">Staff Member Title</div>
- <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Roger Dingledine</div>
+ <div class="caps">Project Leader; Director, Researcher</div>
+ <p>Original developer of Tor along with Nick Mathewson and Paul Syverson. Leading researcher in the anonymous communications field. Frequent speaker at conferences to advocate Tor, explain what Tor is and can do, and helps coordinate academic researchers.</p>
</td>
<td>
- <div class="name">Staff Member Name</div>
- <div class="caps">Staff Member Title</div>
- <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Matt Edman</div>
+ <div class="caps">Vidalia Developer; Researcher</div>
+ <p>Lead developer for <a href="<page projects/vidalia>">Vidalia</a>, a cross-platform Tor GUI included in the bundles.</p>
</td>
</tr>
<tr>
<td>
- <div class="name">Staff Member Name</div>
- <div class="caps">Staff Member Title</div>
- <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Nathan Freitas</div>
+ <div class="caps">Mobile phone hacker</div>
+ <p>The driving force behind Tor on the Android platform in the form of <a href="<page docs/android>">Orbot.</p>
</td>
<td class="beige">
- <div class="name">Staff Member Name</div>
- <div class="caps">Staff Member Title</div>
- <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
+ <div class="name">Christian Fromme</div>
+ <div class="caps">Developer</div>
+ <p>Christian works on all things python for Tor. He enhanced and maintains a slew of codebases for us, such as the get-tor email auto-responder, check.torproject.org, bridge db, tor weather, tor controller, tor flow, etc.</p>
</td>
</tr>
+ <tr>
+ <td class="beige">
+ <div class="name">Melissa Gilroy</div>
+ <div class="caps">CFO and Internal Audit</div>
+ <p>With a strong background in non-profit accounting and auditing, Melissa is in charge of Tor's finances, audit compliance, and keeping Tor's financial operations moving along.</p>
+ </td>
+ <td>
+ <div class="name">Sebastian Hahn</div>
+ <div class="caps">Developer</div>
+ <p>Worked during the 2008 Google Summer of Code on a networking application to automatically carry out tests for Tor and during the 2009 Google Summer of Code on expanding our secure updater to include BitTorrent support. Generally manages out git repository, reviews code patches, and generally helps out a lot.</p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <div class="name">Damian Johnson</div>
+ <div class="caps">ARM Developer</div>
+ <p>Builds a command-line application for monitoring Tor relays, providing real-time status information such as the current
+ configuration, bandwidth usage, message log, etc. (<a href="http://atagar.com/arm">ARM</a>).</p>
+ </td>
+ <td class="beige">
+ <div class="name">Andrew Lewman</div>
+ <div class="caps">Executive Director; Director; <a href="<page press/press>">press contact</a></div>
+ <p>Manages the business operations of The Tor Project, Inc. Plays roles of finance, advocacy, project management, and general support.</p>
+ </td>
+ </tr>
+ <tr>
+ <td class="beige">
+ <div class="name">Dr. Karsten Loesing</div>
+ <div class="caps">Researchers and Developer</div>
+ <p>Worked during the 2007 Google Summer of Code on <a href="<gitblob>doc/spec/proposals/114-distributed-storage.txt">distributing and securing the publishing and fetching of hidden service descriptors</a>. Currently working on <a href="<page projects/hidserv>">making hidden services faster and more reliable</a>, and on <a href="http://metrics.torproject.org/">metrics</a>.</p>
+ </td>
+ <td>
+ <div class="name">Nick Mathewson</div>
+ <div class="caps">Chief Architect, Researcher, Director</div>
+ <p>One of the three original designers of Tor; does a lot of the ongoing design work. One of the two main developers, along with Roger.</p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <div class="name">Dr. Steven Murdoch</div>
+ <div class="caps">Researcher and Developer</div>
+ <p>Researcher at the University of Cambridge, currently funded by The Tor Project to improve the security, performance, and usability of Tor. Creator of the <a href="<page projects/torbrowser>">Tor Browser Bundle</a>.</p>
+ </td>
+ <td class="beige">
+ <div class="name">Peter Palfrader</div>
+ <div class="caps">Sysadmin and Developer</div>
+ <p>Manages the Debian packages, runs one of the directory authorities, runs the website and the wiki, and generally helps out a lot.</p>
+ </td>
+ </tr>
+ <tr>
+ <td class="beige">
+ <div class="name">Mike Perry</div>
+ <div class="caps">Torbutton and Tor Performance Developer</div>
+ <p>Author of <a href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, a Tor controller that builds paths through the Tor network and measures various properties and behaviors, and new author of <a href="<page projects/torbutton>">Torbutton</a>.</p>
+ </td>
+ <td>
+ <div class="name">Karen Reilly</div>
+ <div class="caps">Marketing, Fundraising, and Grant Development Director</div>
+ <p>Responsible for fundraising, advocacy, and general marketing and outreach programs for Tor.</p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <div class="name">Runa A. Sandvik</div>
+ <div class="caps">Translation Coordinator</div>
+ <p>Maintains the <a href="https://translation.torproject.org/">Tor Translation Portal</a>, and works on automatically converting our website wml files to po files (and back) so that they can be handled by <a href="http://translate.sourceforge.net/wiki/pootle/index">Pootle</a>.</p>
+ </td>
+ <td class="beige">
+ <div class="name">Paul Syverson</div>
+ <div class="caps">Researcher</div>
+ <p>Inventor of <a href="http://www.onion-router.net/">Onion Routing</a>, original designer of Tor along with Roger and Nick, and project leader for original design, development, and deployment of Tor. Currently helps out with research and design.</p>
+ </td>
+ </tr>
</table>
<!-- END TABLE -->
@@ -71,4 +160,4 @@
<!-- END SIDECOL -->
</div>
<!-- END CONTENT -->
-#include <foot.wmi>
+#include <foot.wmi>
Modified: website/branches/web20/about/en/people.wml
===================================================================
--- website/branches/web20/about/en/people.wml 2010-08-01 14:44:18 UTC (rev 22761)
+++ website/branches/web20/about/en/people.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -11,7 +11,7 @@
</div>
<div class="maincol">
<h2>Tor: People</h2>
-
+
#<!-- BEGIN SIDEBAR -->
#<div class="sidebar-left">
#<h3>Sections</h3>
@@ -25,82 +25,81 @@
#</ul>
#</div>
#<!-- END SIDEBAR -->
-
+
<p>The Tor Project is a 501(c)(3) non-profit based in
the United States. The official address of the organization is:
</p>
-
+
<address>
The Tor Project<br />
969 Main Street, Suite 206<br />
- Walpole, MA 02081 USA<br /><br />
+ Walpole, MA 02081-2972 USA<br /><br />
</address>
-
+
<p>The organization consists of many volunteers and a few employees.
Please don't contact us individually about Tor topics — if you
have a problem or question, please look through the <a href="<page
about/contact>">contact page</a> for appropriate addresses.</p>
-
+
<div class="underline"></div>
<a id="Core"></a>
<h3><a class="anchor" href="#Core">Core Tor people:</a></h3>
-
+
<dl>
<dt>Carolyn Anhalt (Community and Translation
Coordinator)</dt><dd>Responsible for growing Tor's community
moderators and translators.</dd>
-
+
<dt>Jacob Appelbaum (Developer and Advocate)</dt><dd>Runs
the <a href="https://check.torproject.org/">Tor DNSEL</a> <a
href="http://exitlist.torproject.org/">site</a>, and also the in-progress
Tor weather site.</dd>
-
+
<dt>Erinn Clark (Packaging and Build Automation)</dt><dd>Erinn is tackling
the growing needs for easy to install and configure packages on a variety
of operating systems. Also working on automating the build system and
producing nightly builds for all operating systems we support.</dd>
-
+
<dt>Christopher Davis</dt><dd>Worked during Google Summer of Code 2009
on porting Polipo to Windows and on helping with the libevent bufferevent
code. Now he's the Polipo maintainer.</dd>
-
+
<dt>Roger Dingledine (Project Leader; Director)</dt><dd>Original
developer of Tor; now plays pretty much all the roles to keep everything
on track.</dd>
-
+
<dt>Matt Edman (Developer)</dt><dd>Lead developer for <a href="<page
projects/vidalia>">Vidalia</a>, a cross-platform Tor GUI included in the
Windows and OS X bundles.</dd>
-
+
<dt>Nathan Freitas</dt><dd>The driving force behind Tor on the Android
platform in the form of <a href="<page docs/android>">Orbot</a>.</dd>
-
+
<dt>Christian Fromme (Developer)</dt><dd>Christian works on all things
python for Tor. He enhanced and maintains a slew of codebases for us,
such as the get-tor email auto-responder, check.torproject.org, bridge
db, tor weather, tor controller, tor flow, etc.</dd>
-
+
<dt>Melissa Gilroy (CFO and Internal Audit)</dt><dd>With a strong
background in non-profit accounting and auditing, Melissa is in charge of
Tor's finances, audit compliance, and keeping Tor's financial operations
moving along.</dd>
-
+
<dt>Sebastian Hahn</dt><dd> Worked during the 2008 Google Summer of
Code on a networking application to automatically carry out tests for
Tor and during the 2009 Google Summer of Code on expanding Thandy to
include BitTorrent support. Generally helps out a lot.</dd>
-
+
<dt>Damian Johnson</dt><dd>Builds a command-line application for monitoring
Tor relays, providing real-time status information such as the current
configuration, bandwidth usage, message log, etc. (<a
href="https://svn.torproject.org/svn/arm/trunk/README">code</a>).</dd>
-
+
<dt>Andrew Lewman (Executive Director; Director; <a href="<page
press/press>">press contact</a>)</dt><dd>Manages the business operations
of The Tor Project, Inc. Plays roles of finance, advocacy, project
- management, and general support. General package hacker for Windows,
- OS X, and various linux distributions.</dd>
-
+ management, and general support.</dd>
+
<dt>Karsten Loesing (Developer)</dt><dd>
Worked during the 2007 Google Summer of Code on <a
href="<gitblob>doc/spec/proposals/114-distributed-storage.txt">distributing
@@ -108,76 +107,50 @@
service descriptors</a>. Currently working on <a href="<page
projects/hidserv>">making hidden services faster and more reliable</a>,
and on <a href="http://metrics.torproject.org/">metrics</a>.</dd>
-
+
<dt>Nick Mathewson (Chief architect; Director)</dt><dd>One of the
three original designers of Tor; does a lot of the ongoing design work.
One of the two main developers, along with Roger.</dd>
-
+
<dt>Steven Murdoch (Researcher and Developer)</dt><dd>Researcher at
the University of Cambridge, currently funded by The Tor Project to
improve the security, performance, and usability of Tor. Creator of the
<a href="<page projects/torbrowser>">Tor Browser Bundle</a>.</dd>
-
+
<dt>Peter Palfrader</dt><dd>Manages the Debian packages, runs one of
the directory authorities, runs the website and the wiki, and generally
helps out a lot.</dd>
-
+
<dt>Mike Perry (Developer)</dt><dd>Author of <a
href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>,
a Tor controller that builds paths through the Tor network and measures
various properties and behaviors, and new author of <a href="<page
projects/torbutton>">Torbutton</a>.</dd>
-
+
<dt>Karen Reilly (Development Director)</dt><dd>Responsible for
fundraising, advocacy, and general marketing and outreach programs
for Tor.</dd>
-
+
<dt>Runa A. Sandvik</dt><dd>Maintains the <a
href="https://translation.torproject.org/">Tor Translation
Portal</a>, and works on automatically converting our website wml
files to po files (and back) so that they can be handled by <a
href="http://translate.sourceforge.net/wiki/pootle/index">Pootle</a>.</dd>
-
+
<dt>Paul Syverson</dt><dd>Inventor of <a
href="http://www.onion-router.net/">Onion Routing</a>, original designer
of Tor along with Roger and Nick, and project leader for original design,
development, and deployment of Tor. Currently helps out with research
and design.</dd>
</dl>
-
+
<div class="underline"></div>
- <a id="Board"></a>
- <h3><a class="anchor" href="#Board">The Tor Project Board of
- Directors:</a></h3>
-
- <dl>
- <dt>Meredith Hoban Dunn (Director)</dt><dd>Our audit committee chair. Her
- role is to help us make sure we're able to pass our upcoming corporate
- audits correctly, watch for internal fraud, tell us when we're doing
- things in a non-standard way, and so on.</dd>
-
- <dt>Ian Goldberg (Director)</dt><dd>Cryptographer,
- privacy expert, and professor; one of the designers of <a
- href="http://www.cypherpunks.ca/otr/">Off-the-Record Messaging</a>.</dd>
-
- <dt>Xianghui (Isaac) Mao (Director)</dt><dd>Chinese blogging
- and privacy activist. His current activities can be found at <a
- href="http://isaacmao.com/">his website</a>.</dd>
-
- <dt>Frank Rieger (Director)</dt><dd>CTO of <a
- href="http://www.gsmk.de/">GSMK Cryptophone</a>.</dd>
-
- <dt>Wendy Seltzer (Director)</dt><dd>Lawyer,
- cyberlaw professor, and founder of <a
- href="http://chillingeffects.org/">ChillingEffects.org</a>.</dd>
-
- <dt>Along with Roger, Nick, and Andrew listed above as Directors.</dt>
- </dl>
-
+ <h3><a href="<page about/board>">The Tor Project Board of Directors:</a></h3>
+
<div class="underline"></div>
<a id="GSoC"></a>
<h3><a class="anchor" href="#GSoC">Google Summer of Code 2010 students:</a></h3>
-
+
<dl>
<dt>Kevin Berry</dt><dd>Working on a database schema to support better
node churn metrics and on a more dynamic metrics website. Mentored by
@@ -191,11 +164,11 @@
<dt>John Schanck</dt><dd>Works on improving the automated detection of
misconfigured or malicious exit nodes. Mentored by Mike Perry.</dd>
</dl>
-
+
<div class="underline"></div>
<a id="Translators"></a>
<h3><a class="anchor" href="#Translators">Core translators:</a></h3>
-
+
<dl>
<dt>Bogdan Drozdowski</dt><dd><a
href="https://www.torproject.org/index.html.pl">Polish</a>.</dd>
@@ -218,11 +191,11 @@
<dt>ygrek</dt><dd><a
href="https://www.torproject.org/index.html.ru">Russian</a>.</dd>
</dl>
-
+
<div class="underline"></div>
<a id="Volunteers"></a>
<h3><a class="anchor" href="#Volunteers">More volunteers:</a></h3>
-
+
<dl>
<dt>Anonym</dt><dd>Maintainer of the Incognito LiveCD.</dd>
<dt>Kevin Bankston</dt><dd>EFF lawyer who helped write the <a
@@ -268,11 +241,11 @@
href="http://freehaven.net/anonbib/">research papers</a> about Tor,
people who teach others about Tor, etc.</dt>
</dl>
-
+
<div class="underline"></div>
<a id="Past"></a>
<h3><a class="anchor" href="#Past">Past thanks to:</a></h3>
-
+
<dl>
<dt>John Bashinski</dt><dd> Contributed the initial rpm spec file.</dd>
<dt>Domenik Bork</dt><dd> Worked on
@@ -354,4 +327,4 @@
<!-- END SIDECOL -->
</div>
<!-- END CONTENT -->
-#include <foot.wmi>
+#include <foot.wmi>
Modified: website/branches/web20/about/en/sponsors.wml
===================================================================
--- website/branches/web20/about/en/sponsors.wml 2010-08-01 14:44:18 UTC (rev 22761)
+++ website/branches/web20/about/en/sponsors.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -16,35 +16,35 @@
have a diversity of funding sources too — and we're eager to diversify
even further! Our sponsorships are divided into levels based on total funding received:
</p>
-
+
<h3><i>Magnoliophyta</i> (over $1 million)</h3>
<ul>
- <li>You?</li>
+ <li>An anonymous North American NGO (2008-2010)</li>
</ul>
-
+
<h3><i>Liliopsida</i> (up to $750k)</h3>
<ul>
- <li>An anonymous North American NGO (2008-2010)</li>
+ <li>You or your organization?</li>
</ul>
-
+
<h3><i>Asparagales</i> (up to $500k)</h3>
<ul>
- <li><a href="http://www.ibb.gov/">International Broadcasting Bureau</a> (2006-2010)</li>
+ <li><a href="http://www.bbg.gov/">Broadcasting Board of Governors</a> (2006-2010)</li>
<li>An anonymous European NGO (2006-2008)</li>
</ul>
-
+
<h3><i>Alliaceae</i> (up to $200k)</h3>
<ul>
- <li>You?</li>
+ <li>You or your organization?</li>
</ul>
-
+
<h3><i>Allium</i> (up to $100k)</h3>
<ul>
<li><a href="http://www.nlnet.nl/">NLnet Foundation</a> (2008-2009)</li>
<li><a href="http://chacs.nrl.navy.mil/">Naval Research Laboratory</a> (2006-2010)</li>
<li>An anonymous North American ISP (2009-2010)</li>
</ul>
-
+
<h3><i>Allium cepa</i> (up to $50k)</h3>
<ul>
<li><a href="<page donate/donate>">More than 500 personal donations from individuals like you</a> (2006-2010)</li>
@@ -54,7 +54,7 @@
<li><a href="http://www.torfox.org/">Torfox</a> (2009)</li>
<li><a href="http://www.shinjiru.com/">Shinjiru Technology</a> (2009-2010)</li>
</ul>
-
+
<h3>Past sponsors</h3>
<p>We greatly appreciate the support provided by our past sponsors in keeping the pre-501(c)(3) Tor Project progressing through our ambitious goals:</p>
<ul>
@@ -79,4 +79,4 @@
<!-- END SIDECOL -->
</div>
<!-- END CONTENT -->
-#include <foot.wmi>
+#include <foot.wmi>
Modified: website/branches/web20/en/home.wml
===================================================================
--- website/branches/web20/en/home.wml 2010-08-01 14:44:18 UTC (rev 22761)
+++ website/branches/web20/en/home.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -138,7 +138,7 @@
<div class="user">
<img src="images/consumers.jpg" alt="Consumer Advocates" />
<h3>Consumer Advocates</h3>
- <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
+ <p>NEEDS TEXT.</p>
</div>
<div class="user">
<img src="images/activists.jpg" alt="Activists & Whistleblowers" />
@@ -169,7 +169,7 @@
<tr>
<td>
<div class="calendar"><span class="month">Apr</span><br /><span class="day">27</span></div>
- <p>Tor 0.2.1.24 released as stable. Fixes compatibility with recent Apple OSX openssl changes and adds some performance enhancements.<br /><span class="continue"><a href="#">Read the full list of changes »</a></span></p>
+ <p>Tor 0.2.1.26 released as stable. Fixes compatibility with recent Apple OSX openssl changes and adds some performance enhancements.<br /><span class="continue"><a href="#">Read the full list of changes »</a></span></p>
</td>
</tr>
</table>
Deleted: website/branches/web20/projects/en/hidserv.wml
===================================================================
--- website/branches/web20/projects/en/hidserv.wml 2010-08-01 14:44:18 UTC (rev 22761)
+++ website/branches/web20/projects/en/hidserv.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -1,475 +0,0 @@
-## translation metadata
-# Revision: $Revision: 21511 $
-# Translation-Priority: 4-optional
-
-#include "head.wmi" TITLE="Tor Project: NLnet Project: Speed Up Tor Hidden Services" CHARSET="UTF-8"
-<div id="content" class="clearfix">
- <div id="breadcrumbs">
- <a href="<page home>">Home » </a>
- <a href="<page projects/projects>">Projects » </a>
- <a href="<page projects/hidserv>">NLnet Project</a>
- </div>
- <div id="maincol">
- <!-- PUT CONTENT AFTER THIS TAG -->
-
- <h2>NLnet Project: Speed Up Tor Hidden Services</h2>
- <hr />
-
- <p>
- Tor Hidden Services allow users to set up anonymous information services,
- like websites, that can only be accessed through the Tor network and are
- protected against identification of the host that runs the services.
- The most critical limitations of Tor Hidden Services are the time it takes
- until a Hidden Service is registered in the network and the latency of
- contact establishment when accessed by a user.
- Due to design issues in the original Tor protocol,
- the connection to a new Hidden Service can take several minutes, which
- leads most users to give up before the connection has been established.
- Using Tor Hidden Services for direct interactive user-to-user
- communication (e.g. messaging) is nearly impossible due to the high latency
- of Hidden Service circuit setup.
- </p>
-
- <p>
- This project aims at speeding up Tor Hidden Services by improving the way
- Tor circuits are set up between the user and the Hidden Service as well as
- the way a Hidden Service is registered in the Tor network.
- In a first step precise diagnostics of the behavior of the Hidden Services
- in lab setups and real world situations will be conducted to find the
- root causes of the bad timing effects.
- Based on these diagnostics, optimization strategies will be designed and
- verified for unwanted implications for the security and anonymity of the
- Tor network.
- The most promising optimizations will then be implemented to achieve a
- notable improvement for the users. Precise success metrics will be
- developed in the diagnostics phase, after it becomes clear where the time
- is lost and what improvements are realistic.
- The ultimate goal is to have the Hidden Services protocol change production
- ready and propagated to the Tor users within a timeframe of less than
- 12 months.
- </p>
-
- <p>
- This project is generously funded by:
- </p>
-
- <p>
- <a href="http://www.nlnet.nl/news/2008/20080514-awards.html">
- <img src="$(IMGROOT)/nlnet-160x60.png" alt="The NLnet foundation" /></a>
- </p>
-
- <table width="100%" border="0" cellspacing="0" cellpadding="3">
- <thead>
- <tr>
- <th><big>Project</big></th>
- <th><big>Due Date</big></th>
- </tr>
- </thead>
-
- <tr bgcolor="#e5e5e5">
- <td>
- <b>Deliverable A:</b> Analysis, measurements and problem
- clarification<br />
- <small><em>As Tor Hidden Services have not been actively developed
- further in the last year or so of Tor development, certain aspects of
- the problems are under-diagnosed. To identify the precise sources of
- latency and time loss, an extensive analysis of the deeper reasons for
- them needs to be conducted. Deliverable A will require about one month
- of work. The results of the analysis will influence the design
- decisions to be taken in Deliverable B.</em></small>
- </td>
- <td>
- June 15, 2008
- </td>
- </tr>
-
- <tr>
- <td>
- <b>Deliverable B:</b> Design and evaluation of the necessary
- changes<br />
- <small><em>The changes to Tor Hidden Services will affect core
- functionality of the protocol and therefore require a careful
- evaluation of possible repercussions for the security and anonymity. A
- two-month period is planned for the design and evaluation phase, which
- concludes with an extensive peer review.</em></small>
- </td>
- <td>
- August 15, 2008
- </td>
- </tr>
-
- <tr bgcolor="#e5e5e5">
- <td>
- <b>Deliverable C:</b> Implementation<br />
- <small><em>After design, evaluation and peer review the modifications
- need to be implemented and integrated with the current Tor code base.
- The actual implementation of the necessary changes will take
- approximately two months.</em></small>
- </td>
- <td>
- October 15, 2008
- </td>
- </tr>
-
- <tr>
- <td>
- <b>Deliverable D:</b> Implementation and test of the change up to
- release state<br />
- <small><em>The modification is highly critical to the security and
- anonymity of the Tor network, it requires extensive testing and
- debugging in laboratory and real life conditions. A period of three
- months is projected for testing and debugging, where the responsible
- developer is committed to the testing effort with 1/3 of its time. Part
- of the testing phase will be a public beta period.</em></small>
- </td>
- <td>
- January 15, 2009
- </td>
- </tr>
-
- <tr bgcolor="#e5e5e5">
- <td>
- <b>Deliverable E:</b> Rollout<br />
- <small><em>The actual rollout to the Tor server network will be
- conducted in sync with the regular Tor release schedule. As this
- schedule is dependent on a number of external factors, like the
- completion of other software projects that should go into the same
- release, the actual release time and the time until this release has
- been accepted and installed by most Tor server operators can vary. From
- experience a period of three to four months can be
- expected.</em></small>
- </td>
- <td>
- May 15, 2009
- </td>
- </tr>
- </table>
-
- <br />
-
- <a id="Reports"></a>
- <h2><a class="anchor" href="#Reports">Monthly Status Reports</a></h2>
- <p>
- There will be in total eight monthly status reports beginning with the
- first deliverable on June 15, 2008 and ending with completion of
- implementation and testing work on January 15, 2009.
- </p>
-
- <table width="100%" border="0" cellspacing="0" cellpadding="3">
- <thead>
- <tr>
- <th><big>Month,</big></th>
- <th><big>Status Report</big></th>
- </tr>
- </thead>
-
- <tr bgcolor="#e5e5e5">
- <td>
- <a id="Jun08"></a>
- <a class="anchor" href="#Jun08">Jun 08</a>
- </td>
- <td>
- <small><em>The original goal of analyzing the problems that lead to
- slowdown of Tor Hidden Services has been accomplished. Part of this
- analysis was measuring the delay that a user experiences when
- setting up or accessing a hidden service. Furthermore, measurement data
- from April 2008 could be leveraged to explore timings of internal
- substeps of establishing a connection to a hidden service. The results
- of this analysis are contained in a 22-page
- <a href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">report</a>
- that has been made public on the Tor
- <a href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">developer
- mailing list</a>.</em></small>
- <br/>
- <small><em>The analysis also unveiled a few bugs which were responsible
- for part of the delay in making a hidden service available for
- clients. Some bugs have been fixed subsequent to the analysis, others
- will be fixed soon. The evaluation has further brought up several
- possible approaches to improve Tor Hidden Service performance. Some of
- these ideas can be applied immediately, while others require deeper
- analysis and new measurements. Finally, in the course of the analysis,
- we discovered that some improvements require more in-depth
- changes to Tor which are not directly related to hidden services. These
- changes cannot be achieved in the time frame of this
- project.</em></small>
- </td>
- </tr>
-
- <tr>
- <td>
- <a id="Jul08"></a>
- <a class="anchor" href="#Jul08">Jul 08</a>
- </td>
- <td>
- <small><em>All bugs that have been found in the analysis have been
- fixed. This includes the 2 bugs that have already been fixed during the
- analysis and 4 more bugs that were fixed within the past 30 days. While
- the bugfixes remove unintended performance bottlenecks due to
- programming errors, some of the design changes that have been spotted
- in the previous analysis have side-effects on anonymity or overall
- network load which need to be evaluated against individual performance
- gains. A <a href="http://freehaven.net/~karsten/hidserv/discussion-2008-07-15.pdf">report</a>
- has been published to the
- <a href="http://archives.seul.org/or/dev/Jul-2008/msg00034.html">developer
- mailing list</a> including 7 possible design changes that need to be
- discussed. Some evaluations (namely Low-Bandwidth Measurements and the
- Grand Scaling Plan) have turned out to require more time than expected
- and had to be scheduled for a later time in the project than
- deliverable B. The current plan is to perform these evaluations within
- the timeframe until January 15 and work with assumptions until final
- results are available.</em></small>
- </td>
- </tr>
-
- <tr bgcolor="#e5e5e5">
- <td>
- <a id="Aug08"></a>
- <a class="anchor" href="#Aug08">Aug 08</a>
- </td>
- <td>
- <small><em>During the past 30 days the 7 proposed designs have been
- further evaluated and discussed. Four of them have proven to be
- applicable in terms of the required changes to the code and possible
- anonymity implications. One has been classified as bug rather than
- design change. Two had to be excluded for either unforeseeable security
- problems, or uncertainty of actual performance
- improvements.</em></small>
- <br/>
- <small><em>Together with the results from July 15, the design phase has
- been concluded. The tasks for the upcoming implementation phase are now
- quite clear: One bug needs to be fixed and four design changes need to
- be implemented. Further, evaluations of the changed design need to be
- performed in order to verify their usefulness. A
- <a href="http://freehaven.net/~karsten/hidserv/design-2008-08-15.pdf">report</a>
- with the results of the design phase has been published to the
- <a href="http://archives.seul.org/or/dev/Aug-2008/msg00025.html">developer
- mailing list</a>.</em></small>
- </td>
- </tr>
-
- <tr>
- <td>
- <a id="Sep08"></a>
- <a class="anchor" href="#Sep08">Sep 08</a>
- </td>
- <td>
- <small><em>During the first half of the implementation phase two bugs
- could be fixed that were related to hidden services: the
- <a href="http://bugs.noreply.org/flyspray/index.php?do=details&id=767">first
- bug</a> has already been identified in the design phase and was
- responsible for an unusual high failure rate when making a hidden
- service available in the system; the
- <a href="http://bugs.noreply.org/flyspray/index.php?id=814&do=details">second
- bug</a> was found during the implementation phase and was responsible
- for failure to connect to a working hidden service. Both bugfixes will
- be included in the next unstable version and likely be backported to
- one of the next stable releases.</em></small>
- <br/>
- <small><em>The four design changes that were proposed as result of the
- design phase have been implemented in an
- <a href="https://tor-svn.freehaven.net/svn/tor/branches/hidserv-design-changes/">experimental
- branch</a> of the unstable development tree. Early function tests have
- shown that these changes work and provide better (perceived)
- performance. This needs to be confirmed throughout the next four weeks
- in internal tests. The next goal is to prepare a release of this
- experimental branch that can be given out to beta testers at the
- beginning of the upcoming testing phase.</em></small>
- </td>
- </tr>
-
- <tr bgcolor="#e5e5e5">
- <td>
- <a id="Oct08"></a>
- <a class="anchor" href="#Oct08">Oct 08</a>
- </td>
- <td>
- <small><em>The implementation phase has been concluded. The bugfixes
- that were found in the past 30 days have been released in developer
- version <a href="http://archives.seul.org/or/talk/Oct-2008/msg00093.html">0.2.1.6-alpha</a>.
- The four design changes that were identified in the design phase have
- been specified in
- <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/155-four-hidden-service-improvements.txt">proposal 155</a>.
- Three design changes have been included in the development codebase and
- will automatically be included in the next development version. The
- first two design changes improve connection establishment to a hidden
- service by reducing a timeout from 60 to 30 seconds and by making a
- second attempt in parallel after a delay of 15 seconds. The third
- design change affects publication of a hidden service in the network by
- advertising the service at 5 rather than 3 points in the network in
- parallel and succeeding as soon as 3 points are established. The fourth
- design change has turned out to be rather ineffective, but would add
- considerable code complexity and was therefore dismissed. By now there
- are no more open bugfixes or new designs. All changes are in the
- development codebase and can be tested in the next phase.</em></small>
- </td>
- </tr>
-
- <tr>
- <td>
- <a id="Nov08"></a>
- <a class="anchor" href="#Nov08">Nov 08</a>
- </td>
- <td>
- <small><em>The performance improvements that were implemented in the
- last phase have been released in Tor version 0.2.1.7-alpha. Users can
- download this development version from the Tor homepage and test the
- improvements with minimal effort. Further, two bugfixes (<a
- href="http://bugs.noreply.org/flyspray/index.php?id=767&do=details">1</a>,
- <a href="http://bugs.noreply.org/flyspray/index.php?id=814&do=details">2</a>)
- that were found in the course of this project have been backported to
- the stable branch and will be included with the next stable version
- 0.2.0.32.</em></small>
- <br/>
- <small><em>The main focus of the past 31 days was to perform new
- measurements to see whether the improvements are effective or not.
- Measurements were conducted for two days in the time of November 6th to
- 8th. Unfortunately, the Tor network suffered a serious problem in this
- time: An expired directory authority certificate produced huge amounts
- of traffic within the Tor network which <a
- href="http://archives.seul.org/or/talk/Nov-2008/msg00053.html">forced
- many operators to shut down their relays</a>. A second measurement was
- performed between 13th and 15th. The raw data are available <a
- href="http://freehaven.net/~karsten/hidserv/perfdata-2008-11-13.tar.gz">here</a>
- (40 MB). But results show that the overall
- network performance is still worse than in June 2008 when the first
- hidden service measurements have been performed. This becomes visible
- when comparing requests to the Tor directories which have not been
- affected by the performance improvements and which exhibit
- significantly worse performance than before. The effects of performance
- improvements are visible, but absolute values are not comparable at
- this time. New measurements will be conducted in December in the hope
- that the effects of this problem have mitigated.</em></small>
- <br/>
- <small><em>Further, there might be a <a
- href="http://bugs.noreply.org/flyspray/index.php?id=847&do=details">bug</a>
- in the way how Tor downloads directory information during
- bootstrapping. Even though this is not related to hidden services, an
- improvement would benefit hidden service publication, too. Part of the
- work during the upcoming 30 days will be to investigate this bug.
- </em></small>
- </td>
- </tr>
-
- <tr bgcolor="#e5e5e5">
- <td>
- <a id="Dec08"></a>
- <a class="anchor" href="#Dec08">Dec 08</a>
- </td>
- <td>
- <small><em>Part of the last 30 days has been used to fix bugs that have
- influenced the previous hidden service measurements. The first <a
- href="http://archives.seul.org/or/cvs/Nov-2008/msg00100.html">bugfix</a>
- corrects a possible segmentation fault that was very likely responsible
- for a number of failed measurement runs. Another <a
- href="https://bugs.torproject.org/flyspray/index.php?id=847&do=details">bug</a>
- could be explained that lead to significant delays in bootstrapping:
- Very slow directory authorities occupied bootstrapping clients for
- a long time before clients finally gave up and bootstrapped using
- another authority. As a result, the slowest two directory authorities
- have dedicated more bandwidth to their nodes, so that the effect is
- mitigated. A third <a
- href="https://bugs.torproject.org/flyspray/index.php?id=874&do=details">bug</a>
- has been introduced with the hidden service performance improvements in
- November; the effect was that Tor processes running hidden services
- would stop advertising their service upon reloading their
- configuration. Further, this bug has uncovered that Tor has
- re-established its introduction points upon reloading, which might have
- affected hidden service stability. This bug has been fixed and will be
- included in the upcoming version 0.2.1.9-alpha.</em></small>
- <br/>
- <small><em>Apart from fixing bugs, new measurements have been performed
- between December 8 and 10. These will very likely be the final
- measurements to compare hidden service performance now with the
- beginning of the project. The data have not been completely evaluated,
- so it is difficult to make a statement about improvements at this
- point. However, a <a
- href="http://freehaven.net/~karsten/hidserv/prelimreport-2008-12-15.pdf">preliminary
- evaluation</a> shows that service publication times have improved
- significantly. This is a result of Tor clients bootstrapping faster and
- of the performance improvements added in November. In contrast to this,
- the results for establishing a connection to a hidden service are less
- promising. While the improvements added in November seem to have a
- positive effect on performance, some substeps exhibit significantly
- worse performance. One example is fetching hidden service descriptors
- in order to contact a hidden service. A possible explanation is that
- the sudden increase in the number of hidden service directory nodes in
- September has had a negative effect on performance. Part of the work in
- the final 31 days will be to evaluate these data in more detail and
- make a final conclusion on the achievements of this
- project.</em></small>
- </td>
- </tr>
-
- <tr>
- <td>
- <a id="Jan09"></a>
- <a class="anchor" href="#Jan09">Jan 09</a>
- </td>
- <td>
- <small><em>The testing phase has been concluded. Testing was performed
- in a public beta phase with all changes to hidden services being part
- of the 0.2.1.x-alpha series. The result of the public beta phase is a
- couple of identified bugs that could already be fixed.</em></small>
- <br/>
- <small><em>Another part of testing was a second set of measurements
- that was performed in December. A
- <a href="http://freehaven.net/~karsten/hidserv/comparison-2009-01-15.pdf">comparison</a>
- of measurements performed in June and December has revealed that the
- changes of this project are effective. Service publication times could
- be more than halved from 2:12 minutes to 58 seconds in the mean. This
- improvement is far better than expected. With this improvement it might
- even be worthwile to think about reducing stabilization time from 30
- seconds to a lower value in the future. However, connection
- establishment remains at approximately 56 seconds between requesting a
- hidden service to having established a connection to the hidden server.
- The main reason for missing improvements is the switch from the
- centralized to a decentralized storage for hidden service descriptors.
- This deteriorating effect of distributing the hidden service directory
- has not been expected before. Future work should focus on improving
- downloads from the distributed hidden service directory, for example by
- parallelizing requests.</em></small>
- <br/>
- <small><em>This report concludes the series of monthly status updates.
- The rollout of the 0.2.1.x series including the hidden service
- performance improvements is going to take place within the next weeks
- to months.</em></small>
- </td>
- </tr>
- </table>
-
- <br />
-
- <!-- Do we want a people section? If so, would it make sense to write what
- these people will be doing? And what exactly are these people going to
- do? :)
- <a id="People"></a>
- <h2><a class="anchor" href="#People">People</a></h2>
- <ul>
- <li><a href="<page about/people>#Core">Karsten Loesing</a></li>
- <li><a href="<page about/people>#Core">Steven Murdoch</a></li>
- </ul>
- -->
-
- <a id="Links"></a>
- <h2><a class="anchor" href="#Links">Links</a></h2>
- <ul>
- <li>Research paper on <b>Performance Measurements and Statistics of Tor
- Hidden Services</b>
- (<a href="http://www.uni-bamberg.de/fileadmin/uni/fakultaeten/wiai_lehrstuehle/praktische_informatik/Dateien/Publikationen/loesing2008performance.pdf">PDF</a>)
- by Karsten Loesing, Werner Sandmann, Christian Wilms, and Guido Wirtz. In
- the Proceedings of the 2008 International Symposium on Applications and the
- Internet (SAINT), Turku, Finland, July 2008.</li>
-
- <!-- In the future, put links to proposal, preliminary results, etc. here -->
-
- </ul>
- </div>
- <!-- END MAINCOL -->
- <div id = "sidecol">
-#include "side.wmi"
-#include "info.wmi"
- </div>
- <!-- END SIDECOL -->
-</div>
-<!-- END CONTENT -->
-#include <foot.wmi>
Added: website/branches/web20/projects/en/hidserv.wml
===================================================================
--- website/branches/web20/projects/en/hidserv.wml (rev 0)
+++ website/branches/web20/projects/en/hidserv.wml 2010-08-01 17:37:01 UTC (rev 22762)
@@ -0,0 +1,475 @@
+## translation metadata
+# Revision: $Revision: 21511 $
+# Translation-Priority: 4-optional
+
+#include "head.wmi" TITLE="Tor Project: NLnet Project: Speed Up Tor Hidden Services" CHARSET="UTF-8"
+<div id="content" class="clearfix">
+ <div id="breadcrumbs">
+ <a href="<page home>">Home » </a>
+ <a href="<page projects/projects>">Projects » </a>
+ <a href="<page projects/hidserv>">NLnet Project</a>
+ </div>
+ <div id="maincol">
+ <!-- PUT CONTENT AFTER THIS TAG -->
+
+ <h2>NLnet Project: Speed Up Tor Hidden Services</h2>
+ <hr />
+
+ <p>
+ Tor Hidden Services allow users to set up anonymous information services,
+ like websites, that can only be accessed through the Tor network and are
+ protected against identification of the host that runs the services.
+ The most critical limitations of Tor Hidden Services are the time it takes
+ until a Hidden Service is registered in the network and the latency of
+ contact establishment when accessed by a user.
+ Due to design issues in the original Tor protocol,
+ the connection to a new Hidden Service can take several minutes, which
+ leads most users to give up before the connection has been established.
+ Using Tor Hidden Services for direct interactive user-to-user
+ communication (e.g. messaging) is nearly impossible due to the high latency
+ of Hidden Service circuit setup.
+ </p>
+
+ <p>
+ This project aims at speeding up Tor Hidden Services by improving the way
+ Tor circuits are set up between the user and the Hidden Service as well as
+ the way a Hidden Service is registered in the Tor network.
+ In a first step precise diagnostics of the behavior of the Hidden Services
+ in lab setups and real world situations will be conducted to find the
+ root causes of the bad timing effects.
+ Based on these diagnostics, optimization strategies will be designed and
+ verified for unwanted implications for the security and anonymity of the
+ Tor network.
+ The most promising optimizations will then be implemented to achieve a
+ notable improvement for the users. Precise success metrics will be
+ developed in the diagnostics phase, after it becomes clear where the time
+ is lost and what improvements are realistic.
+ The ultimate goal is to have the Hidden Services protocol change production
+ ready and propagated to the Tor users within a timeframe of less than
+ 12 months.
+ </p>
+
+ <p>
+ This project is generously funded by:
+ </p>
+
+ <p>
+ <a href="http://www.nlnet.nl/news/2008/20080514-awards.html">
+ <img src="$(IMGROOT)/nlnet-160x60.png" alt="The NLnet foundation" /></a>
+ </p>
+
+ <table width="100%" border="0" cellspacing="0" cellpadding="3">
+ <thead>
+ <tr>
+ <th><big>Project</big></th>
+ <th><big>Due Date</big></th>
+ </tr>
+ </thead>
+
+ <tr bgcolor="#e5e5e5">
+ <td>
+ <b>Deliverable A:</b> Analysis, measurements and problem
+ clarification<br />
+ <small><em>As Tor Hidden Services have not been actively developed
+ further in the last year or so of Tor development, certain aspects of
+ the problems are under-diagnosed. To identify the precise sources of
+ latency and time loss, an extensive analysis of the deeper reasons for
+ them needs to be conducted. Deliverable A will require about one month
+ of work. The results of the analysis will influence the design
+ decisions to be taken in Deliverable B.</em></small>
+ </td>
+ <td>
+ June 15, 2008
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <b>Deliverable B:</b> Design and evaluation of the necessary
+ changes<br />
+ <small><em>The changes to Tor Hidden Services will affect core
+ functionality of the protocol and therefore require a careful
+ evaluation of possible repercussions for the security and anonymity. A
+ two-month period is planned for the design and evaluation phase, which
+ concludes with an extensive peer review.</em></small>
+ </td>
+ <td>
+ August 15, 2008
+ </td>
+ </tr>
+
+ <tr bgcolor="#e5e5e5">
+ <td>
+ <b>Deliverable C:</b> Implementation<br />
+ <small><em>After design, evaluation and peer review the modifications
+ need to be implemented and integrated with the current Tor code base.
+ The actual implementation of the necessary changes will take
+ approximately two months.</em></small>
+ </td>
+ <td>
+ October 15, 2008
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <b>Deliverable D:</b> Implementation and test of the change up to
+ release state<br />
+ <small><em>The modification is highly critical to the security and
+ anonymity of the Tor network, it requires extensive testing and
+ debugging in laboratory and real life conditions. A period of three
+ months is projected for testing and debugging, where the responsible
+ developer is committed to the testing effort with 1/3 of its time. Part
+ of the testing phase will be a public beta period.</em></small>
+ </td>
+ <td>
+ January 15, 2009
+ </td>
+ </tr>
+
+ <tr bgcolor="#e5e5e5">
+ <td>
+ <b>Deliverable E:</b> Rollout<br />
+ <small><em>The actual rollout to the Tor server network will be
+ conducted in sync with the regular Tor release schedule. As this
+ schedule is dependent on a number of external factors, like the
+ completion of other software projects that should go into the same
+ release, the actual release time and the time until this release has
+ been accepted and installed by most Tor server operators can vary. From
+ experience a period of three to four months can be
+ expected.</em></small>
+ </td>
+ <td>
+ May 15, 2009
+ </td>
+ </tr>
+ </table>
+
+ <br />
+
+ <a id="Reports"></a>
+ <h2><a class="anchor" href="#Reports">Monthly Status Reports</a></h2>
+ <p>
+ There will be in total eight monthly status reports beginning with the
+ first deliverable on June 15, 2008 and ending with completion of
+ implementation and testing work on January 15, 2009.
+ </p>
+
+ <table width="100%" border="0" cellspacing="0" cellpadding="3">
+ <thead>
+ <tr>
+ <th><big>Month,</big></th>
+ <th><big>Status Report</big></th>
+ </tr>
+ </thead>
+
+ <tr bgcolor="#e5e5e5">
+ <td>
+ <a id="Jun08"></a>
+ <a class="anchor" href="#Jun08">Jun 08</a>
+ </td>
+ <td>
+ <small><em>The original goal of analyzing the problems that lead to
+ slowdown of Tor Hidden Services has been accomplished. Part of this
+ analysis was measuring the delay that a user experiences when
+ setting up or accessing a hidden service. Furthermore, measurement data
+ from April 2008 could be leveraged to explore timings of internal
+ substeps of establishing a connection to a hidden service. The results
+ of this analysis are contained in a 22-page
+ <a href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">report</a>
+ that has been made public on the Tor
+ <a href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">developer
+ mailing list</a>.</em></small>
+ <br/>
+ <small><em>The analysis also unveiled a few bugs which were responsible
+ for part of the delay in making a hidden service available for
+ clients. Some bugs have been fixed subsequent to the analysis, others
+ will be fixed soon. The evaluation has further brought up several
+ possible approaches to improve Tor Hidden Service performance. Some of
+ these ideas can be applied immediately, while others require deeper
+ analysis and new measurements. Finally, in the course of the analysis,
+ we discovered that some improvements require more in-depth
+ changes to Tor which are not directly related to hidden services. These
+ changes cannot be achieved in the time frame of this
+ project.</em></small>
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <a id="Jul08"></a>
+ <a class="anchor" href="#Jul08">Jul 08</a>
+ </td>
+ <td>
+ <small><em>All bugs that have been found in the analysis have been
+ fixed. This includes the 2 bugs that have already been fixed during the
+ analysis and 4 more bugs that were fixed within the past 30 days. While
+ the bugfixes remove unintended performance bottlenecks due to
+ programming errors, some of the design changes that have been spotted
+ in the previous analysis have side-effects on anonymity or overall
+ network load which need to be evaluated against individual performance
+ gains. A <a href="http://freehaven.net/~karsten/hidserv/discussion-2008-07-15.pdf">report</a>
+ has been published to the
+ <a href="http://archives.seul.org/or/dev/Jul-2008/msg00034.html">developer
+ mailing list</a> including 7 possible design changes that need to be
+ discussed. Some evaluations (namely Low-Bandwidth Measurements and the
+ Grand Scaling Plan) have turned out to require more time than expected
+ and had to be scheduled for a later time in the project than
+ deliverable B. The current plan is to perform these evaluations within
+ the timeframe until January 15 and work with assumptions until final
+ results are available.</em></small>
+ </td>
+ </tr>
+
+ <tr bgcolor="#e5e5e5">
+ <td>
+ <a id="Aug08"></a>
+ <a class="anchor" href="#Aug08">Aug 08</a>
+ </td>
+ <td>
+ <small><em>During the past 30 days the 7 proposed designs have been
+ further evaluated and discussed. Four of them have proven to be
+ applicable in terms of the required changes to the code and possible
+ anonymity implications. One has been classified as bug rather than
+ design change. Two had to be excluded for either unforeseeable security
+ problems, or uncertainty of actual performance
+ improvements.</em></small>
+ <br/>
+ <small><em>Together with the results from July 15, the design phase has
+ been concluded. The tasks for the upcoming implementation phase are now
+ quite clear: One bug needs to be fixed and four design changes need to
+ be implemented. Further, evaluations of the changed design need to be
+ performed in order to verify their usefulness. A
+ <a href="http://freehaven.net/~karsten/hidserv/design-2008-08-15.pdf">report</a>
+ with the results of the design phase has been published to the
+ <a href="http://archives.seul.org/or/dev/Aug-2008/msg00025.html">developer
+ mailing list</a>.</em></small>
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <a id="Sep08"></a>
+ <a class="anchor" href="#Sep08">Sep 08</a>
+ </td>
+ <td>
+ <small><em>During the first half of the implementation phase two bugs
+ could be fixed that were related to hidden services: the
+ <a href="http://bugs.noreply.org/flyspray/index.php?do=details&id=767">first
+ bug</a> has already been identified in the design phase and was
+ responsible for an unusual high failure rate when making a hidden
+ service available in the system; the
+ <a href="http://bugs.noreply.org/flyspray/index.php?id=814&do=details">second
+ bug</a> was found during the implementation phase and was responsible
+ for failure to connect to a working hidden service. Both bugfixes will
+ be included in the next unstable version and likely be backported to
+ one of the next stable releases.</em></small>
+ <br/>
+ <small><em>The four design changes that were proposed as result of the
+ design phase have been implemented in an
+ <a href="https://tor-svn.freehaven.net/svn/tor/branches/hidserv-design-changes/">experimental
+ branch</a> of the unstable development tree. Early function tests have
+ shown that these changes work and provide better (perceived)
+ performance. This needs to be confirmed throughout the next four weeks
+ in internal tests. The next goal is to prepare a release of this
+ experimental branch that can be given out to beta testers at the
+ beginning of the upcoming testing phase.</em></small>
+ </td>
+ </tr>
+
+ <tr bgcolor="#e5e5e5">
+ <td>
+ <a id="Oct08"></a>
+ <a class="anchor" href="#Oct08">Oct 08</a>
+ </td>
+ <td>
+ <small><em>The implementation phase has been concluded. The bugfixes
+ that were found in the past 30 days have been released in developer
+ version <a href="http://archives.seul.org/or/talk/Oct-2008/msg00093.html">0.2.1.6-alpha</a>.
+ The four design changes that were identified in the design phase have
+ been specified in
+ <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/155-four-hidden-service-improvements.txt">proposal 155</a>.
+ Three design changes have been included in the development codebase and
+ will automatically be included in the next development version. The
+ first two design changes improve connection establishment to a hidden
+ service by reducing a timeout from 60 to 30 seconds and by making a
+ second attempt in parallel after a delay of 15 seconds. The third
+ design change affects publication of a hidden service in the network by
+ advertising the service at 5 rather than 3 points in the network in
+ parallel and succeeding as soon as 3 points are established. The fourth
+ design change has turned out to be rather ineffective, but would add
+ considerable code complexity and was therefore dismissed. By now there
+ are no more open bugfixes or new designs. All changes are in the
+ development codebase and can be tested in the next phase.</em></small>
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <a id="Nov08"></a>
+ <a class="anchor" href="#Nov08">Nov 08</a>
+ </td>
+ <td>
+ <small><em>The performance improvements that were implemented in the
+ last phase have been released in Tor version 0.2.1.7-alpha. Users can
+ download this development version from the Tor homepage and test the
+ improvements with minimal effort. Further, two bugfixes (<a
+ href="http://bugs.noreply.org/flyspray/index.php?id=767&do=details">1</a>,
+ <a href="http://bugs.noreply.org/flyspray/index.php?id=814&do=details">2</a>)
+ that were found in the course of this project have been backported to
+ the stable branch and will be included with the next stable version
+ 0.2.0.32.</em></small>
+ <br/>
+ <small><em>The main focus of the past 31 days was to perform new
+ measurements to see whether the improvements are effective or not.
+ Measurements were conducted for two days in the time of November 6th to
+ 8th. Unfortunately, the Tor network suffered a serious problem in this
+ time: An expired directory authority certificate produced huge amounts
+ of traffic within the Tor network which <a
+ href="http://archives.seul.org/or/talk/Nov-2008/msg00053.html">forced
+ many operators to shut down their relays</a>. A second measurement was
+ performed between 13th and 15th. The raw data are available <a
+ href="http://freehaven.net/~karsten/hidserv/perfdata-2008-11-13.tar.gz">here</a>
+ (40 MB). But results show that the overall
+ network performance is still worse than in June 2008 when the first
+ hidden service measurements have been performed. This becomes visible
+ when comparing requests to the Tor directories which have not been
+ affected by the performance improvements and which exhibit
+ significantly worse performance than before. The effects of performance
+ improvements are visible, but absolute values are not comparable at
+ this time. New measurements will be conducted in December in the hope
+ that the effects of this problem have mitigated.</em></small>
+ <br/>
+ <small><em>Further, there might be a <a
+ href="http://bugs.noreply.org/flyspray/index.php?id=847&do=details">bug</a>
+ in the way how Tor downloads directory information during
+ bootstrapping. Even though this is not related to hidden services, an
+ improvement would benefit hidden service publication, too. Part of the
+ work during the upcoming 30 days will be to investigate this bug.
+ </em></small>
+ </td>
+ </tr>
+
+ <tr bgcolor="#e5e5e5">
+ <td>
+ <a id="Dec08"></a>
+ <a class="anchor" href="#Dec08">Dec 08</a>
+ </td>
+ <td>
+ <small><em>Part of the last 30 days has been used to fix bugs that have
+ influenced the previous hidden service measurements. The first <a
+ href="http://archives.seul.org/or/cvs/Nov-2008/msg00100.html">bugfix</a>
+ corrects a possible segmentation fault that was very likely responsible
+ for a number of failed measurement runs. Another <a
+ href="https://bugs.torproject.org/flyspray/index.php?id=847&do=details">bug</a>
+ could be explained that lead to significant delays in bootstrapping:
+ Very slow directory authorities occupied bootstrapping clients for
+ a long time before clients finally gave up and bootstrapped using
+ another authority. As a result, the slowest two directory authorities
+ have dedicated more bandwidth to their nodes, so that the effect is
+ mitigated. A third <a
+ href="https://bugs.torproject.org/flyspray/index.php?id=874&do=details">bug</a>
+ has been introduced with the hidden service performance improvements in
+ November; the effect was that Tor processes running hidden services
+ would stop advertising their service upon reloading their
+ configuration. Further, this bug has uncovered that Tor has
+ re-established its introduction points upon reloading, which might have
+ affected hidden service stability. This bug has been fixed and will be
+ included in the upcoming version 0.2.1.9-alpha.</em></small>
+ <br/>
+ <small><em>Apart from fixing bugs, new measurements have been performed
+ between December 8 and 10. These will very likely be the final
+ measurements to compare hidden service performance now with the
+ beginning of the project. The data have not been completely evaluated,
+ so it is difficult to make a statement about improvements at this
+ point. However, a <a
+ href="http://freehaven.net/~karsten/hidserv/prelimreport-2008-12-15.pdf">preliminary
+ evaluation</a> shows that service publication times have improved
+ significantly. This is a result of Tor clients bootstrapping faster and
+ of the performance improvements added in November. In contrast to this,
+ the results for establishing a connection to a hidden service are less
+ promising. While the improvements added in November seem to have a
+ positive effect on performance, some substeps exhibit significantly
+ worse performance. One example is fetching hidden service descriptors
+ in order to contact a hidden service. A possible explanation is that
+ the sudden increase in the number of hidden service directory nodes in
+ September has had a negative effect on performance. Part of the work in
+ the final 31 days will be to evaluate these data in more detail and
+ make a final conclusion on the achievements of this
+ project.</em></small>
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <a id="Jan09"></a>
+ <a class="anchor" href="#Jan09">Jan 09</a>
+ </td>
+ <td>
+ <small><em>The testing phase has been concluded. Testing was performed
+ in a public beta phase with all changes to hidden services being part
+ of the 0.2.1.x-alpha series. The result of the public beta phase is a
+ couple of identified bugs that could already be fixed.</em></small>
+ <br/>
+ <small><em>Another part of testing was a second set of measurements
+ that was performed in December. A
+ <a href="http://freehaven.net/~karsten/hidserv/comparison-2009-01-15.pdf">comparison</a>
+ of measurements performed in June and December has revealed that the
+ changes of this project are effective. Service publication times could
+ be more than halved from 2:12 minutes to 58 seconds in the mean. This
+ improvement is far better than expected. With this improvement it might
+ even be worthwile to think about reducing stabilization time from 30
+ seconds to a lower value in the future. However, connection
+ establishment remains at approximately 56 seconds between requesting a
+ hidden service to having established a connection to the hidden server.
+ The main reason for missing improvements is the switch from the
+ centralized to a decentralized storage for hidden service descriptors.
+ This deteriorating effect of distributing the hidden service directory
+ has not been expected before. Future work should focus on improving
+ downloads from the distributed hidden service directory, for example by
+ parallelizing requests.</em></small>
+ <br/>
+ <small><em>This report concludes the series of monthly status updates.
+ The rollout of the 0.2.1.x series including the hidden service
+ performance improvements is going to take place within the next weeks
+ to months.</em></small>
+ </td>
+ </tr>
+ </table>
+
+ <br />
+
+ <!-- Do we want a people section? If so, would it make sense to write what
+ these people will be doing? And what exactly are these people going to
+ do? :)
+ <a id="People"></a>
+ <h2><a class="anchor" href="#People">People</a></h2>
+ <ul>
+ <li><a href="<page about/people>#Core">Karsten Loesing</a></li>
+ <li><a href="<page about/people>#Core">Steven Murdoch</a></li>
+ </ul>
+ -->
+
+ <a id="Links"></a>
+ <h2><a class="anchor" href="#Links">Links</a></h2>
+ <ul>
+ <li>Research paper on <b>Performance Measurements and Statistics of Tor
+ Hidden Services</b>
+ (<a href="http://www.uni-bamberg.de/fileadmin/uni/fakultaeten/wiai_lehrstuehle/praktische_informatik/Dateien/Publikationen/loesing2008performance.pdf">PDF</a>)
+ by Karsten Loesing, Werner Sandmann, Christian Wilms, and Guido Wirtz. In
+ the Proceedings of the 2008 International Symposium on Applications and the
+ Internet (SAINT), Turku, Finland, July 2008.</li>
+
+ <!-- In the future, put links to proposal, preliminary results, etc. here -->
+
+ </ul>
+ </div>
+ <!-- END MAINCOL -->
+ <div id = "sidecol">
+#include "side.wmi"
+#include "info.wmi"
+ </div>
+ <!-- END SIDECOL -->
+</div>
+<!-- END CONTENT -->
+#include <foot.wmi>
More information about the tor-commits
mailing list