- tor-commits - lists.torproject.org

[translation/vidalia_help_completed] Update translations for vidalia_help_completed
by translation＠torproject.org 06 Dec '12

06 Dec '12

commit 82a4f81d7cfaa7ec9f4dad31e6241f3e2dba1827 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Dec 6 11:45:39 2012 +0000 Update translations for vidalia_help_completed --- lv/log.po | 160 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 160 insertions(+), 0 deletions(-) diff --git a/lv/log.po b/lv/log.po new file mode 100644 index 0000000..7b6e55b --- /dev/null +++ b/lv/log.po @@ -0,0 +1,160 @@ +# +# Translators: +# Ojars Balcers <ojars.balcers(a)gmail.com>, 2012. +msgid "" +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 17:00+0200\n" +"PO-Revision-Date: 2012-12-06 11:40+0000\n" +"Last-Translator: Ojars Balcers <ojars.balcers(a)gmail.com>\n" +"Language-Team: LANGUAGE <LL(a)li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: lv\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2);\n" + +#. type: Content of: <html><body><h1> +#: en/log.html:16 +msgid "Message Log" +msgstr "Ziņojumu žurnāls" + +#. type: Content of: <html><body> +#: en/log.html:19 +msgid "" +"The message log lets you see status information about a running Tor process." +" <a name=\"basic\"/> Each message has a severity associated with it," +" ranging from Error (most serious) to Debug (most verbose). " +"See the help section on <a href=\"#severities\">message severities</a> for " +"more information. <a name=\"severities\"/>" +msgstr "Ziņojumu žurnāls rāda Tor procesa izpildes statusa informāciju. <a name=\"pamata\"/> Katrs ziņojumam piešķirts tam atbilstīgais nozīmīgums, diapazonā no Kļūda (visnopietnākais) līdz Atkļūdot (visizvērstākais). Lūdzu skatiet kļūdu nodaļu par <a href=\"#severities\">ziņojumu nozīmīgums</a> , lai uzzinātu vairāk. <a name=\"nozīmīgums\"/>" + +#. type: Content of: <html><body><h3> +#: en/log.html:28 +msgid "Message Severities" +msgstr "Ziņojumu nozīmīgums" + +#. type: Content of: <html><body> +#: en/log.html:30 +msgid "" +"A message's severity tells you how important the message is. A higher " +"severity message usually indicates that something has gone wrong with Tor. " +"Lower severity messages appear frequently during normal Tor operations and " +"usually do not need to be logged." +msgstr "Ziņojumu nopietnība vēsta par to cik nozīmīgs ir ziņojums. Lielākas nopietnības ziņojums vēsta, ka pastāv ar Tor saistīta problēmsituācija. Mazākas nopietnības ziņojumi bieži tiek rādīti arī normālas Tor'a darbības laikā. Parasti tos nav nepieciešams reģistrēt." + +#. type: Content of: <html><body> +#: en/log.html:37 +msgid "" +"The possible message severities, from most severe to least severe, are:" +msgstr "Iespējamais ziņojumu nozīmīgums, secībā no svarīgākā uz mazāk svarīgo, ir: " + +#. type: Content of: <html><body><ul><li> +#: en/log.html:41 +msgid "" +"Error: Messages that appear when something has gone very wrong and " +"Tor cannot proceed. These messages will be highlighted in red in the " +"message log." +msgstr "Kļūda: Ziņojumi, kuri parādās, kad kaut kas ir nogājis tiešām greizi un Tor nevar turpināt darbu. Ziņojumu žurnālā šādi ziņojumi tiks izcelti ar sarkans." + +#. type: Content of: <html><body><ul><li> +#: en/log.html:46 +msgid "" +"Warning: Messages that only appear when something has gone wrong with" +" Tor, but are not fatal and Tor will continue running. These messages will " +"be highlighted in yellow." +msgstr "Brīdinājums: Ziņojumi, kuri parādās vienīgi kad Tor notikusi darbības kļūda, bet tas nav kritiski un Tor turpinās izpildi. Šādi ziņojumi tiks izcelti ar dzeltens." + +#. type: Content of: <html><body><ul><li> +#: en/log.html:51 +msgid "" +"Notice: Messages that appear infrequently during normal Tor operation" +" and are not considered errors, but you still may care about." +msgstr "Norāde: Ziņojumi, kuri normālas Tor'a darbības laikā parādās salīdzinoši reti, un netiek uzskatīti par kļūdu ziņojumiem. Tomēr tiem var pievērst uzmanību." + +#. type: Content of: <html><body><ul><li> +#: en/log.html:55 +msgid "" +"Info: Messages that appear frequently during normal Tor operation and" +" are not usually of interest to most users." +msgstr "Informācija: Ziņojumi, kuri parādās Tor normālas darbības laikā, un vairumam lietotāju parasti neinteresē." + +#. type: Content of: <html><body><ul><li> +#: en/log.html:59 +msgid "" +"Debug: Extremely verbose messages that are primarily of interest to " +"developers. You should generally not log debug messages unless you know what" +" you are doing." +msgstr "Atkļūdošana: Ļoti izvērsti ziņojumi, kuri pārsvarā informē izstrādātājus. Vispārīgā gadījumā nav nepieciešams reģistrēt atkļūdošanas ziņojumus, izņemot, ja zināt kāpēc tas tā ir jādara." + +#. type: Content of: <html><body> +#: en/log.html:66 +msgid "" +"Most users should only log Error, Warning, and Notice " +"messages." +msgstr "Vairumam lietotāju vajadzētu reģistrēt vienīgi ziņojumus, kuri pieder klasēm Kļūda, Brīdinājums un Norāde." + +#. type: Content of: <html><body> +#: en/log.html:71 +msgid "" +"To select which message severities you would like to see, do the following:" +msgstr "Lai atzīmētu ziņojumu nozīmīgumu, kurus vēlaties redzēt, dariet sekojošo:" + +#. type: Content of: <html><body><ol><li> +#: en/log.html:73 en/log.html:92 +msgid "Open the message log from the Vidalia tray menu." +msgstr "Atvērt ziņojumu žurnālu Vidalia paliktņa izvēlnē." + +#. type: Content of: <html><body><ol><li> +#: en/log.html:74 en/log.html:93 +msgid "Click on Settings at the top of the message log window." +msgstr "Noklikšķināt uz Iestatījumi ziņojumu žurnāla loga augšpusē." + +#. type: Content of: <html><body><ol><li> +#: en/log.html:76 +msgid "" +"Check message severities you would like to see from the Message Filter group" +" on the left and uncheck message severities you would like to hide." +msgstr "Kreisajā pusē Ziņojumu filtra grupā atzīmējiet to ziņojumu nopietnības līmeni, kurus vēlaties redzēt, un noņemiet atzīmi tiem ziņojumu nopietnības līmeņiem, kurus vēlaties paslēpt." + +#. type: Content of: <html><body><ol><li> +#: en/log.html:79 +msgid "Click Save Settings to apply your new message filter." +msgstr "Noklikšķināt Saglabāt iestatījumus , lai lietotu jauno ziņojumu filtru." + +#. type: Content of: <html><body> +#: en/log.html:84 +msgid "<a name=\"logfile\"/>" +msgstr "<a name=\"žurnāldatne\"/>" + +#. type: Content of: <html><body><h3> +#: en/log.html:85 +msgid "Logging to a File" +msgstr "Reģistrēšana datnē" + +#. type: Content of: <html><body> +#: en/log.html:87 +msgid "" +"Vidalia can also write log messages to a file, as well as logging them in " +"the message log window. To enable logging to a file, follow these steps:" +msgstr "Vidalia var gan rakstīt žurnāla ziņojumus datnē, gan reģistrēt tos ziņojumu žurnāla logā. Lai iespējotu reģistrēšanu datnē, veiciet sekojošas darbības:" + +#. type: Content of: <html><body><ol><li> +#: en/log.html:94 +msgid "" +"Check the box labeled Automatically save new log messages to a file." +msgstr "Atzīmēt rūtiņu Jaunus žurnāla ziņojumus automātiski saglabāt datnē." + +#. type: Content of: <html><body><ol><li> +#: en/log.html:96 +msgid "" +"If you would like to change the file to which messages will be written, " +"either type the path and filename into the text box, or click Browse " +"to navigate to a location for your log file." +msgstr "Ja vēlaties mainīt datni, kurā ziņojumi tiks rakstīti, vai nu ierakstiet teksta lodziņā datnes nosaukumu un ceļu uz to, vai arī noklikšķiniet Pārlūkot , lai pārvietotos uz žurnāla datnes atrašanās vietu." + +#. type: Content of: <html><body><ol><li> +#: en/log.html:100 +msgid "Click Save Settings to save your log destination." +msgstr "Noklikšķiniet Saglabāt iestatījumus , lai saglabātu sava žurnāla mērķi."

