tor-commits April 2016

tor-commits@lists.torproject.org

20 participants
1645 discussions

[stem/master] str_tools crop() issue with zero size
by atagar＠torproject.org 10 Apr '16

10 Apr '16

commit 2f31248f254d5dae2ed11c0a70b98e465c5b185c Author: Damian Johnson <atagar(a)torproject.org> Date: Sun Apr 10 11:19:26 2016 -0700 str_tools crop() issue with zero size Our str_tools crop() function provided a longer string than it should when given a width less than three. This is because ending with an ellipse subtracts three causing us to have a negative size, causing a wrap. --- stem/util/str_tools.py | 3 +++ test/unit/util/str_tools.py | 1 + 2 files changed, 4 insertions(+) diff --git a/stem/util/str_tools.py b/stem/util/str_tools.py index a64f6c2..a01eb8a 100644 --- a/stem/util/str_tools.py +++ b/stem/util/str_tools.py @@ -210,6 +210,9 @@ def crop(msg, size, min_word_length = 4, min_crop = 0, ending = Ending.ELLIPSE, # ellipse, and cropping words requires an extra space for hyphens if ending == Ending.ELLIPSE: + if size < 3: + return ('', msg) if get_remainder else '' + size -= 3 elif min_word_length and ending == Ending.HYPHEN: min_word_length += 1 diff --git a/test/unit/util/str_tools.py b/test/unit/util/str_tools.py index 922026c..3d0936f 100644 --- a/test/unit/util/str_tools.py +++ b/test/unit/util/str_tools.py @@ -30,6 +30,7 @@ class TestStrTools(unittest.TestCase): self.assertEqual('This is a looo...', str_tools.crop('This is a looooong message', 17)) self.assertEqual('This is a...', str_tools.crop('This is a looooong message', 12)) self.assertEqual('', str_tools.crop('This is a looooong message', 3)) + self.assertEqual('', str_tools.crop('This is a looooong message', 0)) def test_size_label(self): """

1 0

[translation/tor-launcher-network-settings_completed] Update translations for tor-launcher-network-settings_completed
by translation＠torproject.org 10 Apr '16

10 Apr '16

commit b9f35ebd29c6b13b396f57cb6bb9cacc2054d793 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Apr 10 05:45:43 2016 +0000 Update translations for tor-launcher-network-settings_completed --- zh_CN/network-settings.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh_CN/network-settings.dtd b/zh_CN/network-settings.dtd index 3adf58a..c9619ae 100644 --- a/zh_CN/network-settings.dtd +++ b/zh_CN/network-settings.dtd @@ -55,7 +55,7 @@ <!ENTITY torsettings.firewall.checkbox "该计算机的防火墙仅允许特定端口的互联网连接"> <!ENTITY torsettings.firewall.allowedPorts "允许的端口："> <!ENTITY torsettings.useBridges.checkbox "我的互联网服务提供商 (ISP) 封锁了 Tor 网络连接"> -<!ENTITY torsettings.useBridges.default "使用集成的网桥进行连接"> +<!ENTITY torsettings.useBridges.default "使用集成的网桥连接"> <!ENTITY torsettings.useBridges.note "每种网桥使用不同的方法以避免被封锁。如果某个网桥不工作，请换用另一种重试。"> <!ENTITY torsettings.useBridges.type "传输类型："> <!ENTITY torsettings.useBridges.custom "输入自定义网桥">

1 0

[translation/tor-launcher-network-settings] Update translations for tor-launcher-network-settings
by translation＠torproject.org 10 Apr '16

10 Apr '16

commit a94190f28d42c22fba6c508a3be5fb16a6a91a22 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Apr 10 05:45:39 2016 +0000 Update translations for tor-launcher-network-settings --- zh_CN/network-settings.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh_CN/network-settings.dtd b/zh_CN/network-settings.dtd index 3adf58a..c9619ae 100644 --- a/zh_CN/network-settings.dtd +++ b/zh_CN/network-settings.dtd @@ -55,7 +55,7 @@ <!ENTITY torsettings.firewall.checkbox "该计算机的防火墙仅允许特定端口的互联网连接"> <!ENTITY torsettings.firewall.allowedPorts "允许的端口："> <!ENTITY torsettings.useBridges.checkbox "我的互联网服务提供商 (ISP) 封锁了 Tor 网络连接"> -<!ENTITY torsettings.useBridges.default "使用集成的网桥进行连接"> +<!ENTITY torsettings.useBridges.default "使用集成的网桥连接"> <!ENTITY torsettings.useBridges.note "每种网桥使用不同的方法以避免被封锁。如果某个网桥不工作，请换用另一种重试。"> <!ENTITY torsettings.useBridges.type "传输类型："> <!ENTITY torsettings.useBridges.custom "输入自定义网桥">

1 0

[translation/abouttor-homepage_completed] Update translations for abouttor-homepage_completed
by translation＠torproject.org 10 Apr '16

10 Apr '16

commit 25f11c8d7c7cd16cef051f5243282e30a8ec8dfe Author: Translation commit bot <translation(a)torproject.org> Date: Sun Apr 10 04:15:50 2016 +0000 Update translations for abouttor-homepage_completed --- es_CO/aboutTor.dtd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/es_CO/aboutTor.dtd b/es_CO/aboutTor.dtd index 894f362..1701157 100644 --- a/es_CO/aboutTor.dtd +++ b/es_CO/aboutTor.dtd @@ -6,14 +6,14 @@ <!ENTITY aboutTor.title "Acerca de Tor"> -<!ENTITY aboutTor.outOfDateTorOn.label "SIN EMBARGO, este navegador está desactualizado."> +<!ENTITY aboutTor.outOfDateTorOn.label "ADVERTENCIA: este navegador está desactualizado."> <!ENTITY aboutTor.outOfDateTorOff.label "ADEMÁS, este navegador está desactualizado."> <!ENTITY aboutTor.outOfDate2.label "Haz clic en la cebolla y despues selecciona Verificar para Actualizar el Navegador Tor"> <!ENTITY aboutTor.check.label "Probar configuraciones de red de Tor"> -<!ENTITY aboutTor.success.label "Felicitaciones!"> -<!ENTITY aboutTor.success2.label "Este navegador está configurado para usar Tor."> +<!ENTITY aboutTor.success.label "Bienvenido al Navegador Tor"> +<!ENTITY aboutTor.success2.label "Conectado a la red de Tor"> <!ENTITY aboutTor.success3.label "Ahora usted es libre de navegar por Internet anónimamente."> <!ENTITY aboutTor.failure.label "Algo salió mal!"> <!ENTITY aboutTor.failure2.label "Tor no está funcionando en este navegador.">

1 0

[translation/abouttor-homepage] Update translations for abouttor-homepage
by translation＠torproject.org 10 Apr '16

10 Apr '16

commit 41727ab003a4a9040d0da30c969a15acfab98094 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Apr 10 04:15:47 2016 +0000 Update translations for abouttor-homepage --- es_CO/aboutTor.dtd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/es_CO/aboutTor.dtd b/es_CO/aboutTor.dtd index 1c7f427..1701157 100644 --- a/es_CO/aboutTor.dtd +++ b/es_CO/aboutTor.dtd @@ -6,14 +6,14 @@ <!ENTITY aboutTor.title "Acerca de Tor"> -<!ENTITY aboutTor.outOfDateTorOn.label "WARNING: this browser is out of date."> +<!ENTITY aboutTor.outOfDateTorOn.label "ADVERTENCIA: este navegador está desactualizado."> <!ENTITY aboutTor.outOfDateTorOff.label "ADEMÁS, este navegador está desactualizado."> <!ENTITY aboutTor.outOfDate2.label "Haz clic en la cebolla y despues selecciona Verificar para Actualizar el Navegador Tor"> <!ENTITY aboutTor.check.label "Probar configuraciones de red de Tor"> -<!ENTITY aboutTor.success.label "Welcome to Tor Browser"> -<!ENTITY aboutTor.success2.label "Connected to the Tor network."> +<!ENTITY aboutTor.success.label "Bienvenido al Navegador Tor"> +<!ENTITY aboutTor.success2.label "Conectado a la red de Tor"> <!ENTITY aboutTor.success3.label "Ahora usted es libre de navegar por Internet anónimamente."> <!ENTITY aboutTor.failure.label "Algo salió mal!"> <!ENTITY aboutTor.failure2.label "Tor no está funcionando en este navegador.">

1 0

[translation/https_everywhere] Update translations for https_everywhere
by translation＠torproject.org 10 Apr '16

10 Apr '16

commit de4d5f7ed90ba879573037b471f38ece9957ed17 Author: Translation commit bot <translation(a)torproject.org> Date: Sun Apr 10 04:15:16 2016 +0000 Update translations for https_everywhere --- es_CO/https-everywhere.dtd | 58 +++++++++++++++++++++++----------------------- 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/es_CO/https-everywhere.dtd b/es_CO/https-everywhere.dtd index a0198ca..82c2954 100644 --- a/es_CO/https-everywhere.dtd +++ b/es_CO/https-everywhere.dtd @@ -1,56 +1,56 @@ -<!ENTITY https-everywhere.about.title "About HTTPS Everywhere"> +<!ENTITY https-everywhere.about.title "Acerca de HTTPS Everywhere"> <!ENTITY https-everywhere.about.ext_name "HTTPS Everywhere"> <!ENTITY https-everywhere.about.ext_description "Encrypt the Web! Automatically use HTTPS security on many sites."> <!ENTITY https-everywhere.about.version "Version"> -<!ENTITY https-everywhere.about.created_by "Created by"> -<!ENTITY https-everywhere.about.and ", and"> +<!ENTITY https-everywhere.about.created_by "Creado por"> +<!ENTITY https-everywhere.about.and ", y"> <!ENTITY https-everywhere.about.librarians "Ruleset Librarians"> -<!ENTITY https-everywhere.about.thanks "Thanks to"> -<!ENTITY https-everywhere.about.many_contributors "Many many contributors, including"> +<!ENTITY https-everywhere.about.thanks "Gracias a"> +<!ENTITY https-everywhere.about.many_contributors "Muchos muchos colaboradores, incluyendo"> <!ENTITY https-everywhere.about.noscript "Also, portions of HTTPS Everywhere are based on code from NoScript, by Giorgio Maone and others. We are grateful for their excellent work!"> -<!ENTITY https-everywhere.about.contribute "If you like HTTPS Everywhere, you might consider"> -<!ENTITY https-everywhere.about.donate_tor "Donating to Tor"> +<!ENTITY https-everywhere.about.contribute "Si te gusta HTTPS Everywhere, podrías considerar"> +<!ENTITY https-everywhere.about.donate_tor "Donando a Tor"> <!ENTITY https-everywhere.about.tor_lang_code "en"> <!ENTITY https-everywhere.about.or "or"> -<!ENTITY https-everywhere.about.donate_eff "Donating to EFF"> +<!ENTITY https-everywhere.about.donate_eff "Donando a EFF"> -<!ENTITY https-everywhere.menu.donate_eff_imperative "Donate to EFF"> -<!ENTITY https-everywhere.menu.about "About HTTPS Everywhere"> +<!ENTITY https-everywhere.menu.donate_eff_imperative "Donar a EFF"> +<!ENTITY https-everywhere.menu.about "Acerca de HTTPS Everywhere"> <!ENTITY https-everywhere.menu.observatory "SSL Observatory Preferences"> <!ENTITY https-everywhere.menu.globalEnable "Habilitar HTTPS Everywhere"> <!ENTITY https-everywhere.menu.globalDisable "Desabilitar HTTPS Everywhere"> <!ENTITY https-everywhere.menu.blockHttpRequests "Block all HTTP requests"> <!ENTITY https-everywhere.menu.showCounter "Show Counter"> -<!ENTITY https-everywhere.menu.viewAllRules "View All Rules"> +<!ENTITY https-everywhere.menu.viewAllRules "Ver Todas Las Reglas"> -<!ENTITY https-everywhere.prefs.title "HTTPS Everywhere Preferences"> -<!ENTITY https-everywhere.prefs.enable_all "Enable All"> -<!ENTITY https-everywhere.prefs.disable_all "Disable All"> -<!ENTITY https-everywhere.prefs.reset_defaults "Reset to Defaults"> +<!ENTITY https-everywhere.prefs.title "Preferencias de HTTPS Everywhere"> +<!ENTITY https-everywhere.prefs.enable_all "Habilitar Todo"> +<!ENTITY https-everywhere.prefs.disable_all "Deshabilitar Todo"> +<!ENTITY https-everywhere.prefs.reset_defaults "Reestablecer a Valores Predeterminados"> <!ENTITY https-everywhere.prefs.search "Buscar"> -<!ENTITY https-everywhere.prefs.site "Site"> -<!ENTITY https-everywhere.prefs.notes "Notes"> +<!ENTITY https-everywhere.prefs.site "Sitio"> +<!ENTITY https-everywhere.prefs.notes "Notas"> <!ENTITY https-everywhere.prefs.list_caption "Which HTTPS redirection rules should apply?"> -<!ENTITY https-everywhere.prefs.enabled "Enabled"> +<!ENTITY https-everywhere.prefs.enabled "Habilitado"> <!ENTITY https-everywhere.prefs.ruleset_howto "You can learn how to write your own rulesets (to add support for other web sites)"> -<!ENTITY https-everywhere.prefs.here_link "here"> -<!ENTITY https-everywhere.prefs.toggle "Toggle"> -<!ENTITY https-everywhere.prefs.reset_default "Reset to Default"> -<!ENTITY https-everywhere.prefs.view_xml_source "View XML Source"> +<!ENTITY https-everywhere.prefs.here_link "aquí"> +<!ENTITY https-everywhere.prefs.toggle "Alternar"> +<!ENTITY https-everywhere.prefs.reset_default "Reestablecer a Valor Predeterminado"> +<!ENTITY https-everywhere.prefs.view_xml_source "Ver Fuente XML"> <!ENTITY https-everywhere.chrome.stable_rules "Stable rules"> -<!ENTITY https-everywhere.chrome.stable_rules_description "Force encrypted connections to these websites:"> -<!ENTITY https-everywhere.chrome.experimental_rules "Experimental rules"> +<!ENTITY https-everywhere.chrome.stable_rules_description "Forzar conecciones encriptadas para estos sitios web:"> +<!ENTITY https-everywhere.chrome.experimental_rules "Reglas experimentales"> <!ENTITY https-everywhere.chrome.experimental_rules_description "May cause warnings or breakage. Disabled by default."> -<!ENTITY https-everywhere.chrome.add_rule "Add a rule for this site"> -<!ENTITY https-everywhere.chrome.add_new_rule "Add a new rule for this site"> -<!ENTITY https-everywhere.chrome.always_https_for_host "Always use https for this host"> +<!ENTITY https-everywhere.chrome.add_rule "Añadir una regla para este sitio"> +<!ENTITY https-everywhere.chrome.add_new_rule "Añadir una nueva regla para este sitio"> +<!ENTITY https-everywhere.chrome.always_https_for_host "Siempre usar https para este host"> <!ENTITY https-everywhere.chrome.host "Host:"> <!ENTITY https-everywhere.chrome.show_advanced "Show advanced"> <!ENTITY https-everywhere.chrome.hide_advanced "Hide advanced"> -<!ENTITY https-everywhere.chrome.rule_name "Rule name"> +<!ENTITY https-everywhere.chrome.rule_name "Nombre de regla"> <!ENTITY https-everywhere.chrome.regex "Matching regex"> -<!ENTITY https-everywhere.chrome.redirect_to "Redirect to"> +<!ENTITY https-everywhere.chrome.redirect_to "Redireccionar a"> <!ENTITY https-everywhere.chrome.status_cancel_button "Cancelar">

1 0

[torspec/master] prop224: Minor fixes to descriptor format
by asn＠torproject.org 09 Apr '16

09 Apr '16

commit fdd5cc01bcb3c02901c51e3bd9f5812e4066c43b Author: John Brooks <special(a)torproject.org> Date: Thu Mar 10 19:25:45 2016 +0100 prop224: Minor fixes to descriptor format --- proposals/224-rend-spec-ng.txt | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index f7a4304..78b2071 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -942,11 +942,14 @@ Status: Draft The encrypted part of the hidden service descriptor is encrypted and authenticated with symmetric keys generated as follows: - salt = 16 random bytes, different for each post to each replica, + SALT = 16 bytes from H(random), different for each post to each replica, even if the content of the descriptor hasn't changed. (This avoids leaking service stability, and linking replicas via encrypted data comparison.) + (We hash salt so that we don't leak the raw bytes returned by a PRNG + to the network. See [RANDOM-REFS].) + [ XX/teor - is the extra load on the HSDirs worth it? ] secret_input = blinded_public_key(replica-keynum) | @@ -960,13 +963,10 @@ Status: Draft The encrypted data has the format: - H(SALT) H(random bytes from above) [16 bytes] + SALT hashed random bytes from above [16 bytes] ENCRYPTED The plaintext encrypted with S [variable] MAC MAC of both above fields [32 bytes] - (We hash salt so that we don't leak the raw bytes returned by a PRNG - to the network. See [RANDOM-REFS].) - The encryption format is ENCRYPTED = STREAM(SECRET_IV,SECRET_KEY) xor Plaintext @@ -1040,6 +1040,8 @@ Status: Draft [TODO: I'd like to have a cross-certification here too.] + To remain compatible with future revisions to the descriptor format, + clients should ignore unrecognized lines in the descriptor. Other encryption and authentication key formats are allowed; clients should ignore ones they do not recognize.

