April 2018 - tor-commits - lists.torproject.org

[torspec/master] rend-spec-v3: document trailing zero byte in BLIND_STRING (A.2.)
by nickm＠torproject.org 02 Apr '18

02 Apr '18

commit 73f26437470e4b4b360a484daaa1ce94efad317f Author: Filippo Valsorda <hi(a)filippo.io> Date: Fri Nov 17 15:18:57 2017 -0500 rend-spec-v3: document trailing zero byte in BLIND_STRING (A.2.) The implementation uses sizeof instead of strlen, so the C string NUL byte is hashed. --- rend-spec-v3.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt index ef5f940..d595268 100644 --- a/rend-spec-v3.txt +++ b/rend-spec-v3.txt @@ -2160,7 +2160,7 @@ A.2. Tor's key derivation scheme blinding factor like this: h = H(BLIND_STRING | A | s | B | N) - BLIND_STRING = "Derive temporary signing key" + BLIND_STRING = "Derive temporary signing key" | INT_1(0) N = "key-blind" | INT_8(period-number) | INT_8(period_length) then clamp the blinding factor 'h' according to the ed25519 spec:

1 0

[torspec/master] rend-spec-v3: add details to blinding implementation (A.2.)
by nickm＠torproject.org 02 Apr '18

02 Apr '18

commit 42e31d525b38fd8810006d7deacc8f41ef34db8d Author: Filippo Valsorda <hi(a)filippo.io> Date: Fri Nov 17 15:19:45 2017 -0500 rend-spec-v3: add details to blinding implementation (A.2.) In particular, document how to derive the second half of the private key. --- rend-spec-v3.txt | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt index d595268..e408e8b 100644 --- a/rend-spec-v3.txt +++ b/rend-spec-v3.txt @@ -2162,6 +2162,7 @@ A.2. Tor's key derivation scheme h = H(BLIND_STRING | A | s | B | N) BLIND_STRING = "Derive temporary signing key" | INT_1(0) N = "key-blind" | INT_8(period-number) | INT_8(period_length) + B = "(1511[...]2202, 4631[...]5960)" then clamp the blinding factor 'h' according to the ed25519 spec: @@ -2171,8 +2172,15 @@ A.2. Tor's key derivation scheme and do the key derivation as follows: - private key for the period: a' = h a - public key for the period: A' = h A = (ha)B + private key for the period: + + a' = h a mod l + RH' = SHA-512(RH_BLIND_STRING | RH)[:32] + RH_BLIND_STRING = "Derive temporary signing key hash input" + + public key for the period: + + A' = h A = (ha)B Generating a signature of M: given a deterministic random-looking r (see EdDSA paper), take R=rB, S=r+hash(R,A',M)ah mod l. Send signature @@ -2185,6 +2193,8 @@ A.2. Tor's key derivation scheme = rB + (hash(R,A',M)ah)B = R + hash(R,A',M)A' ) + This boils down to regular Ed25519 with key pair (a', A'). + See [KEYBLIND-REFS] for an extensive discussion on this scheme and possible alternatives. Also, see [KEYBLIND-PROOF] for a security proof of this scheme.

1 0

[torspec/master] dir-spec, rend-spec-v3: typos and simplifications
by nickm＠torproject.org 02 Apr '18

02 Apr '18