1 0

[translation/vidalia_help] Update translations for vidalia_help
by translation＠torproject.org 06 Dec '12

06 Dec '12

commit d8f92eb1709db8f627ab4c3d3400c4fafbf4a497 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Dec 6 11:45:29 2012 +0000 Update translations for vidalia_help --- lv/log.po | 14 +++++++------- lv/netview.po | 23 +++++++++++------------ 2 files changed, 18 insertions(+), 19 deletions(-) diff --git a/lv/log.po b/lv/log.po index 843cf4e..7b6e55b 100644 --- a/lv/log.po +++ b/lv/log.po @@ -6,7 +6,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 17:00+0200\n" -"PO-Revision-Date: 2012-12-04 18:34+0000\n" +"PO-Revision-Date: 2012-12-06 11:40+0000\n" "Last-Translator: Ojars Balcers <ojars.balcers(a)gmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" @@ -42,7 +42,7 @@ msgid "" "severity message usually indicates that something has gone wrong with Tor. " "Lower severity messages appear frequently during normal Tor operations and " "usually do not need to be logged." -msgstr "" +msgstr "Ziņojumu nopietnība vēsta par to cik nozīmīgs ir ziņojums. Lielākas nopietnības ziņojums vēsta, ka pastāv ar Tor saistīta problēmsituācija. Mazākas nopietnības ziņojumi bieži tiek rādīti arī normālas Tor'a darbības laikā. Parasti tos nav nepieciešams reģistrēt." #. type: Content of: <html><body> #: en/log.html:37 @@ -71,7 +71,7 @@ msgstr "Brīdinājums: Ziņojumi, kuri parādās vienīgi kad Tor notikus msgid "" "Notice: Messages that appear infrequently during normal Tor operation" " and are not considered errors, but you still may care about." -msgstr "" +msgstr "Norāde: Ziņojumi, kuri normālas Tor'a darbības laikā parādās salīdzinoši reti, un netiek uzskatīti par kļūdu ziņojumiem. Tomēr tiem var pievērst uzmanību." #. type: Content of: <html><body><ul><li> #: en/log.html:55 @@ -86,7 +86,7 @@ msgid "" "Debug: Extremely verbose messages that are primarily of interest to " "developers. You should generally not log debug messages unless you know what" " you are doing." -msgstr "" +msgstr "Atkļūdošana: Ļoti izvērsti ziņojumi, kuri pārsvarā informē izstrādātājus. Vispārīgā gadījumā nav nepieciešams reģistrēt atkļūdošanas ziņojumus, izņemot, ja zināt kāpēc tas tā ir jādara." #. type: Content of: <html><body> #: en/log.html:66 @@ -116,7 +116,7 @@ msgstr "Noklikšķināt uz Iestatījumi ziņojumu žurnāla loga augšpus msgid "" "Check message severities you would like to see from the Message Filter group" " on the left and uncheck message severities you would like to hide." -msgstr "" +msgstr "Kreisajā pusē Ziņojumu filtra grupā atzīmējiet to ziņojumu nopietnības līmeni, kurus vēlaties redzēt, un noņemiet atzīmi tiem ziņojumu nopietnības līmeņiem, kurus vēlaties paslēpt." #. type: Content of: <html><body><ol><li> #: en/log.html:79 @@ -138,7 +138,7 @@ msgstr "Reģistrēšana datnē" msgid "" "Vidalia can also write log messages to a file, as well as logging them in " "the message log window. To enable logging to a file, follow these steps:" -msgstr "" +msgstr "Vidalia var gan rakstīt žurnāla ziņojumus datnē, gan reģistrēt tos ziņojumu žurnāla logā. Lai iespējotu reģistrēšanu datnē, veiciet sekojošas darbības:" #. type: Content of: <html><body><ol><li> #: en/log.html:94 @@ -152,7 +152,7 @@ msgid "" "If you would like to change the file to which messages will be written, " "either type the path and filename into the text box, or click Browse " "to navigate to a location for your log file." -msgstr "" +msgstr "Ja vēlaties mainīt datni, kurā ziņojumi tiks rakstīti, vai nu ierakstiet teksta lodziņā datnes nosaukumu un ceļu uz to, vai arī noklikšķiniet Pārlūkot , lai pārvietotos uz žurnāla datnes atrašanās vietu." #. type: Content of: <html><body><ol><li> #: en/log.html:100 diff --git a/lv/netview.po b/lv/netview.po index 28e0dd9..ce2c0dd 100644 --- a/lv/netview.po +++ b/lv/netview.po @@ -1,23 +1,24 @@ # # Translators: +# Ojars Balcers <ojars.balcers(a)gmail.com>, 2012. msgid "" 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 17:00+0200\n" -"PO-Revision-Date: 2010-11-30 05:03+0000\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"PO-Revision-Date: 2012-12-06 11:45+0000\n" +"Last-Translator: Ojars Balcers <ojars.balcers(a)gmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: lv\n" -"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2)\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2);\n" #. type: Content of: <html><body><h1> #: en/netview.html:16 msgid "Network Viewer" -msgstr "" +msgstr "Tīkla skatītājs" #. type: Content of: <html><body> #: en/netview.html:20 @@ -29,12 +30,12 @@ msgstr "" #. type: Content of: <html><body> #: en/netview.html:25 msgid "<a name=\"overview\"/>" -msgstr "" +msgstr "<a name=\"apskats\"/>" #. type: Content of: <html><body><h3> #: en/netview.html:26 msgid "Overview" -msgstr "" +msgstr "Apskats" #. type: Content of: <html><body> #: en/netview.html:28 @@ -49,12 +50,12 @@ msgstr "" #. type: Content of: <html><body> #: en/netview.html:35 msgid "<a name=\"netmap\"/>" -msgstr "" +msgstr "<a name=\"tīkla karte\"/>" #. type: Content of: <html><body><h3> #: en/netview.html:36 msgid "Network Map" -msgstr "" +msgstr "Tīkla karte" #. type: Content of: <html><body> #: en/netview.html:38 @@ -98,12 +99,12 @@ msgstr "" #. type: Content of: <html><body> #: en/netview.html:66 msgid "<a name=\"relaylist\"/>" -msgstr "" +msgstr "<a name=\"retranslatoru saraksts\"/>" #. type: Content of: <html><body><h3> #: en/netview.html:67 msgid "Relay Status" -msgstr "" +msgstr "Retranslatora statuss" #. type: Content of: <html><body> #: en/netview.html:69 @@ -245,5 +246,3 @@ msgstr "" #: en/netview.html:168 msgid "Date this relay's information was last updated." msgstr "" - -