1 0

[torspec/master] prop224: Some syntax fixes and remove time-period
by asn＠torproject.org 09 Apr '16

09 Apr '16

commit 68c654d37aaa4c3f9e87b6639c95509715369367 Author: David Goulet <dgoulet(a)ev0ke.net> Date: Thu Mar 10 09:50:41 2016 -0500 prop224: Some syntax fixes and remove time-period Signed-off-by: David Goulet <dgoulet(a)ev0ke.net> --- proposals/224-rend-spec-ng.txt | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index 8dd30b0..f7a4304 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -839,23 +839,19 @@ Status: Draft The format for a hidden service descriptor is as follows, using the meta-format from dir-spec.txt. - "hs-descriptor" SP "3" certificate NL + "hs-descriptor" SP version-number SP certificate NL [At start, exactly once.] + The version-number contains a positive integer indicating the version + of the descriptor. Current version is "3". + The 'certificate' field contains a certificate in the format from proposal 220, with the short-term ed25519 descriptor-signing key for the replica, signed by the blinded public key for the replica. It must contain a ed25519-signing-key extension containing the blinded public key for the replica. - "time-period" SP YYYY-MM-DD HH:MM:SS NUM NL - - [Exactly once.] - - The time period for which this descriptor is relevant, including - its starting time and its period number. - "revision-counter" SP Integer NL [Exactly once.] @@ -987,10 +983,10 @@ Status: Draft [Exactly once] - A space-separated list of integers denoting CREATE2 cell format - numbers that the server recognizes. Must include at least TAP and - ntor as described in tor-spec.txt. See tor-spec section 5.1 for a - list of recognized handshake types. + A space-separated list of integers denoting CREATE2 cell format numbers + that the server recognizes. Must include at least ntor as described in + tor-spec.txt. See tor-spec section 5.1 for a list of recognized + handshake types. "authentication-required" SP types NL @@ -1011,7 +1007,7 @@ Status: Draft The link-specifiers is a base64 encoding of a link specifier block in the format described in BUILDING-BLOCKS. - "auth-key" SP "ed25519" certificate NL + "auth-key" SP "ed25519" SP certificate NL [Exactly once per introduction point]

