Added page for NLnet Hidden Services project.
Karsten Loesing commited on 2008-05-27 22:45:18
Zeige 1 geänderte Dateien mit 187 Einfügungen und 0 Löschungen.
- projects/en/hidserv.wml 000000000..127f14fc8
| ... | ... |
@@ -0,0 +1,187 @@ |
| 1 |
+## translation metadata |
|
| 2 |
+# Revision: $Revision: 14486 $ |
|
| 3 |
+# Translation-Priority: 3-low |
|
| 4 |
+ |
|
| 5 |
+#include "head.wmi" TITLE="NLnet Project: Speed Up Tor Hidden Services" |
|
| 6 |
+ |
|
| 7 |
+<div class="main-column"> |
|
| 8 |
+ |
|
| 9 |
+<!-- PUT CONTENT AFTER THIS TAG --> |
|
| 10 |
+ |
|
| 11 |
+<h2>NLnet Project: Speed Up Tor Hidden Services</h2> |
|
| 12 |
+<hr /> |
|
| 13 |
+ |
|
| 14 |
+<p> |
|
| 15 |
+Tor Hidden Services allow users to set up anonymous information services, |
|
| 16 |
+like websites, that can only be accessed through the Tor network and are |
|
| 17 |
+protected against identification of the host that runs the services. |
|
| 18 |
+The most critical limitation of Tor Hidden Services is the time it takes |
|
| 19 |
+until a Hidden Service is registered in the network and the latency of |
|
| 20 |
+contact establishment when accessed by a user. |
|
| 21 |
+Due to design issues in the original Tor protocol, |
|
| 22 |
+the connection to a new Hidden Service can take several minutes, which |
|
| 23 |
+leads most users to give up before the connection has been established. |
|
| 24 |
+Using Tor Hidden Services for direct interactive user-to-user |
|
| 25 |
+communication (e.g. messaging) is nearly impossible due to the high latency |
|
| 26 |
+of Hidden Service circuit setup. |
|
| 27 |
+</p> |
|
| 28 |
+ |
|
| 29 |
+<p> |
|
| 30 |
+This project aims at speeding up Tor Hidden Services by improving the way |
|
| 31 |
+Tor circuits are set up between the user and the Hidden Service as well as |
|
| 32 |
+the way a Hidden Service is registered in the Tor network. |
|
| 33 |
+In a first step precise diagnostics of the behavior of the Hidden Services |
|
| 34 |
+in lab setups and real world situations will be conducted to find the |
|
| 35 |
+root causes of the bad timing effects. |
|
| 36 |
+Based on these diagnostics, optimization strategies will be designed and |
|
| 37 |
+verified for unwanted implications for the security and anonymity of the |
|
| 38 |
+Tor network. |
|
| 39 |
+The most promising optimizations will then be implemented to achieve a |
|
| 40 |
+notable improvement for the users. Precise success metrics will be |
|
| 41 |
+developed in the diagnostics phase, after it becomes clear where the time |
|
| 42 |
+is lost and what improvements are realistic. |
|
| 43 |
+The ultimate goal is to have the Hidden Services protocol change production |
|
| 44 |
+ready and propagated to the Tor users within a timeframe of less than |
|
| 45 |
+12 months. |
|
| 46 |
+</p> |
|
| 47 |
+ |
|
| 48 |
+<p> |
|
| 49 |
+This project is generously funded by the |
|
| 50 |
+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html">NLnet foundation</a>. |
|
| 51 |
+</p> |
|
| 52 |
+ |
|
| 53 |
+<a id="Timetable"></a> |
|
| 54 |
+<h2><a class="anchor" href="#Timetable">Timetable</a></h2> |
|
| 55 |
+<table width="100%" border="0" cellspacing="0" cellpadding="3"> |
|
| 56 |
+<!-- <thead> |
|
| 57 |
+<tr bgcolor="#e5e5e5"> |
|
| 58 |
+<th>Deliverable</th> |
|
| 59 |
+<th>Due Date</th> |
|
| 60 |
+</tr> |
|
| 61 |
+</thead> --> |
|
| 62 |
+ |
|
| 63 |
+<tr bgcolor="#e5e5e5"> |
|
| 64 |
+ <td> |
|
| 65 |
+ <b>Deliverable A:</b> Analysis, measurements and problem |
|
| 66 |
+ clarification<br /> |
|
| 67 |
+ <small><em>As Tor Hidden Services have not been actively developed |
|
| 68 |
+ further in the last year or so of Tor development, certain aspects of |
|
| 69 |
+ the problems are under-diagnosed. To identify the precise sources of |
|
| 70 |
+ latency and time loss, an extensive analysis of the deeper reasons for |
|
| 71 |
+ them needs to be conducted. Deliverable A will require about one month |
|
| 72 |
+ of work. The results of the analysis will influence the design |
|
| 73 |
+ decisions to be taken in Deliverable B.</em></small> |
|
| 74 |
+ </td> |
|
| 75 |
+ <td> |
|
| 76 |
+ June 15, 2008 |
|
| 77 |
+ </td> |
|
| 78 |
+</tr> |
|
| 79 |
+ |
|
| 80 |
+<tr> |
|
| 81 |
+ <td> |
|
| 82 |
+ <b>Deliverable B:</b> Design and evaluation of the necessary |
|
| 83 |
+ changes<br /> |
|
| 84 |
+ <small><em>The changes to Tor Hidden Services will affect core |
|
| 85 |
+ functionality of the protocol and therefore require a careful |
|
| 86 |
+ evaluation of possible repercussions for the security and anonymity. A |
|
| 87 |
+ two-month period is planned for the design and evaluation phase, which |
|
| 88 |
+ concludes with an extensive peer review.</em></small> |
|
| 89 |
+ </td> |
|
| 90 |
+ <td> |
|
| 91 |
+ August 15, 2008 |
|
| 92 |
+ </td> |
|
| 93 |
+</tr> |
|
| 94 |
+ |
|
| 95 |
+<tr bgcolor="#e5e5e5"> |
|
| 96 |
+ <td> |
|
| 97 |
+ <b>Deliverable C:</b> Implementation<br /> |
|
| 98 |
+ <small><em>After design, evaluation and peer review the modifications |
|
| 99 |
+ need to be implemented and integrated with the current Tor code base. |
|
| 100 |
+ The actual implementation of the necessary changes will take |
|
| 101 |
+ approximately two months.</em></small> |
|
| 102 |
+ </td> |
|
| 103 |
+ <td> |
|
| 104 |
+ October 15, 2008 |
|
| 105 |
+ </td> |
|
| 106 |
+</tr> |
|
| 107 |
+ |
|
| 108 |
+<tr> |
|
| 109 |
+ <td> |
|
| 110 |
+ <b>Deliverable D:</b> Implementation and test of the change up to |
|
| 111 |
+ release state<br /> |
|
| 112 |
+ <small><em>The modification is highly critical to the security and |
|
| 113 |
+ anonymity of the Tor network, it requires extensive testing and |
|
| 114 |
+ debugging in laboratory and real life conditions. A period of three |
|
| 115 |
+ months is projected for testing and debugging, where the responsible |
|
| 116 |
+ developer is committed to the testing effort with 1/3 of its time. Part |
|
| 117 |
+ of the testing phase will be a public beta period.</em></small> |
|
| 118 |
+ </td> |
|
| 119 |
+ <td> |
|
| 120 |
+ January 15, 2009 |
|
| 121 |
+ </td> |
|
| 122 |
+</tr> |
|
| 123 |
+ |
|
| 124 |
+<tr bgcolor="#e5e5e5"> |
|
| 125 |
+ <td> |
|
| 126 |
+ <b>Deliverable E:</b> Rollout<br /> |
|
| 127 |
+ <small><em>The actual rollout to the Tor server network will be |
|
| 128 |
+ conducted in sync with the regular Tor release schedule. As this |
|
| 129 |
+ schedule is dependent on a number of external factors, like the |
|
| 130 |
+ completion of other software projects that should go into the same |
|
| 131 |
+ release, the actual release time and the time until this release has |
|
| 132 |
+ been accepted and installed by most Tor server operators can vary. From |
|
| 133 |
+ experience a period of three to four months can be |
|
| 134 |
+ expected.</em></small> |
|
| 135 |
+ </td> |
|
| 136 |
+ <td> |
|
| 137 |
+ May 15, 2009 |
|
| 138 |
+ </td> |
|
| 139 |
+</tr> |
|
| 140 |
+</table> |
|
| 141 |
+ |
|
| 142 |
+<br /> |
|
| 143 |
+ |
|
| 144 |
+<a id="Reports"></a> |
|
| 145 |
+<h2><a class="anchor" href="#Reports">Monthly Status Reports</a></h2> |
|
| 146 |
+<p> |
|
| 147 |
+There will be in total eight monthly status reports beginning with the |
|
| 148 |
+first deliverable on June 15, 2008 and ending with completion of |
|
| 149 |
+implementation and testing work on January 15, 2009. |
|
| 150 |
+</p> |
|
| 151 |
+ |
|
| 152 |
+<!-- Where do we put status reports? The idea here is to create separate pages. |
|
| 153 |
+<ul> |
|
| 154 |
+<li><a href="<page projects/hidserv-2008-06>">June 2008 monthly status |
|
| 155 |
+report</a></li> |
|
| 156 |
+</ul> |
|
| 157 |
+--> |
|
| 158 |
+ |
|
| 159 |
+<!-- Do we want a people section? If so, would it make sense to write what |
|
| 160 |
+these people will be doing? And---what exactly are these people going to |
|
| 161 |
+do? :) |
|
| 162 |
+<a id="People"></a> |
|
| 163 |
+<h2><a class="anchor" href="#People">People</a></h2> |
|
| 164 |
+<ul> |
|
| 165 |
+<li><a href="<page people>#Core">Karsten Loesing</a></li> |
|
| 166 |
+<li><a href="<page people>#Core">Steven Murdoch</a></li> |
|
| 167 |
+</ul> |
|
| 168 |
+--> |
|
| 169 |
+ |
|
| 170 |
+<a id="Links"></a> |
|
| 171 |
+<h2><a class="anchor" href="#Links">Links</a></h2> |
|
| 172 |
+<ul> |
|
| 173 |
+<li>Research paper on <b>Performance Measurements and Statistics of Tor |
|
| 174 |
+Hidden Services</b> |
|
| 175 |
+(<a href="http://www.uni-bamberg.de/fileadmin/uni/fakultaeten/wiai_lehrstuehle/praktische_informatik/Dateien/Publikationen/loesing2008performance.pdf">PDF</a>) |
|
| 176 |
+by Karsten Loesing, Werner Sandmann, Christian Wilms, and Guido Wirtz. In |
|
| 177 |
+the Proceedings of the 2008 International Symposium on Applications and the |
|
| 178 |
+Internet (SAINT), Turku, Finland, July 2008. |
|
| 179 |
+ |
|
| 180 |
+<!-- In the future, put links to proposal, preliminary results, etc. here --> |
|
| 181 |
+ |
|
| 182 |
+</ul> |
|
| 183 |
+ |
|
| 184 |
+</div><!-- #main --> |
|
| 185 |
+ |
|
| 186 |
+#include <foot.wmi> |
|
| 187 |
+ |
|
| 0 | 188 |