1 0

[onionoo/master] Handle non-positive offsets and limits.
by karsten＠torproject.org 06 Dec '12

06 Dec '12

commit b4b90b045c1ef257d08951954bb44ec59aec909f Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Thu Dec 6 09:09:55 2012 +0100 Handle non-positive offsets and limits. Non-positive offsets were previously ignored, which is still the case. However, non-positive limits were ignored, too, which seems wrong. If a client wants even less than none documents, we shouldn't respond with all documents we have. Instead, we should return an empty response. --- src/org/torproject/onionoo/ResourceServlet.java | 12 ++++-------- web/index.html | 4 ++++ 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/org/torproject/onionoo/ResourceServlet.java b/src/org/torproject/onionoo/ResourceServlet.java index bc075b0..0fa9174 100644 --- a/src/org/torproject/onionoo/ResourceServlet.java +++ b/src/org/torproject/onionoo/ResourceServlet.java @@ -330,16 +330,12 @@ public class ResourceServlet extends HttpServlet { response.sendError(HttpServletResponse.SC_BAD_REQUEST); return; } - if (limit >= 0) { - while (limit < orderedRelays.size()) { - orderedRelays.remove(orderedRelays.size() - 1); - } + while (!orderedRelays.isEmpty() && limit < orderedRelays.size()) { + orderedRelays.remove(orderedRelays.size() - 1); } limit -= orderedRelays.size(); - if (limit >= 0) { - while (limit < orderedBridges.size()) { - orderedBridges.remove(orderedBridges.size() - 1); - } + while (!orderedBridges.isEmpty() && limit < orderedBridges.size()) { + orderedBridges.remove(orderedBridges.size() - 1); } } diff --git a/web/index.html b/web/index.html index e29c0b8..ca87016 100755 --- a/web/index.html +++ b/web/index.html @@ -684,10 +684,14 @@ undefined. <tr><td>offset</td><td>Skip the given number of relays and/or bridges. Relays are skipped first, then bridges. +Non-positive offset values are treated as zero and don't change the +result. </td></tr> <tr><td>limit</td><td>Limit result to the given number of relays and/or bridges. Relays are kept first, then bridges. +Non-positive limit values are treated as zero and lead to an empty +result. When used together with offset, the offsetting step precedes the limiting step. </td></tr>