1 0

[torspec/master] prop224: In cells, replace TYPE/LEN/KEY with just TYPE/KEY.
by asn＠torproject.org 09 Apr '16

09 Apr '16

commit 83a62b6e0f31dcb8fbe917ac9d406b78193605b7 Author: George Kadianakis <desnacked(a)riseup.net> Date: Tue Mar 15 15:28:25 2016 +0200 prop224: In cells, replace TYPE/LEN/KEY with just TYPE/KEY. --- proposals/224-rend-spec-ng.txt | 45 +++++++++++++++++++++++++++--------------- 1 file changed, 29 insertions(+), 16 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index dd76e36..d80b2d5 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -153,6 +153,18 @@ Status: Draft themselves, but over those strings prefixed with a distinguishing value. + Through this proposal we use the following construction when sending + cryptographic keys in tor cells: + + KEYTYPE [1 byte] + KEY [depends on KEYTYPE] + + In this case the size of the KEY depends on the KEYTYPE. Here are the + currently defined key types: + + * The KEYTYPE value [01] is for Ed25519 keys (size: 32 bytes). + * The KEYTYPE value [02] is for Curve25519 keys (size: 32 bytes). + * The KEYTYPE value [03] is for truncated Curve25519 keys (size: 8 bytes). 0.4. Protocol building blocks [BUILDING-BLOCKS] @@ -1182,14 +1194,11 @@ Status: Draft NUMKEYS [1 byte] NUMKEYS times: KEYTYPE [1 byte] - KEYLEN [1 byte] - KEY [KEYLEN bytes] + KEY [depends on KEYTYPE] COUNTER [4 bytes] SIGLEN [1 byte] SIGNATURE [SIGLEN bytes.] - The KEYTYPE value [01] is for Curve25519 keys. - The COUNTER field is a monotonically increasing value across a given introduction point authentication key. @@ -1252,9 +1261,11 @@ Status: Draft An INTRODUCE1 cell has the following contents: - AUTH_KEYID [32 bytes] - ENC_KEYID [8 bytes] - N_EXTENSIONS [1 Byte] + AUTH_KEYTYPE [1 byte] + AUTH_KEYID [depends on AUTH_KEYTYPE] + ENC_KEYTYPE [1 byte] + ENC_KEYID [depends on ENC_KEYTYPE] + N_EXTENSIONS [1 byte] N_EXTENSIONS times: EXT_FIELD_TYPE [1 byte] EXT_FIELD_LEN [1 byte] @@ -1275,12 +1286,12 @@ Status: Draft running whose PK_ID is the first 20 bytes of AUTH_KEYID. If so, it behaves as in rend-spec.txt.) - The AUTH_KEYID for an Ed25519 public key is the public key itself. - The ENC_KEYID for a Curve25519 public key is the first 8 bytes of the - public key. (This key ID is safe to truncate, since all the keys are - generated by the hidden service host, and the ID is only valid - relative to a single AUTH_KEYID.) The ENCRYPTED field is as - described in 3.3 below. + The AUTH_KEYTYPE is an Ed25519 public key (value [01]). + + The ENC_KEYTYPE is a truncated Curve25519 public key (value [03]). (This key + is safe to truncate, since all the keys are generated by the hidden service + host, and the ID is only valid relative to a single AUTH_KEYID.) The + ENCRYPTED field is as described in 3.3 below. To relay an INTRODUCE1 cell, the introduction point sends an INTRODUCE2 cell with exactly the same contents. @@ -1360,7 +1371,7 @@ Status: Draft EXT_FIELD_TYPE [1 byte] EXT_FIELD_LEN [1 byte] EXT_FIELD [EXT_FIELD_LEN bytes] - ONION_KEY_TYPE [2 bytes] + ONION_KEY_TYPE [1 bytes] ONION_KEY [depends on ONION_KEY_TYPE] NSPEC (Number of link specifiers) [1 byte] NSPEC times: @@ -1458,8 +1469,10 @@ Status: Draft Substituting those fields into the INTRODUCE1 cell body format described in [FMT_INTRO1] above, we have - AUTH_KEYID [32 bytes] - ENC_KEYID [8 bytes] + AUTH_KEYTYPE [1 byte] + AUTH_KEYID [depends on AUTH_KEYTYPE] + ENC_KEYTYPE [1 byte] + ENC_KEYID [depends on ENC_KEYTYPE] N_EXTENSIONS [1 bytes] N_EXTENSIONS times: EXT_FIELD_TYPE [1 byte]