commit ae8d5de13ba64238bc24b841e6269af72b86460a Author: Filippo Valsorda <hi(a)filippo.io> Date: Fri Nov 17 15:22:17 2017 -0500 dir-spec, rend-spec-v3: typos and simplifications --- dir-spec.txt | 24 ++++++++++++------------ rend-spec-v3.txt | 2 +- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index 1c63b21..54e122f 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -285,11 +285,13 @@ <signature item keyword> [arguments] NL SIGNATURE NL The "SIGNATURE" Object contains a signature (using the signing key) of - the PKCS1-padded digest of the entire document, taken from the + the PKCS#1 1.5 padded digest of the entire document, taken from the beginning of the Initial item, through the newline after the Signature Item's keyword and its arguments. - Unless otherwise, the digest algorithm is SHA-1. + The signature does not include the algorithmIdentifier specified in PKCS #1. + + Unless specified otherwise, the digest algorithm is SHA-1. All documents are invalid unless signed with the correct signing key. @@ -2102,7 +2104,7 @@ See shared-rand-current-value decription above. - The authority section of a consensus contains groups the following items, + The authority section of a consensus contains groups of the following items, in the order given, with one group for each authority that contributed to the consensus, with groups sorted by authority identity digest: @@ -2144,7 +2146,8 @@ "Nickname" is the OR's nickname. "Identity" is a hash of its identity key, encoded in base64, with trailing equals sign(s) removed. "Digest" is a hash of its most recent descriptor as - signed (that is, not including the signature), encoded in base64. + signed (that is, not including the signature) by the RSA identity + key (see section 1.3.), encoded in base64. "Publication" is the publication time of its most recent descriptor, in the form YYYY-MM-DD HH:MM:SS, in UTC. Implementations MAY base @@ -3398,7 +3401,7 @@ prefer fallbacks to authorities, trying them earlier and more frequently. In all other cases, the client downloads from caches randomly chosen from among those believed to be V3 directory servers. (This information comes - from the network-status documents; see 6 below.) + from the network-status documents.) After receiving any response client MUST discard any network-status documents that it did not request. @@ -3484,8 +3487,8 @@ After choosing mirrors, the client divides the descriptors among them randomly. - After receiving any response client MUST discard any descriptors that it - did not request. + After receiving any response the client MUST discard any descriptors that + it did not request. When a descriptor download fails, the client notes it, and does not consider the descriptor downloadable again until a certain amount of time @@ -3847,11 +3850,8 @@ D. Inferring missing proto lines. Cons=1-2 Desc=1-2 DirCache=1 HSDir=1 HSIntro=3 HSRend=1-2 Link=1-4 LinkAuth=1 Microdesc=1-2 Relay=1-2 - For Desc, Tor versions before 0.2.7.stable should be taken to have Desc=1 - and versions 0.2.7.stable or later should have Desc=1-2. - - For Microdesc and Cons, Tor versions before 0.2.7.stable should be taken to - support version 1; 0.2.7.stable and later should have 1-2. + For Desc, Microdesc and Cons, Tor versions before 0.2.7.stable should be + taken to only support version 1. E. Limited ed diff format diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt index e408e8b..ebe05d8 100644 --- a/rend-spec-v3.txt +++ b/rend-spec-v3.txt @@ -2232,7 +2232,7 @@ Appendix C. Recommendations for searching for vanity .onions [VANITY] While pk does not satisfy X: Add the number 8 to sk - Add the scalar 8*B to pk + Add the point 8*B to pk Return sk, pk.

1 0

[torspec/master] Merge remote-tracking branch 'filippo/master'
by nickm＠torproject.org 02 Apr '18

02 Apr '18

commit 10d5417f9d8c1503394c8bca0f97c772f02f808f Merge: e2145ba ab22bd1 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Apr 2 19:12:25 2018 -0400 Merge remote-tracking branch 'filippo/master' dir-spec.txt | 37 +++++++++++++------------------------ rend-spec-v3.txt | 18 ++++++++++++++---- 2 files changed, 27 insertions(+), 28 deletions(-)

1 0

[translation/tor-launcher-properties_completed] Update translations for tor-launcher-properties_completed
by translation＠torproject.org 02 Apr '18

02 Apr '18

commit 0c72655aa909b8f9aece450ef2be0fe85d2796b6 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Apr 2 22:46:22 2018 +0000 Update translations for tor-launcher-properties_completed --- pt_BR/torlauncher.properties | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pt_BR/torlauncher.properties b/pt_BR/torlauncher.properties index afdcf8ccb..21d01062d 100644 --- a/pt_BR/torlauncher.properties +++ b/pt_BR/torlauncher.properties @@ -32,8 +32,8 @@ torlauncher.error_bridge_bad_default_type=Entre as pontes fornecidas que têm o torlauncher.bridge_suffix.meek-amazon=(funciona na China) torlauncher.bridge_suffix.meek-azure=(funciona na China) -torlauncher.request_a_bridge=Solicitar uma Ponte... -torlauncher.request_a_new_bridge=Solicitar uma Nova Ponte +torlauncher.request_a_bridge=Solicitar uma ponte... +torlauncher.request_a_new_bridge=Solicitar uma nova ponte torlauncher.contacting_bridgedb=Entrando em contato com BridgeDB. Por favor, aguarde. torlauncher.captcha_prompt=Resolva o CAPTCHA para solicitar uma ponte. torlauncher.bad_captcha_solution=A solução não está correta. Por favor, tente novamente.

1 0

[translation/tor-launcher-properties] Update translations for tor-launcher-properties
by translation＠torproject.org 02 Apr '18

02 Apr '18