1 0

[torspec/master] Adjust Krawczyk's construction to be RFC5869.
by nickm＠torproject.org 06 Dec '12

06 Dec '12

commit 35d872981166ef4b1fca2fe9766de530346e2873 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Dec 3 10:30:05 2012 -0500 Adjust Krawczyk's construction to be RFC5869. --- proposals/216-ntor-handshake.txt | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/proposals/216-ntor-handshake.txt b/proposals/216-ntor-handshake.txt index c6c6579..2ee9b14 100644 --- a/proposals/216-ntor-handshake.txt +++ b/proposals/216-ntor-handshake.txt @@ -103,13 +103,13 @@ Key expansion: where K0==g^xy, and K is divvied up into Df, Db, Kf, and Kb portions. - Instead, let's have it be + Instead, let's have it be HKDF-SHA256 as defined in RFC5869: - K = K_0 | K_1 | K_2 | K_3 | ... + K = K_1 | K_2 | K_3 | ... - Where K_0 = H(m_expand | INT8(i) , KEY_SEED ) + Where K_1 = H(m_expand | INT8(1) , KEY_SEED ) and K_(i+1) = H(K_i | m_expand | INT8(i) , KEY_SEED ) - and m_expend is an arbitrarily chosen value, + and m_expand is an arbitrarily chosen value, and INT8(i) is a octet with the value "i". Ian says this is due to a construction from Krawczyk at @@ -117,6 +117,9 @@ Key expansion: Let m_expand be PROTOID | ":key_expand" + In RFC5869's vocabulary, this is HKDF-SHA256 with info == m_expand, + salt == t_key, and IKM == secret_input. + Performance notes: In Tor's current circuit creation handshake, the client does:

1 0

[torspec/master] Tweaks/additions to ntor proposal:
by nickm＠torproject.org 06 Dec '12

06 Dec '12

