November 2012 - tor-commits - lists.torproject.org

[tor-design-2012/master] Add a {; make LaTeX finish
by nickm＠torproject.org 14 Nov '12

14 Nov '12

commit b4df8c08e433a75e57ee72a03409855fb5073250 Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Nov 14 15:06:27 2012 -0500 Add a {; make LaTeX finish --- tor-design-2012.tex | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/tor-design-2012.tex b/tor-design-2012.tex index 43cf08b..cb8c1b5 100644 --- a/tor-design-2012.tex +++ b/tor-design-2012.tex @@ -1504,7 +1504,7 @@ information into the fully qualified domain name (FQDN) Alice uses when establishing her connection. Location-hidden services use a virtual top level domain called {\tt .onion}: thus hostnames take the form {\tt y.onion} where -\tt y} encodes the hash of the public +{\tt y} encodes the hash of the public key. Alice's onion proxy examines addresses; if they're destined for a hidden server, it decodes the key and starts the rendezvous as described above.

1 0

[translation/vidalia_alpha_completed] Update translations for vidalia_alpha_completed
by translation＠torproject.org 14 Nov '12

14 Nov '12

commit b989422940f8d9de4487ca96d3f9857ae88bae92 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Nov 14 19:45:20 2012 +0000 Update translations for vidalia_alpha_completed --- es/vidalia_es.po | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git a/es/vidalia_es.po b/es/vidalia_es.po index 560cff0..6e9896b 100644 --- a/es/vidalia_es.po +++ b/es/vidalia_es.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2012-03-21 17:46+0000\n" -"PO-Revision-Date: 2012-11-14 19:13+0000\n" +"PO-Revision-Date: 2012-11-14 19:45+0000\n" "Last-Translator: strel <strelnic(a)gmail.com>\n" "Language-Team: Spanish (http://www.transifex.com/projects/p/torproject/language/es/)\n" "MIME-Version: 1.0\n" @@ -2781,7 +2781,7 @@ msgstr "Vidalia no pudo guardar las opciones del fichero torrc." msgctxt "RouterDescriptor" msgid "Online" -msgstr "En Línea" +msgstr "Conectado" msgctxt "RouterDescriptor" msgid "Hibernating" @@ -2789,7 +2789,7 @@ msgstr "Hibernando" msgctxt "RouterDescriptor" msgid "Offline" -msgstr "Fuera de Línea" +msgstr "Desconectado" msgctxt "RouterDescriptorView" msgid "Location:" @@ -2805,15 +2805,15 @@ msgstr "Plataforma:" msgctxt "RouterDescriptorView" msgid "Bandwidth:" -msgstr "Ancho de Banda:" +msgstr "Ancho de banda:" msgctxt "RouterDescriptorView" msgid "Uptime:" -msgstr "Tiempo de disponibilidad:" +msgstr "Tiempo conectado:" msgctxt "RouterDescriptorView" msgid "Last Updated:" -msgstr "Última Actualización:" +msgstr "Última actualización:" msgctxt "RouterDescriptorView" msgid "Copy" @@ -2825,11 +2825,11 @@ msgstr "Hibernando" msgctxt "RouterInfoDialog" msgid "Online" -msgstr "En Línea" +msgstr "Conectado" msgctxt "RouterInfoDialog" msgid "Offline" -msgstr "Fuera de Línea" +msgstr "Desconectado" msgctxt "RouterInfoDialog" msgid "Unknown" @@ -2849,7 +2849,7 @@ msgstr "Nombre:" msgctxt "RouterInfoDialog" msgid "Status:" -msgstr "Estado" +msgstr "Estado:" msgctxt "RouterInfoDialog" msgid "Location:"

1 0

[translation/vidalia_alpha] Update translations for vidalia_alpha
by translation＠torproject.org 14 Nov '12

14 Nov '12

commit 32742eed7435404ada8361c3780655e256cbc570 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Nov 14 19:45:17 2012 +0000 Update translations for vidalia_alpha --- es/vidalia_es.po | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git a/es/vidalia_es.po b/es/vidalia_es.po index 560cff0..6e9896b 100644 --- a/es/vidalia_es.po +++ b/es/vidalia_es.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2012-03-21 17:46+0000\n" -"PO-Revision-Date: 2012-11-14 19:13+0000\n" +"PO-Revision-Date: 2012-11-14 19:45+0000\n" "Last-Translator: strel <strelnic(a)gmail.com>\n" "Language-Team: Spanish (http://www.transifex.com/projects/p/torproject/language/es/)\n" "MIME-Version: 1.0\n" @@ -2781,7 +2781,7 @@ msgstr "Vidalia no pudo guardar las opciones del fichero torrc." msgctxt "RouterDescriptor" msgid "Online" -msgstr "En Línea" +msgstr "Conectado" msgctxt "RouterDescriptor" msgid "Hibernating" @@ -2789,7 +2789,7 @@ msgstr "Hibernando" msgctxt "RouterDescriptor" msgid "Offline" -msgstr "Fuera de Línea" +msgstr "Desconectado" msgctxt "RouterDescriptorView" msgid "Location:" @@ -2805,15 +2805,15 @@ msgstr "Plataforma:" msgctxt "RouterDescriptorView" msgid "Bandwidth:" -msgstr "Ancho de Banda:" +msgstr "Ancho de banda:" msgctxt "RouterDescriptorView" msgid "Uptime:" -msgstr "Tiempo de disponibilidad:" +msgstr "Tiempo conectado:" msgctxt "RouterDescriptorView" msgid "Last Updated:" -msgstr "Última Actualización:" +msgstr "Última actualización:" msgctxt "RouterDescriptorView" msgid "Copy" @@ -2825,11 +2825,11 @@ msgstr "Hibernando" msgctxt "RouterInfoDialog" msgid "Online" -msgstr "En Línea" +msgstr "Conectado" msgctxt "RouterInfoDialog" msgid "Offline" -msgstr "Fuera de Línea" +msgstr "Desconectado" msgctxt "RouterInfoDialog" msgid "Unknown" @@ -2849,7 +2849,7 @@ msgstr "Nombre:" msgctxt "RouterInfoDialog" msgid "Status:" -msgstr "Estado" +msgstr "Estado:" msgctxt "RouterInfoDialog" msgid "Location:"

1 0

[translation/vidalia_alpha_completed] Update translations for vidalia_alpha_completed
by translation＠torproject.org 14 Nov '12

14 Nov '12

commit f8406957c32d121934e587a79888d7325db273dc Author: Translation commit bot <translation(a)torproject.org> Date: Wed Nov 14 19:15:21 2012 +0000 Update translations for vidalia_alpha_completed --- es/vidalia_es.po | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git a/es/vidalia_es.po b/es/vidalia_es.po index d0aa191..560cff0 100644 --- a/es/vidalia_es.po +++ b/es/vidalia_es.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2012-03-21 17:46+0000\n" -"PO-Revision-Date: 2012-11-13 03:31+0000\n" +"PO-Revision-Date: 2012-11-14 19:13+0000\n" "Last-Translator: strel <strelnic(a)gmail.com>\n" "Language-Team: Spanish (http://www.transifex.com/projects/p/torproject/language/es/)\n" "MIME-Version: 1.0\n" @@ -2471,7 +2471,7 @@ msgstr "Ajustar zoom" msgctxt "NetViewer" msgid "Zooms to fit all currently displayed circuits" -msgstr "Ajusta el zoom para encuadrar todos los circuitos mostrados" +msgstr "Ajusta el zoom encuadrando todos los circuitos mostrados" msgctxt "NetViewer" msgid "Ctrl+Z" @@ -2495,7 +2495,7 @@ msgstr "Pantalla completa" msgctxt "NetViewer" msgid "View the network map as a full screen window" -msgstr "Ver el mapa de red como una ventana de pantalla completa" +msgstr "Muestra el mapa de red como una ventana de pantalla completa" msgctxt "NetViewer" msgid "Ctrl+F" @@ -2507,7 +2507,7 @@ msgstr "Mapa de Red" msgctxt "NetViewer" msgid "Relay" -msgstr "Repetidor (relay)" +msgstr "Repetidor" msgctxt "NetViewer" msgid "Connection" @@ -2569,7 +2569,7 @@ msgstr "Uso un proxy para acceder a internet" msgctxt "NetworkPage" msgid "Proxy Settings" -msgstr "Configuración de Proxy" +msgstr "Configuración para Proxy" msgctxt "NetworkPage" msgid "Username:" @@ -2593,11 +2593,11 @@ msgstr "Mi cortafuegos (firewall) sólo me permite conectarme a ciertos puertos" msgctxt "NetworkPage" msgid "Firewall Settings" -msgstr "Configuración en el Cortafuegos (firewall)" +msgstr "Configuración en el Cortafuegos" msgctxt "NetworkPage" msgid "Allowed Ports:" -msgstr "Puertos a usar permitidos en el cortafuegos:" +msgstr "Puertos a usar permitidos por el cortafuegos:" msgctxt "NetworkPage" msgid "80, 443" @@ -2607,7 +2607,7 @@ msgctxt "NetworkPage" msgid "" "Check to encrypt directory requests and, optionally, use bridge relays to " "access the Tor network" -msgstr "Marcar para cifrar peticiones de directorio y, opcionalmente, usar puentes repetidores (bridges) para acceder a la red Tor" +msgstr "Marcar para cifrar peticiones al directorio y, opcionalmente, usar repetidores puente (bridges) para acceder a la red Tor" msgctxt "NetworkPage" msgid "My ISP blocks connections to the Tor network" @@ -2645,7 +2645,7 @@ msgctxt "NetworkPage" msgid "" "No new bridges are currently available. You can either wait a while and try " "again, or try another method of finding new bridges." -msgstr "Actualmente no hay nuevos puentes disponibles. Puede esperar un rato e intentar de nuevo o probar con otro método para encontrar nuevos puentes." +msgstr "Actualmente no hay puentes nuevos disponibles. Puede esperar un rato e intentarlo de nuevo, o probar con otro método para encontrar nuevos puentes." msgctxt "NetworkPage" msgid "Click Help to see other methods of finding new bridges."

1 0

[translation/vidalia_alpha] Update translations for vidalia_alpha
by translation＠torproject.org 14 Nov '12

14 Nov '12

commit c2b2c75b034c8ee13d1ce972bc375275abaccdf6 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Nov 14 19:15:18 2012 +0000 Update translations for vidalia_alpha --- es/vidalia_es.po | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git a/es/vidalia_es.po b/es/vidalia_es.po index d0aa191..560cff0 100644 --- a/es/vidalia_es.po +++ b/es/vidalia_es.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2012-03-21 17:46+0000\n" -"PO-Revision-Date: 2012-11-13 03:31+0000\n" +"PO-Revision-Date: 2012-11-14 19:13+0000\n" "Last-Translator: strel <strelnic(a)gmail.com>\n" "Language-Team: Spanish (http://www.transifex.com/projects/p/torproject/language/es/)\n" "MIME-Version: 1.0\n" @@ -2471,7 +2471,7 @@ msgstr "Ajustar zoom" msgctxt "NetViewer" msgid "Zooms to fit all currently displayed circuits" -msgstr "Ajusta el zoom para encuadrar todos los circuitos mostrados" +msgstr "Ajusta el zoom encuadrando todos los circuitos mostrados" msgctxt "NetViewer" msgid "Ctrl+Z" @@ -2495,7 +2495,7 @@ msgstr "Pantalla completa" msgctxt "NetViewer" msgid "View the network map as a full screen window" -msgstr "Ver el mapa de red como una ventana de pantalla completa" +msgstr "Muestra el mapa de red como una ventana de pantalla completa" msgctxt "NetViewer" msgid "Ctrl+F" @@ -2507,7 +2507,7 @@ msgstr "Mapa de Red" msgctxt "NetViewer" msgid "Relay" -msgstr "Repetidor (relay)" +msgstr "Repetidor" msgctxt "NetViewer" msgid "Connection" @@ -2569,7 +2569,7 @@ msgstr "Uso un proxy para acceder a internet" msgctxt "NetworkPage" msgid "Proxy Settings" -msgstr "Configuración de Proxy" +msgstr "Configuración para Proxy" msgctxt "NetworkPage" msgid "Username:" @@ -2593,11 +2593,11 @@ msgstr "Mi cortafuegos (firewall) sólo me permite conectarme a ciertos puertos" msgctxt "NetworkPage" msgid "Firewall Settings" -msgstr "Configuración en el Cortafuegos (firewall)" +msgstr "Configuración en el Cortafuegos" msgctxt "NetworkPage" msgid "Allowed Ports:" -msgstr "Puertos a usar permitidos en el cortafuegos:" +msgstr "Puertos a usar permitidos por el cortafuegos:" msgctxt "NetworkPage" msgid "80, 443" @@ -2607,7 +2607,7 @@ msgctxt "NetworkPage" msgid "" "Check to encrypt directory requests and, optionally, use bridge relays to " "access the Tor network" -msgstr "Marcar para cifrar peticiones de directorio y, opcionalmente, usar puentes repetidores (bridges) para acceder a la red Tor" +msgstr "Marcar para cifrar peticiones al directorio y, opcionalmente, usar repetidores puente (bridges) para acceder a la red Tor" msgctxt "NetworkPage" msgid "My ISP blocks connections to the Tor network" @@ -2645,7 +2645,7 @@ msgctxt "NetworkPage" msgid "" "No new bridges are currently available. You can either wait a while and try " "again, or try another method of finding new bridges." -msgstr "Actualmente no hay nuevos puentes disponibles. Puede esperar un rato e intentar de nuevo o probar con otro método para encontrar nuevos puentes." +msgstr "Actualmente no hay puentes nuevos disponibles. Puede esperar un rato e intentarlo de nuevo, o probar con otro método para encontrar nuevos puentes." msgctxt "NetworkPage" msgid "Click Help to see other methods of finding new bridges."

1 0

[translation/vidalia_help] Update translations for vidalia_help
by translation＠torproject.org 14 Nov '12

14 Nov '12

commit c7345b99dfb974a1bdfcc53c1aa67ee4a43e6e83 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Nov 14 14:45:28 2012 +0000 Update translations for vidalia_help --- el/config.po | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/el/config.po b/el/config.po index e243681..4d853ec 100644 --- a/el/config.po +++ b/el/config.po @@ -7,7 +7,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2010-06-26 16:58+0200\n" -"PO-Revision-Date: 2012-11-12 20:55+0000\n" +"PO-Revision-Date: 2012-11-14 14:20+0000\n" "Last-Translator: anvo <fragos.george(a)hotmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" @@ -61,12 +61,12 @@ msgid "" "Startup Options: This setting allows you to have Vidalia " "automatically start Tor when Vidalia starts. You can also configure Vidalia " "to run when your system starts (Windows only)." -msgstr "" +msgstr "Επιλογές εκκίνησης: Οι ρυθμίσεις αυτές επιτρέπουν την αυτόματη εκκίνηση του Tor κάθε φορά που ξεκινά το Vidalia. Μπορείτε, επίσης, να ρυθμίσετε το Vidalia να εκτελείται μόλις εκκινεί το σύστημά σας (για Windows μόνον)." #. type: Content of: <html><body> #: en/config.html:46 msgid "<a name=\"network\"/>" -msgstr "" +msgstr "<a name=\"δίκτυο\"/>" #. type: Content of: <html><body><h3> #: en/config.html:47 @@ -78,7 +78,7 @@ msgstr "Ρυθμίσεις Δικτύου " msgid "" "The Network settings page lets you change how Tor connects to the Tor" " network." -msgstr "" +msgstr "Οι ρυθμίσεις Δικτύου σας επιτρέπουν να αλλάξετε τον τρόπο που το Tors συνδέεται στο δίκτυο Tor." #. type: Content of: <html><body><ul><li> #: en/config.html:53

1 0

r25888: {website} Dropping task priority and alphabetising It has always irked (website/trunk/getinvolved/en)
by Damian Johnson 14 Nov '12

14 Nov '12

Author: atagar Date: 2012-11-14 06:26:37 +0000 (Wed, 14 Nov 2012) New Revision: 25888 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Dropping task priority and alphabetising It has always irked me that we had a task 'priority'. Who decides these priorities? Against what? Sure I think that stem projects are the most important thing since the discovery of pepperjack cheese but does that really mean I should label my projects as 'ultra super omega-purple level important'? Dropping the priority from task ideas and sorting everything alphabetically. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2012-11-14 05:50:42 UTC (rev 25887) +++ website/trunk/getinvolved/en/volunteer.wml 2012-11-14 06:26:37 UTC (rev 25888) @@ -787,87 +787,203 @@ <ol> - <a id="improveTorbirdy"></a> +  + +  + +  + + <a id="compassRefactoring"></a> + <li> + Compass Refactoring + + Effort Level: Medium + + Skill Level: Medium + + Likely Mentors: gsathya, karsten - TorBirdy is under active development and is available from <a - href="https://trac.torproject.org/projects/tor/wiki/torbirdy">our wiki</a> - and <a - href="https://addons.mozilla.org/en-US/thunderbird/addon/torbirdy/">mozilla's - addons site</a>. + Compass was first designed to be a cli app and then hacked into a web app. + The codebase needs to be refactored such that the main processing code is + separated from the display functions(probably into separate files) and made + modular so that adding more features (<a + href="https://trac.torproject.org/6612">#6612</a>) is easy. For example, the + main processing logic could be in compass.py, whereas print_groups() and other + display related functions could be part of a separate cli.py; web.py would also + have to modified to make use of this new modular code. Bonus points for adding + features to compass(<a href="https://trac.torproject.org/6619">#6619</a>, <a + href="https://trac.torproject.org/6612">#6612</a>, <a + href="https://trac.torproject.org/6728">#6728</a>). + </li> +   @@ -876,8 +992,6 @@ <li> Develop a fully automatic firewall-probing system - Priority: High - Effort Level: Medium to High Skill Level: High @@ -904,202 +1018,274 @@ -->  -   - <a id="limitCapabilities"></a> +  - <a id="docUpdate"></a> +  - <a id="torCleanup"></a> + <a id="improveTorbirdy"></a> <li> - Tor Codebase Cleanup + Improving TorBirdy - Priority: Medium to High + Effort Level: High - Effort Level: Low to High, depending on subproject chosen - Skill Level: Medium to High - Likely Mentors: Nick (nickm) + Likely Mentors: Sukhbir, Jacob - The Tor code is almost 10 years old in places, and we haven't always had - enough time or wisdom to write things as well as we could have. Our unit - test coverage is shamefully low, and the dependency graph of our modules is - shamefully convoluted . We could use refactoring and unit tests! Please - look through the Tor source code and look for ugly or tricky code or - dependencies -- the uglier and trickier the better -- and think about how - you could make the code look better, read better, and (subject to testing) - work better. + TorBirdy is Torbutton for Thunderbird, Icedove and related Mozilla mail + clients. + + TorBirdy is under active development and is available from <a + href="https://trac.torproject.org/projects/tor/wiki/torbirdy">our wiki</a> + and <a + href="https://addons.mozilla.org/en-US/thunderbird/addon/torbirdy/">mozilla's + addons site</a>. + - If this is for a fun side-project, it would be great for you to work on - anything that can be made better and more tested. For an internship-level - position, we'd hope that you could find a number of particularly tricky or - knotty piece of the code to clean up, and aim for resolving the ugliest - problems, not necessarily the easiest. + The goal of this project is to improve TorBirdy by: + <ul> + <li> + Writing a Thunderbird patch to plug known leaks. We have already <a + href="https://bugzilla.mozilla.org/show_bug.cgi?id=776397">submitted a + patch to Thunderbird</a> but we anticipate there will be much more work + required before it is accepted, possibly involving rewriting the entire + patch; this appears trivial, but it is not, as we are proposing a + completely new privacy-safe message-ID header generation algorithm for + Thunderbird. + </li> + <li> + Implementing a JavaScript HTTP proxy (see the <a + href="https://trac.torproject.org/projects/tor/ticket/6958">ticket</a>) + </li> + <li> + Auditing TorBirdy for leaks and for use with other add-ons (as an + example see its <a + href="https://trac.torproject.org/projects/tor/ticket/6319">ticket</a>) + </li> + </ul> + - For a big project here, it would be great to pick one of the major - "submodules" of Tor -- path selection, node discovery, directory authority - operations, directory service -- and refactor its interface completely, to - minify and codify its points of contact with the rest of Tor. + A student undertaking this project should have some C++ and JavaScript + development experience. Previous experience with Firefox/Thunderbird + extension development is a plus, but not required. </li> - <a id="httpsImersonation"></a> +  <a id="chutneyExpansion"></a> <li> Make Chutney Do More, More Reliably - Priority: Medium - Effort Level: Medium to High, depending on scope of project Skill Level: Medium @@ -1119,91 +1305,254 @@ </li> - <a id="stemUsability"></a> +  +  + +  +  + + <a id="limitCapabilities"></a> + <li> + Run With Limited Capabilities + + Effort Level: Medium to High + + Skill Level: High + + Likely Mentors: Nick (nickm) - Stem is very nearly feature complete but presently has no users. We - want to change that prior to making our first release for a couple - reasons... + Many modern operating systems give a running program the ability to drop + capabilities that it no longer needs, and other ways for a program to run + pieces of itself in a sandbox with diminished privileges. - <ul> - <li>Make sure that we have a reasonably good API, and improve the rough - edges that hurt its usability.</li> - <li>Provide examples for how stem can be used.</li> - </ul> - - This project involves several tasks... + We'd like to do this with Tor, to improve its resistance to attacks. The + easiest areas to address would be on systems like <a + href="https://lwn.net/Articles/475361/">recent Linux kernels</a> that make + it easy to drop or restrict the set of syscalls that a program can invoke. + That's a great project, but probably not big enough for an internship just + on its own. For that, we'd want to make progress on at least multiple + platforms, or look into refactoring Tor into pieces that need more + privileges and pieces that don't with an eye towards sandboxing them + differently. - <ol> - <li>Move stem's site to Tor's website (<a href="https://trac.torproject.org/projects/tor/ticket/7324">ticket</a>)</li> - <li>Set up Piwik for our site (<a href="https://trac.torproject.org/projects/tor/ticket/7424">ticket</a>)</li> - <li>Come up with a better, more developer friendly "Module Overview" for our documentation (<a href="https://stem.readthedocs.org/en/latest/api/control.html">example page</a>). For instance, it would be nice to provide interlinking between the overview and the classes/methods that it lists. This will probably involve asking for help from the <a href="http://sphinx-doc.org/">Sphinx user list</a>.</li> - <li>Finally get your hands dirty using stem. We want to expand stem's <a href="https://stem.readthedocs.org/en/latest/tutorial.html">tutorial page</a> with more examples. To do this you'll want to both brainstorm some of your own and contact the <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev/">tor-dev@ email list</a> to solicit ideas. This last step is pretty open ended, so go nuts with whatever you think will improve stem's usability!</li> - </ol> + + See tickets <a href="https://trac.torproject.org/7005">#7005</a> and <a + href="https://trac.torproject.org/5219">#5219</a>, and their descendants, + for more information. + </li> - <a id="compassRefactoring"></a> + <a id="metricsSearch"></a> <li> - Compass Refactoring + Searchable Tor descriptor and Metrics data archive - Priority: Medium + Effort Level: Medium + Skill Level: Medium + + Likely Mentors: Karsten + The <a href="https://metrics.torproject.org/data.html">Metrics data + archive</a> of Tor relay descriptors and other Tor-related network data has + grown to over 100G in size, bz2-compressed. We have developed two search + interfaces: the <a + href="https://metrics.torproject.org/relay-search.html">relay search</a> + finds relays by nickname, fingerprint, or IP address in a given month; <a + href="https://metrics.torproject.org/exonerator.html">ExoneraTor</a> finds + whether a given IP address was a relay on a given day. + + We'd like to have a more general search application for Tor descriptors + and metrics data. There are more <a + href="https://metrics.torproject.org/formats.html">descriptor types</a> + that we'd like to include in the search. The search application should + handle most of them and understand some semantics like what's a timestamp, + what's an IP address, and what's a link to another descriptor. Users + should then be able to search for arbitrary strings or limit their search + to given time periods or IP address ranges. Descriptors that reference + other descriptors should contain links, and descriptors should be able to + say from where they are linked. The goal is to make the archive easily + browsable. + + The search application shall be separate from the metrics website and + shouldn't rely on the metrics website codebase. The search application + will contain hourly updated descriptor data from the metrics website via + rsync. Programming language and database system are not specified yet, + though there's a slight preference for Python/Django and Postgres for + maintenance reasons. If there are good reasons to pick something else, + e.g, some NoSQL variant or some search application framework, that's fine, + too. Further requirements are that lookups should be really fast and that + changes to the search application can be implemented in reasonable + time. + + Applications for this project should come with a design of the proposed + search application, ideally with a proof-of-concept based on a subset of + the available data to show that it will be able to handle the 100G+ of + data. + </li> + +   -  + Likely Mentors: Damian (atagar) + + <a href="https://stem.readthedocs.org/en/latest/index.html">Stem</a> is a + python controller library for tor. Like it's predecessor, <a + href="#project-torctl">TorCtl</a>, it uses tor's <a + href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control + protocol</a> to help developers program against the tor process, enabling + them to build things similar to <a href="#project-vidalia">Vidalia</a> and + <a href="#project-arm">arm</a>. + -  + + While TorCtl provided a fine first draft for this sort of functionality, + it has not proved to be extensible nor maintainable. Stem is a rewrite of + TorCtl with a heavy focus on testing, documentation, and providing a + developer friendly API. + -  + + Stem is very nearly feature complete but presently has no users. We + want to change that prior to making our first release for a couple + reasons... + -   -  - -  -  - - <a id="metricsSearch"></a> - <li> - Searchable Tor descriptor and Metrics data archive - - Priority: Medium - - Effort Level: Medium - - Skill Level: Medium - - Likely Mentors: Karsten - The <a href="https://metrics.torproject.org/data.html">Metrics data archive</a> of Tor relay descriptors and other Tor-related network data has grown to over 100G in size, bz2-compressed. We have developed two search interfaces: the <a href="https://metrics.torproject.org/relay-search.html">relay search</a> finds relays by nickname, fingerprint, or IP address in a given month; <a href="https://metrics.torproject.org/exonerator.html">ExoneraTor</a> finds whether a given IP address was a relay on a given day. - - We'd like to have a more general search application for Tor descriptors and metrics data. There are more <a href="https://metrics.torproject.org/formats.html">descriptor types</a> that we'd like to include in the search. The search application should handle most of them and understand some semantics like what's a timestamp, what's an IP address, and what's a link to another descriptor. Users should then be able to search for arbitrary strings or limit their search to given time periods or IP address ranges. Descriptors that reference other descriptors should contain links, and descriptors should be able to say from where they are linked. The goal is to make the archive easily browsable. - - The search application shall be separate from the metrics website and shouldn't rely on the metrics website codebase. The search application will contain hourly updated descriptor data from the metrics website via rsync. Programming language and database system are not specified yet, though there's a slight preference for Python/Django and Postgres for maintenance reasons. If there are good reasons to pick something else, e.g, some NoSQL variant or some search application framework, that's fine, too. Further requirements are that lookups should be really fast and that changes to the search application can be implemented in reasonable time. - - Applications for this project should come with a design of the proposed search application, ideally with a proof-of-concept based on a subset of the available data to show that it will be able to handle the 100G+ of data. - -  - -   - -  - -    - -   - -  -  <li> Bring up new ideas!

1 0

[tor-design-2012/master] Pass over the rest of the tor-design section. Demote an item to could-do-later
by nickm＠torproject.org 14 Nov '12

14 Nov '12

commit bf5fb7919a9806eef73ba1b859f163466789094a Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Nov 14 01:14:52 2012 -0500 Pass over the rest of the tor-design section. Demote an item to could-do-later --- todo | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/todo b/todo index aab4d6a..f69a1f8 100644 --- a/todo +++ b/todo @@ -36,14 +36,14 @@ ITEMS: o Abstract o Introduction - . Revise design goals and assumptions [steven] o Revise tor-design up to "opening and closing streams" [nick] - . Revise tor-design "opening and closing streams" onward [steven] + o Revise tor-design "opening and closing streams" onward [steven] o Revise hidden services section [nick] o Revise "other design decisions" [nick] CAN DO AFTER SPONSOR DEADLINE: + . Revise design goals and assumptions [steven] - Revise related work [steven] - Revise "attacks and defenses" [steven] - Replace "early experiences: Tor in the wild" [???? Nick? Can Roger?]

1 0

[tor-design-2012/master] Quick pass to revise the rest of the tor-design section
by nickm＠torproject.org 14 Nov '12

14 Nov '12

commit f77b7a6e255319c259daf0d060444d2909fd8d3e Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Nov 14 01:13:57 2012 -0500 Quick pass to revise the rest of the tor-design section --- tor-design-2012.tex | 57 +++++++++++++++++++++++++-------------------------- 1 files changed, 28 insertions(+), 29 deletions(-) diff --git a/tor-design-2012.tex b/tor-design-2012.tex index 38a6eed..43cf08b 100644 --- a/tor-design-2012.tex +++ b/tor-design-2012.tex @@ -1140,8 +1140,11 @@ reply to notify the application of its success. The OP now accepts data from the application's TCP stream, packaging it into \emph{relay data} cells and sending those cells along the circuit to the chosen OR. -% Mention the optimistic data extension: clients can send data before getting -% a relay_connected cell. -NM + +(As an optimization, to avoid a round-trip while waiting for a +connected reply, clients may send data immediately after the +connected cell. The need to be ready to send the same data to +another stream, though, if no connected cell arrives.) There's a catch to using SOCKS, however---some applications pass the alphanumeric hostname to the Tor client, while others @@ -1153,8 +1156,6 @@ resolved at the far end. Common applications like Firefox and SSH need to be configured to use SOCKS4A or SOCKS5 (with the option to send hostnames rather than IP address) to avoid this vulnerability. -% No longer true wrt mozilla and SSH. -NM -% Believed done -SJM With Firefox, the Torbutton add-on ensures that the browser sends requests via Tor by configuring Firefox to correctly use a @@ -1177,12 +1178,10 @@ Other applications, which can be configured to use SOCKS (and send the proxy a hostname rather than IP address), may be connected directly to Tor. Other options available are to intercept calls to the resolver and sockets libraries with -\emph{torsocks} or to use a firewall (Tor supports BSD and -Linux's in-built firewall) to intercept outgoing DNS requests +\emph{torsocks} or to use an operating system firewall's transparent +port-forwarding mechanism (Tor supports BSD and +Linux's in-built port-forwarding) to intercept outgoing DNS requests and TCP connections, sending them via Tor. -% We don't recommend privoxy any more. Proxies are one solution though. But -% for web, we think you need a custom browser. -NM -% Believed done -SJM Closing a Tor stream is analogous to closing a TCP stream: it uses a two-step handshake for normal operation, or a one-step @@ -1216,8 +1215,8 @@ modify data. Addressing the insider malleability attack, however, is more complex. We could do integrity checking of the relay cells at each hop, -either by including hashes or by using an authenticating cipher -mode like EAX~\cite{eax}, but there are some problems. First, +either by including MACs or by using an authenticating cipher +mode like GCM~\cite{gcm}, but there are some problems. First, these approaches impose a message-expansion overhead at each hop, and so we would have to either leak the path length or waste bytes by padding to a maximum path length. Second, these @@ -1228,10 +1227,6 @@ session keys. Third, we have already accepted that our design is vulnerable to end-to-end timing attacks; so tagging attacks performed within the circuit provide no additional information to the attacker. -% This "no additional information to the attacker" claim is less great than -% it might have seemed in 2004. We're looking towards wide-block approaches -% here instead. Also we should really not cite EAX and hashes but probably -% GCM and MACs as the likelier alternatives. -NM Thus, we check integrity only at the edges of each stream. (Remember that in our leaky-pipe circuit topology, a @@ -1244,8 +1239,6 @@ cells they create, and include with each relay cell the first four bytes of the current digest. Each also keeps a SHA-1 digest of data received, to verify that the received hashes are correct. -% Mention that sha-1 is showing its age, and we're moving away from it in our -% next relay protocol. -NM To be sure of removing or modifying a cell, the attacker must be able to deduce the current digest state (which depends on all @@ -1260,6 +1253,17 @@ overhead; the chance that an adversary will correctly guess a valid hash is acceptably low, given that the OP or OR tear down the circuit if they receive a bad hash. +This approach has, however, appeared less robust than we hoped; +while tagging attacks don't provide more information than an +end-to-end attacker could get through passive correlation attacks, +they succeed more quickly. Even that isn't such a big deal, were +it not for a class of attacks that become possible if an attacker +can detect non-corelatable circuits early and kill them (see +\ref{???XXXsomewhere-in-attacks-and-defenses}). We are therefore looking +into improved constructions for integrity, especially ones based +on wide-block ciphers. We hope to also take the opportunity to +move the authentication mechanism away from the moribund SHA-1. + \subsection{Rate limiting and fairness} \label{subsec:rate-limit} @@ -1348,9 +1352,10 @@ cell only when the number of bytes pending to be flushed is under some threshold (currently 10 cells' worth). % I don't believe that the numbers are 1000 and 100 any more. Must check -NM -These arbitrarily chosen parameters seem to give tolerable -throughput and delay; see Section~\ref{sec:in-the-wild}. -% The above paragraph has not held up over time -NM +These arbitrarily chosen parameters give tolerable but not great +throughput and delay; see Section~\ref{sec:in-the-wild}. See also +Section~\ref{????:how-to-really-ratelim} for discussion of future +work directions on the topic. \section{Rendezvous Points and hidden services} \label{sec:rendezvous} @@ -1405,9 +1410,6 @@ community finds objectionable, or if Bob's service tends to get attacked by network vandals). The extra level of indirection also allows Bob to respond to some requests and ignore others. -% Mention that the list of introduction points can now be encrypted. -NM -% Mention user authentication? -NM -% Believed done -SJM \subsection{Rendezvous points in Tor} @@ -1481,7 +1483,7 @@ points available. Bob could also give secret public keys for consulting the lookup service. All of these approaches limit exposure even when some selected users collude in the DoS\@. -% Thiss whole section is dated in ways I don't know off the top of my head. +% Thiss whole section may be dated in ways I don't know off the top of my head. % Gotta review the protocol revisions over the years. -NM @@ -1501,15 +1503,12 @@ remains a SOCKS proxy. We encode all of the necessary information into the fully qualified domain name (FQDN) Alice uses when establishing her connection. Location-hidden services use a virtual top level domain called {\tt .onion}: thus -hostnames take the form {\tt x.y.onion} where {\tt x} is the -authorization cookie and {\tt y} encodes the hash of the public +hostnames take the form {\tt y.onion} where +\tt y} encodes the hash of the public key. Alice's onion proxy examines addresses; if they're destined for a hidden server, it decodes the key and starts the rendezvous as described above. -% Authorization cookies never got built, right? it turns out that -% ``x.y.onion'' as a format for conveying them is a bad idea, due to the -% referer headers and stuff like that -NM \subsection{Previous rendezvous work}

1 0

[tor-design-2012/master] add a bit more about the control protocol
by nickm＠torproject.org 14 Nov '12

14 Nov '12

commit d69a468a07322588d60820c3e5752be05d97cdbc Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Nov 14 01:04:09 2012 -0500 add a bit more about the control protocol --- todo | 4 ++-- tor-design-2012.tex | 31 +++++++++++++++++++++++++++++++ 2 files changed, 33 insertions(+), 2 deletions(-) diff --git a/todo b/todo index da35f25..aab4d6a 100644 --- a/todo +++ b/todo @@ -25,10 +25,10 @@ ITEMS: o Bandwidth authorities o Path selection rules o stream isolation - . Integrate content from the third blog post [steven] + o Integrate content from the third blog post [steven] o link protocol tls X rise and fall of .exit - . controller protocol + o controller protocol o torbutton o tor browser bundle diff --git a/tor-design-2012.tex b/tor-design-2012.tex index 69c04a6..38a6eed 100644 --- a/tor-design-2012.tex +++ b/tor-design-2012.tex @@ -1826,6 +1826,37 @@ caches,'' and periodically fetch network consensus documents; clients can contact a cache instead, once they know who the caches are. +\subsection{The Tor controller protocol} + +Tor has always had a minimalist user interface---it can be +configured on the command line or a configuration file and sends +output to a log file. This was fine for advanced users, but most +users will prefer a GUI. Building a GUI into Tor would be +difficult, and would force certain choices (e.g. GUI toolkit) to +be made which might not suit all users and all +platforms. Therefore Tor includes an interface for other programs to +communicate with the Tor daemon, extracting information to display +on the GUI and changing the Tor configuration based on user +actions. This interface is an ASCII-based protocol, implemented +over a local socket, to allow another program to control Tor. + +The control protocol has also proven useful to researchers +experimenting with Tor. Initially the functionality exposed in the +control protocol was simply that exposed by the configuration file +and log files. Providing status information in a specified and +machine-readable format made the task of monitoring and +controlling Tor easier. Later, functionality was added to the +control protocol which should not be exposed to ordinary Tor users +but is useful to researchers, such as allowing controllers to +arbitrarily control the path selection process. + +To prevent arbitrary local processes from changing Tor's +configuration to make it less secure, the control protocol +provides authentication mechanisms so that only authorized local +processes (ones that can read an appropriate file on the +filesystem, or that know an appropriate passord) can connect to +the controller port. + \section{Attacks and Defenses} \label{sec:attacks}

1 0