commit f88e80162e6efa9a5337f13f000d38949b204c8d Author: Translation commit bot <translation(a)torproject.org> Date: Mon Apr 2 22:46:16 2018 +0000 Update translations for tor-launcher-properties --- pt_BR/torlauncher.properties | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pt_BR/torlauncher.properties b/pt_BR/torlauncher.properties index afdcf8ccb..21d01062d 100644 --- a/pt_BR/torlauncher.properties +++ b/pt_BR/torlauncher.properties @@ -32,8 +32,8 @@ torlauncher.error_bridge_bad_default_type=Entre as pontes fornecidas que têm o torlauncher.bridge_suffix.meek-amazon=(funciona na China) torlauncher.bridge_suffix.meek-azure=(funciona na China) -torlauncher.request_a_bridge=Solicitar uma Ponte... -torlauncher.request_a_new_bridge=Solicitar uma Nova Ponte +torlauncher.request_a_bridge=Solicitar uma ponte... +torlauncher.request_a_new_bridge=Solicitar uma nova ponte torlauncher.contacting_bridgedb=Entrando em contato com BridgeDB. Por favor, aguarde. torlauncher.captcha_prompt=Resolva o CAPTCHA para solicitar uma ponte. torlauncher.bad_captcha_solution=A solução não está correta. Por favor, tente novamente.

1 0

[torbirdy/master] Release version 0.2.4
by sukhbir＠torproject.org 02 Apr '18

02 Apr '18

commit a99de97022ceb3c575b14ea355f4ae3f86acb04d Author: Sukhbir Singh <sukhbir(a)torproject.org> Date: Mon Apr 2 16:31:59 2018 -0400 Release version 0.2.4 --- ChangeLog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 77d8ce6..0f773d3 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,4 +1,4 @@ -0.2.4, +0.2.4, 02 April 2018 * Bug 22484: TB 52+ leaks installed dictionary * Bug 22944: Disable fetching site icons * Bug 23148: Invalid GPG keyserver options in Enigmail

1 0

[nyx/master] Python3 stacktrace when dates are on a year boundary
by atagar＠torproject.org 02 Apr '18

02 Apr '18

commit f2bbbf74e144a635738e122631cf02c855c1246e Author: Damian Johnson <atagar(a)torproject.org> Date: Mon Apr 2 11:35:08 2018 -0700 Python3 stacktrace when dates are on a year boundary Oops, python3 compatibility issue... https://trac.torproject.org/projects/tor/ticket/24820 >>> import time >>> time.mktime(list(time.strptime('2017', '%Y'))) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: Tuple or struct_time argument required As above, this needs to be swapped to a tuple. I'm a tad tempted to simply subtract 31536000 (the number of seconds in a year) from the unix timestamp instead, but on reflection there's leap years, leap seconds, and god knows what else so... meh. --- nyx/log.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nyx/log.py b/nyx/log.py index 08a4878..37db680 100644 --- a/nyx/log.py +++ b/nyx/log.py @@ -494,7 +494,7 @@ def read_tor_log(path, read_limit = None): if timestamp > time.time(): # log entry is from before a year boundary timestamp_comp[0] -= 1 - timestamp = int(time.mktime(timestamp_comp)) + timestamp = int(time.mktime(tuple(timestamp_comp))) except ValueError: raise ValueError("Log located at %s has a timestamp we don't recognize: %s" % (path, ' '.join(line_comp[:3])))

1 0

[webwml/master] Update OpenBSD instruction in download-easy
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 58a458b1370d641aea493e1fced5d4aeb9ee4352 Author: hiro <hiro(a)torproject.org> Date: Mon Apr 2 19:51:23 2018 +0200 Update OpenBSD instruction in download-easy --- download/en/download-easy.wml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/download/en/download-easy.wml b/download/en/download-easy.wml index 62d9d205..3fd71967 100644 --- a/download/en/download-easy.wml +++ b/download/en/download-easy.wml @@ -131,6 +131,11 @@ <pre>pkg_add tor-browser</pre> + Sometimes the most recent version of Tor Browser on OpenBSD is behind the current release. The available version of TB on OpenBSD should be checked with: + + <pre>pkg_info -Q tor-browser</pre> + + If provided version is not the current Tor Browser version, it is not recommended. To install the Tor Browser port from an updated ports tree, run:

1 0

[webwml/master] Provide a note regarding debian Tor LTS
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit d0fc61a229713520207ad6a04c806a24b228411a Author: hiro <hiro(a)torproject.org> Date: Mon Apr 2 19:42:01 2018 +0200 Provide a note regarding debian Tor LTS --- docs/en/debian.wml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/en/debian.wml b/docs/en/debian.wml index b420a0ad..22cc7c53 100644 --- a/docs/en/debian.wml +++ b/docs/en/debian.wml @@ -25,10 +25,10 @@ If you're using Debian, just run as root. - -Note that this might not always give you the latest stable Tor version, but -you will receive important security fixes. To make sure that you're running -the latest stable version of Tor, see option two below. +Debian provides the <a href="https://packages.debian.org/stretch/tor">LTS</a> +version of Tor. Note that this might not always give you the latest stable +Tor version, but you will receive important security fixes. To make sure +that you're running the latest stable version of Tor, see option two below.

1 0