commit 630b334bb0727653f561b477e3cd1ce8a7905c04 Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Dec 6 02:03:10 2012 -0500 Tweaks/additions to ntor proposal: * Specify node IDs as ID_LENGTH bytes long. * Make t_key not be a prefix of m_expand. Cosmetic but why not. * Rename the directory identifier for the keys. * Specify where they go in the microdescriptor * Change the handshake type to 0x0002, so that 0x0001 can be reserved for CREATE_FAST. * Explain how to stuff these in EXTEND/EXTENDED/CREATE/CREATE2 cells, so clients can use ntor even when the previous node doesn't grok EXTEND2. * Add test vectors which I hope are right for HKDF-SHA256. --- proposals/216-ntor-handshake.txt | 52 ++++++++++++++++++++++++++++++++++--- 1 files changed, 47 insertions(+), 5 deletions(-) diff --git a/proposals/216-ntor-handshake.txt b/proposals/216-ntor-handshake.txt index 2ee9b14..cb36ea1 100644 --- a/proposals/216-ntor-handshake.txt +++ b/proposals/216-ntor-handshake.txt @@ -36,6 +36,8 @@ Notation: Let KEYID be a collision-resistant (but not necessarily preimage-resistant) hash function on members of G, of output length H_LENGTH bytes. + Let each node have a unique identifier, ID_LENGTH bytes in length. + Instantiation: Let's call this PROTOID "ntor-curve25519-sha256-1" (We might want to make @@ -43,7 +45,7 @@ Instantiation: Set H(x,t) == HMAC_SHA256 with message x and key t. So H_LENGTH == 32. Set t_mac == PROTOID | ":mac" - t_key == PROTOID | ":key" + t_key == PROTOID | ":key_extract" t_verify == PROTOID | ":verify" Set EXP(a,b) == curve25519(.,b,a), and g == 9 . Let KEYGEN() do the @@ -64,7 +66,7 @@ Protocol: To send a create cell, the client generates a keypair x,X = KEYGEN(), and sends a CREATE cell with contents: - NODEID: ID -- H_LENGTH bytes + NODEID: ID -- ID_LENGTH bytes KEYID: KEYID(B) -- H_LENGTH bytes CLIENT_PK: X -- G_LENGTH bytes @@ -148,20 +150,60 @@ Integrating with the rest of Tor: Add a new optional entry to router descriptors and microdescriptors: - "onion-key-ntor" SP Base64Key NL + "ntor-onion-key" SP Base64Key NL where Base64Key is a base-64 encoded 32-byte value, with padding omitted. - Add a new consensus method to tell servers to copy "onion-key-ntor" + Add a new consensus method to tell servers to copy "ntor-onion-key" entries to from router descriptors to microdescriptors. + In microdescriptors, "ntor-onion-key" can go right after the "onion-key" + line. + Add a "UseNTorHandshake" configuration option and a corresponding consensus parameter to control whether clients use the ntor handshake. If the configuration option is "auto", clients should obey the consensus parameter. Have the configuration default be "auto" and the consensus value initially be "0". - Reserve the handshake type [00 01] for this handshake in CREATE2 and + Reserve the handshake type [00 02] for this handshake in CREATE2 and EXTEND2 cells. + Specify that this handshake type can be used in EXTEND/EXTENDED/ + CREATE/CREATED cells as follows: instead of a 190-byte TAP onionskin, send + the 16-byte string "ntorNTORntorNTOR", followed by the client's ntor + message. Instead of a 148-byte TAP response, send the server's ntor + response. (We need this so that a client can extend from an 0.2.3 server, + which doesn't know about CREATE2/CREATED2/EXTEND/EXTENDED2.) + +Test vectors for HKDF-SHA256: + + These are some test vectors for HKDF-SHA256 using the values for M_EXPAND + and T_KEY above, taking 100 bytes of key material. + + INPUT: "" (The empty string) + OUTPUT: d3490ed48b12a48f9547861583573fe3f19aafe3 + f81dc7fc75eeed96d741b3290f941576c1f9f0b2 + d463d1ec7ab2c6bf71cdd7f826c6298c00dbfe67 + 11635d7005f0269493edf6046cc7e7dcf6abe0d2 + 0c77cf363e8ffe358927817a3d3e73712cee28d8 + + INPUT: "Tor" (546f72) + OUTPUT: 5521492a85139a8d9107a2d5c0d9c91610d0f959 + 89975ebee6c02a4f8d622a6cfdf9b7c7edd3832e + 2760ded1eac309b76f8d66c4a3c4d6225429b3a0 + 16e3c3d45911152fc87bc2de9630c3961be9fdb9 + f93197ea8e5977180801926d3321fa21513e59ac + + INPUT: "AN ALARMING ITEM TO FIND ON YOUR CREDIT-RATING STATEMENT" + (414e20414c41524d494e47204954454d20544f2046494e44204f4e20 + 594f5552204352454449542d524154494e472053544154454d454e54) + OUTPUT: a2aa9b50da7e481d30463adb8f233ff06e9571a0 + ca6ab6df0fb206fa34e5bc78d063fc291501beec + 53b36e5a0e434561200c5f8bd13e0f88b3459600 + b4dc21d69363e2895321c06184879d94b18f0784 + 11be70b767c7fc40679a9440a0c95ea83a23efbf + + +

1 0

[flashproxy/master] Add -D option to websockify command.
by dcf＠torproject.org 06 Dec '12

06 Dec '12

commit 93649eeed9e88142b7b6a01fc06f4fde12039953 Author: David Fifield <david(a)bamsoftware.com> Date: Wed Dec 5 21:24:23 2012 -0800 Add -D option to websockify command. This causes it to background itself. --- init.d/websockify | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/init.d/websockify b/init.d/websockify index 22a5450..b43f2ea 100755 --- a/init.d/websockify +++ b/init.d/websockify @@ -29,7 +29,7 @@ case "$1" in start) [ -x $WEBSOCKIFY ] || exit 1 echo -n $"Starting websockify server: " - cd $VARDIR && daemon --user "$USER" --pidfile $PIDFILE "$WEBSOCKIFY" :"$WEBSOCKIFY_PORT" "$LOCAL_ADDRESS" + cd $VARDIR && daemon --user "$USER" --pidfile $PIDFILE "$WEBSOCKIFY" -D :"$WEBSOCKIFY_PORT" "$LOCAL_ADDRESS" RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/websockify

1 0

r25935: {} tonight's presentation for northeastern grad students (in projects/presentations: . images)
by Andrew Lewman 06 Dec '12

06 Dec '12

Author: phobos Date: 2012-12-06 05:21:37 +0000 (Thu, 06 Dec 2012) New Revision: 25935 Added: projects/presentations/2012-12-05-NEU-AnonComms-outline.txt projects/presentations/2012-12-05-NEU-AnonComms.pdf projects/presentations/images/envelopes.jpg projects/presentations/images/iograph-torproject-website.png projects/presentations/images/obfsproxy_diagram.png projects/presentations/images/wwwhatranorg.jpg Log: tonight's presentation for northeastern grad students Added: projects/presentations/2012-12-05-NEU-AnonComms-outline.txt =================================================================== --- projects/presentations/2012-12-05-NEU-AnonComms-outline.txt (rev 0) +++ projects/presentations/2012-12-05-NEU-AnonComms-outline.txt 2012-12-06 05:21:37 UTC (rev 25935) @@ -0,0 +1,288 @@ +% Anonymous Communications +% Andrew Lewman andrew(a)torproject.org +% December 05, 2012 + +# Who is this guy? + +501(c)(3) non-profit organization dedicated to the research and development of technologies for online anonymity and privacy + +[https://www.torproject.org](https://www.torproject.org) + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/2009-oval_sticker_new} +\end{center} + +# Three hours of this guy talking? + +Let's hope not. + +Ask questions; early and often. + +# Agenda + - Definitions and Concepts of Anonymity + - What data? + - Attacks against anonymity + - Deployed Systems (Centralized and Decentralized) + +# What is Anonymity? +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/2llg3ts.jpg} +\end{center} + +# Definitions: Anonymity + + - a set of all possible subjects + - state of not being identifiable within anonymity set + +# Definitions: Unlinkability + + - unlinkability of two or more items of interest from the adversary's perspective + - items can be messages, people, events, actions, etc + +# Definitions: Unobservability + + - state of items of interest being indistinguishable from any items of interest + +# Definitions: Pseudonymity + + - identifiers of sets of subjects + +# Definitions: Traffic Analysis + + - The who, what, when of traffic + - Think of the post office + +# Definitions: Steganography + + - the art and science of writing hidden messages in such a way that no one, apart from the sender and intended recipient, suspects the existence of the message, a form of security through obscurity. -- [Wikipedia](https://en.wikipedia.org/wiki/Steganography) + - alice or bob are talking, but to whom? + +# Definitions: Cryptography + - protecting content in transit + - does nothing to hide the traffic of items of interest + +# What data to protect? + + - bits of info which put together deanonymize you + - Names of individuals + - location address (street, IP address, zipcode, etc) + - operating system info + - language info + - amount of data sent + - amount of data received + - traffic timing (heartbeats) + +# Anonymity Loves Company + - make the set of users as large and coherent as possible to create a large anonymity set + +# Attacking Anonymity: Timing Analysis + - An attack used to analyze the time properties of data transfer between items of interest. + - When was data sent? + - How much was data sent? + - How long did it take to send the data? + - When was data received? + - wireshark demo + +# Attacking Anonymity: Timing Analysis + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/iograph-torproject-website.png} +\end{center} + +# Attacking Anonymity: Statistical Disclosure + + - Also called an intersection attack + - trying to identify mutually disjoint sets of recipients + - exponential time involved per number of messages to be analyzed + +# Attacking Anonymity: Tagging + + - tagging (make one item of interest unique) + +# Attacking Anonymity: Traffic Confirmation + + - who sends, how often, and when + - etherape demo + +# Centralized Systems + + - cheap, easy, ubiquitous + - PPTP, IPSec, SSL, SSH, XMPP common protocols + +# Proxy and VPN Servers + - proxy server works on your behalf + - VPN is virtual private network + - proxy for the network layers (layers 2 or 3 of OSI model) + +# Proxy and VPN Servers + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/single_hop_relay.jpg} +\end{center} + +# Trusting the provider + + - trusting the provider + - promises, contracts, mistakes + - some may filter or clean data before passing on to destination + +# Trusting the provider + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/evil_single_hop_relay.jpg} +\end{center} + +# Irrelevant provider + + - Single machine, or cluster of machines, are connected to a network + - If the proxy provider won't cooperate, use the network around it. + +# Irrelevant provider + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/data_snooping_single_hop_relay.jpg} +\end{center} + +# Decentralized Systems + +## Mix Networks + - cascades (JonDos/JonDonym) + - routes (tor) + +## Similar Routing networks + - I2P - Garlic routing, closed network, anonymity and reputation + - Freenet - closed network, anonymity, distributed file storage and sharing + - GNUnet - closed network, anonymity, distributed file storage and sharing + +# Break? + +Anyone need a bio-break for 10 minutes? + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/wwwhatranorg} +\end{center} + +# What is Tor? + + - online anonymity software and network + - open source, freely available (3-clause BSD license) + - active research environment: + +Drexel, Univ of Waterloo, Georgia Tech, Princeton, Boston University, University College London, Univ of Minnesota, National Science Foundation, Naval Research Labs, Cambridge UK, Bamberg Germany, MIT... + + - increasingly diverse toolset: + +Tor, Tor Browser Bundle, Tails Live System, Orbot/OrWeb, Tor Weather, Tor auto-responder, Secure Updater, Arm, Tor2Web, and so on. + +# Who uses Tor? + +\parbox{8cm}{\sloppy \setbeamercolor{background}[\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/anonymousman}} +\parbox{3cm}{\sloppy +\begin{flushleft} +\begin{itemize} +\begin{small} +\item Normal people +\item Journalists +\item Law Enforcement +\item Human Rights Activists +\item Business Execs +\item Militaries +\item Abuse Victims +\end{small} +\end{itemize} +\end{flushleft} +} + +# How many people use Tor? + +estimated 500k to 900k daily users + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/huge-crowd} +\end{center} + +# How does Tor work? + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/tor-network} +\end{center} + +# How does Tor work? + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/tor-safe-selection} +\end{center} + +# How does Tor work? + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/tor-safe-path} +\end{center} + +# How does Tor work? + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/tor-keys1} +\end{center} + +# Attacks on Tor + + - First hop can learn your IP address. + - Last hop can watch your traffic. + +# Attacks on Tor + + - Adversary can block all Tor nodes by IP address and TCP port + - our answer is to use non-public relays called Bridges + - Adversary can legally harass last hop; DMCA, Child Abuse Materials, Threats, etc + - Adversary can run relays, use network to restrict access to other relays + +# Attacks on Tor + + - Deep Packet Inspection + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/procera-evolved-dpi} +\end{center} + +# Attacks on Tor + +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/iran-ssl-dpi-26-seconds-to-death} + +# The Future: Usability + + Who are our users? What do they understand about anonymity, Tor, and privacy online? + Can we guide them to make smarter decisions? + How do we educate them before they start? + +# The Future: Obfsproxy & Pluggable Transports + + Obfuscating proxy for network traffic + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/obfsproxy_diagram.png} +\end{center} + +# The Future: Scaling + + Why not 10,000 relays? Why not 1 million? 10 million? + Need privacy-preserving Scalable Distributed Hash Table designs + +# The Future: IPv6 + + Basic support for IPv6 clients and relays works now. + Need support for IPv6 destinations and pure IPv6 relays + +# The Future: UDP + + Tor only transports TCP packets now. + This limits usable applications + Need to support real-time video and audio chats over Tor. + +# Thanks! + +\begin{center} +\includegraphics[keepaspectratio,width=\textwidth, height=.8\textheight]{images/thankyou_img} +\end{center} + +Visit [https://www.torproject.org](https://www.torproject.org) for more information, links, and ideas. Property changes on: projects/presentations/2012-12-05-NEU-AnonComms-outline.txt ___________________________________________________________________ Added: svn:mime-type + text/plain Added: svn:eol-style + native Added: projects/presentations/2012-12-05-NEU-AnonComms.pdf =================================================================== (Binary files differ) Property changes on: projects/presentations/2012-12-05-NEU-AnonComms.pdf ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: projects/presentations/images/envelopes.jpg =================================================================== (Binary files differ) Property changes on: projects/presentations/images/envelopes.jpg ___________________________________________________________________ Added: svn:mime-type + image/jpeg Added: projects/presentations/images/iograph-torproject-website.png =================================================================== (Binary files differ) Property changes on: projects/presentations/images/iograph-torproject-website.png ___________________________________________________________________ Added: svn:mime-type + image/png Added: projects/presentations/images/obfsproxy_diagram.png =================================================================== (Binary files differ) Property changes on: projects/presentations/images/obfsproxy_diagram.png ___________________________________________________________________ Added: svn:mime-type + image/png Added: projects/presentations/images/wwwhatranorg.jpg =================================================================== (Binary files differ) Property changes on: projects/presentations/images/wwwhatranorg.jpg ___________________________________________________________________ Added: svn:mime-type + image/jpeg

1 0

[ooni-probe/master] Update to match suggestion by Art
by ioerror＠torproject.org 05 Dec '12

05 Dec '12

commit 03076bc639c8dc3e15a6fb4509fdb611042e7b9a Author: Jacob Appelbaum <jacob(a)appelbaum.net> Date: Thu Dec 6 02:20:15 2012 +0630 Update to match suggestion by Art --- nettests/third_party/netalyzr.py | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/nettests/third_party/netalyzr.py b/nettests/third_party/netalyzr.py index 01c57f8..b3a0a3d 100644 --- a/nettests/third_party/netalyzr.py +++ b/nettests/third_party/netalyzr.py @@ -33,9 +33,9 @@ class NetalyzrWrapperTest(nettest.NetTestCase): def blocking_call(self): try: - result = threads.blockingCallFromThread(reactor, os.system(self.run_me)) + result = threads.blockingCallFromThread(reactor, os.system, self.run_me) except: - print "Please check " + self.output_file + "for Netalyzr output" + log.debug("Netalyzr had an error, please see the log file: %s" % self.output_file) finally: reactor.callFromThread(reactor.stop) self.clean_up() @@ -43,6 +43,7 @@ class NetalyzrWrapperTest(nettest.NetTestCase): def clean_up(self): self.report['netalyzr_report'] = self.output_file log.debug("finished running NetalzrWrapper") + log.debug("Please check %s for Netalyzr output" % self.output_file) def test_run_netalyzr(self): """

1 0

[ooni-probe/master] Update nettests/third_party/netalyzr.py to properly run and not hang
by ioerror＠torproject.org 05 Dec '12

05 Dec '12

commit 1aa7c70e7cea0d7912aa01d39e52282bc643ebff Author: Jacob Appelbaum <jacob(a)appelbaum.net> Date: Thu Dec 6 01:54:06 2012 +0630 Update nettests/third_party/netalyzr.py to properly run and not hang nettests/third_party/netalyzr.py now runs properly though the status output is incorrectly shown to be 100% at all times. --- nettests/third_party/netalyzr.py | 19 +++++++++++++++---- 1 files changed, 15 insertions(+), 4 deletions(-) diff --git a/nettests/third_party/netalyzr.py b/nettests/third_party/netalyzr.py index 6ce5a9f..01c57f8 100644 --- a/nettests/third_party/netalyzr.py +++ b/nettests/third_party/netalyzr.py @@ -10,6 +10,7 @@ from ooni import nettest from ooni.utils import log import time import os +from twisted.internet import reactor, threads, defer class NetalyzrWrapperTest(nettest.NetTestCase): name = "NetalyzrWrapper" @@ -30,6 +31,19 @@ class NetalyzrWrapperTest(nettest.NetTestCase): self.output_file.strip() self.run_me = program + " 2>&1 >> " + self.output_file + def blocking_call(self): + try: + result = threads.blockingCallFromThread(reactor, os.system(self.run_me)) + except: + print "Please check " + self.output_file + "for Netalyzr output" + finally: + reactor.callFromThread(reactor.stop) + self.clean_up() + + def clean_up(self): + self.report['netalyzr_report'] = self.output_file + log.debug("finished running NetalzrWrapper") + def test_run_netalyzr(self): """ This test simply wraps netalyzr and runs it from command line @@ -41,7 +55,4 @@ class NetalyzrWrapperTest(nettest.NetTestCase): # (currently there is no progress because the stdout of os.system is # trapped by twisted) and to include the link to the netalyzr report # directly in the OONI report, perhaps even downloading it. - os.system(self.run_me) - self.report['netalyzr_report'] = self.output_file - log.debug("finished running NetalzrWrapper") - + reactor.callInThread(self.blocking_call)

1 0

[onionoo/master] Fix off-by-one error in offset parameter.
by karsten＠torproject.org 05 Dec '12

05 Dec '12

commit ffd88279ab2dd03b367d878cee6207a82857196a Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Wed Dec 5 20:06:39 2012 +0100 Fix off-by-one error in offset parameter. With 10 relays and 10 bridges, setting an offset of 11 should have returned 9 bridges (relays are removed first), but it return 10. An offset of 12 would have returned 9 bridges, and so on. Here's why: we erroneously added a null value to the set of relays before applying the offset parameter. After throwing out the last relay we threw out that null value instead of the first bridge. --- src/org/torproject/onionoo/ResourceServlet.java | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/org/torproject/onionoo/ResourceServlet.java b/src/org/torproject/onionoo/ResourceServlet.java index 9a2e353..bc075b0 100644 --- a/src/org/torproject/onionoo/ResourceServlet.java +++ b/src/org/torproject/onionoo/ResourceServlet.java @@ -279,7 +279,7 @@ public class ResourceServlet extends HttpServlet { orderedRelays.add(filteredRelays.remove(relay)); } } - for (String relay : filteredRelays.values()) { + for (String relay : filteredRelays.keySet()) { if (!orderedRelays.contains(filteredRelays.get(relay))) { orderedRelays.add(filteredRelays.remove(relay)); }

1 0