1 0

[torspec/master] prop224: Clarify use of shared random values.
by asn＠torproject.org 09 Apr '16

09 Apr '16

commit 2b8a0103b9f36a0b834ce1bde6608557fe10f866 Author: George Kadianakis <desnacked(a)riseup.net> Date: Tue Jan 5 16:28:11 2016 +0200 prop224: Clarify use of shared random values. --- proposals/224-rend-spec-ng.txt | 48 +++++++++++++++++++++--------------------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index 8e14e2a..aee91bf 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -797,35 +797,36 @@ Status: Draft to generate such a value at least once per hsdir period. Here we describe how they publish these values; the procedure they use to generate them can change independently of the rest of this - specification. For one possible (somewhat broken) protocol, see - Appendix [SHAREDRANDOM]. + specification. For more information see [SHAREDRANDOM-REFS]. - We add a new line in votes and consensus documents: + According to proposal 250, we add two new lines in consensuses: - "hsdir-shared-random" PERIOD-START VALUE - PERIOD-START = YYYY-MM-DD HH:MM:SS - VALUE = A base-64 encoded 256-bit value. + "shared-rand-previous-value" SP NUM_REVEALS SP VALUE NL + "shared-rand-current-value" SP NUM_REVEALS SP VALUE NL - To decide which hsdir-shared-random line to include in a consensus - for a given PERIOD-START, we choose whichever line appears verbatim - in the most votes, so long as it is listed by at least three - authorities. Ties are broken in favor of the lower value. More than - one PERIOD-START is allowed per vote, and per consensus. The same - PERIOD-START must not appear twice in a vote or in a consensus. +2.3.1. Client behavior in the absense of shared random values - [TODO: Need to define a more robust algorithm. Need to cover cases - where multiple cluster of authorities publish a different value, - etc.] + If the previous or current shared random value cannot be found in a + consensus, then Tor clients need to generate their own random value for use + when choosing HSDirs. - The hs-dir-shared-random lines appear, sorted by PERIOD-START, in the - consensus immediately after the "params" line. + To do so, clients use: - The authorities should publish the shared random value for the - current period, and, at a time at least three voting periods before - the overlap interval begins, the shared random value for the next - period. + SRV = HMAC("shared-random-disaster", TIME_PERIOD_NUM) + + as the SRV for time period TIME_PERIOD_NUM. + +2.3.2. Hidden services and changing shared random values + + It's theoretically possible that the consensus shared random values will + change or disappear in the middle of a time period because of directory + authorities dropping offline or misbehaving. + + To avoid client reachability issues in this rare event, hidden services + should use the new shared random values to find the new responsible HSDirs + and upload their descriptors there. -[TODO: find out what weasel doesn't like here.] + XXX How long should they upload descriptors there for? 2.4. Hidden service descriptors: outer wrapper [DESC-OUTER] @@ -1705,9 +1706,8 @@ References: https://lists.torproject.org/pipermail/tor-dev/2013-December/005943.html [SHAREDRANDOM-REFS]: + https://gitweb.torproject.org/torspec.git/tree/proposals/250-commit-reveal-… https://trac.torproject.org/projects/tor/ticket/8244 - https://lists.torproject.org/pipermail/tor-dev/2013-November/005847.html - https://lists.torproject.org/pipermail/tor-talk/2013-November/031230.html [SCALING-REFS]: https://lists.torproject.org/pipermail/tor-dev/2013-October/005556.html

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits April 2016