October 2020 - tor-commits - lists.torproject.org

[torspec/master] Update dirspec to reflect REASONABLY_LIVE_TIME.
by nickm＠torproject.org 13 Oct '20

13 Oct '20

commit b92dd338887ac023da4b5d1aa27b7b3c8ad552bd Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 17 13:31:42 2020 -0400 Update dirspec to reflect REASONABLY_LIVE_TIME. --- dir-spec.txt | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index 47a4ee7..6b0f438 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -362,7 +362,10 @@ (See note above: clients guess that the next consensus's FU will be two intervals after the current VA.) - VU: The consensus is no longer valid. + VU: The consensus is no longer valid; clients should continue to try to + download a new consensus if they have not done so already. + + VU + 24 hours: Clients will no longer use the consensus at all. VoteSeconds and DistSeconds MUST each be at least 20 seconds; FU-VA and VU-FU MUST each be at least 5 minutes. @@ -1770,10 +1773,14 @@ [Exactly once.] - The end of the Interval for this vote. After this time, the - consensus produced by this vote should not be used. See section 1.4 + The end of the Interval for this vote. After this time, all + clients should try to find a more recent consensus. See section 1.4 for voting timeline information. + In practice, clients continue to use the consensus for up to 24 hours + after it is no longer valid, if no more recent consensus can be + downloaded. + "voting-delay" SP VoteSeconds SP DistSeconds NL [Exactly once.]

1 0

[torspec/master] Clarify ed25519 signatures on routerdescs.
by nickm＠torproject.org 13 Oct '20

13 Oct '20

commit 01122c5bd7d2f0fbb45991dcdddede30a358130f Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 17 10:48:45 2020 -0400 Clarify ed25519 signatures on routerdescs. --- dir-spec.txt | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index 2314974..74493ad 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -627,12 +627,13 @@ It MUST be the next-to-last element in the descriptor, appearing immediately before the RSA signature. It MUST contain an Ed25519 - signature of a SHA256 digest of the entire document, from the - first character up to and including the first space after the - "router-sig-ed25519" string, prefixed with the string "Tor - router descriptor signature v1". Its format is: + signature of a SHA256 digest of the entire document. This digest is + taken from the first character up to and including the first space + after the "router-sig-ed25519" string. Before computing the digest, + the string "Tor router descriptor signature v1" is prefixed to the + document. - The signature is encoded in Base64 with terminating =s removed. + The signature is encoded in Base64, with terminating =s removed. The signing key in the identity-ed25519 certificate MUST be the one used to sign the document.

1 0

[torspec/master] dir-spec: Correct description for keyword, beginline, endline.
by nickm＠torproject.org 13 Oct '20

13 Oct '20

commit b5ab5cd4a9a90324727c961e53e39d703d7ac4c9 Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 17 10:45:10 2020 -0400 dir-spec: Correct description for keyword, beginline, endline. A keyword may not begin with '-'. Otherwise, "-----BEGIN" would be a keyword, and the grammar would be ambiguous. A beginline or endline may have multiple words in its tag. --- dir-spec.txt | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index 7ae5acd..2314974 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -200,7 +200,8 @@ Items. Every Item begins with a KeywordLine, followed by zero or more Objects. A KeywordLine begins with a Keyword, optionally followed by whitespace and more non-newline characters, and ends with a newline. A - Keyword is a sequence of one or more characters in the set [A-Za-z0-9-]. + Keyword is a sequence of one or more characters in the set [A-Za-z0-9-], + but may not start with -. An Object is a block of encoded data in pseudo-Privacy-Enhanced-Mail (PEM) style format: that is, lines of encoded data MAY be wrapped by inserting an ascii linefeed ("LF", also called newline, or "NL" here) character @@ -214,13 +215,14 @@ Document ::= (Item | NL)+ Item ::= KeywordLine Object* KeywordLine ::= Keyword NL | Keyword WS ArgumentChar+ NL - Keyword = KeywordChar+ - KeywordChar ::= 'A' ... 'Z' | 'a' ... 'z' | '0' ... '9' | '-' + Keyword = KeywordStart KeywordChar* + KeywordStart ::= 'A' ... 'Z' | 'a' ... 'z' | '0' ... '9' + KeywordChar ::= KeywordStart | '-' ArgumentChar ::= any printing ASCII character except NL. WS = (SP | TAB)+ Object ::= BeginLine Base64-encoded-data EndLine - BeginLine ::= "-----BEGIN " Keyword "-----" NL - EndLine ::= "-----END " Keyword "-----" NL + BeginLine ::= "-----BEGIN " Keyword (" " Keyword)* "-----" NL + EndLine ::= "-----END " Keyword (" " Keyword)* "-----" NL A Keyword may not be "-----BEGIN".

1 0

[torspec/master] Clarify routerdesc expiration.
by nickm＠torproject.org 13 Oct '20

13 Oct '20

commit c2e507b42a64b554db5936f481e9b5ca54ef13c7 Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 17 10:59:09 2020 -0400 Clarify routerdesc expiration. --- dir-spec.txt | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index 74493ad..ac0cc41 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -3789,12 +3789,11 @@ failure count. Clients retain the most recent descriptor they have downloaded for each - router so long as it is not too old (currently, 48 hours), OR so long as - no better descriptor has been downloaded for the same router. - - [Versions of Tor before 0.1.2.3-alpha would discard descriptors simply for - being published too far in the past.] [The code seems to discard - descriptors in all cases after they're 5 days old. True? -RD] + router so long as it is listed in the consensus. If it is not listed, + they keep it so long as it is not too old (currently, ROUTER_MAX_AGE=48 + hours) and no better router descriptor has been downloaded for the same + relay. Caches retain descriptors until they are at least + OLD_ROUTER_DESC_MAX_AGE=5 days old. Clients which chose to download the microdescriptor consensus instead of the general consensus must download the referenced microdescriptors

1 0

[torspec/master] remove reference to a missing "download all microdescs" feature.
by nickm＠torproject.org 13 Oct '20

13 Oct '20

commit 61b5da1756ad78acbc5ee033b8d4c4579649187b Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 17 10:59:48 2020 -0400 remove reference to a missing "download all microdescs" feature. --- dir-spec.txt | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index ac0cc41..47a4ee7 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -3803,13 +3803,8 @@ need to fetch the microdescriptors that have changed. When a client gets a new microdescriptor consensus, it looks to see if - there are any microdescriptors it needs to learn. If it needs to learn - more than half of the microdescriptors, it requests 'all', else it - requests only the missing ones. Clients MAY try to determine whether - the upload bandwidth for listing the microdescriptors they want is more - or less than the download bandwidth for the microdescriptors they do - not want. - [XXX The 'all' URL is not implemented yet. -KL] + there are any microdescriptors it needs to learn, and launches a request + for them. Clients maintain a cache of microdescriptors along with metadata like when it was last referenced by a consensus, and which identity key

1 0

[torspec/master] Merge remote-tracking branch 'tor-gitlab/mr/6'
by nickm＠torproject.org 13 Oct '20

13 Oct '20

commit 111839f176890ab37b28b00b5c05f03b46874098 Merge: df41296 b92dd33 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Oct 13 14:54:14 2020 -0400 Merge remote-tracking branch 'tor-gitlab/mr/6' dir-spec.txt | 56 ++++++++++++++++++++++++++++++-------------------------- 1 file changed, 30 insertions(+), 26 deletions(-)

1 0

[manual/master] one commit on issue-patch
by gus＠torproject.org 13 Oct '20

13 Oct '20

commit d1ab844f8892491083cf0d1638f8212dd959251a Author: Kim Le <kle2(a)student.unimelb.edu.au> Date: Fri Oct 9 11:05:43 2020 +1100 one commit on issue-patch --- content/mobile-tor/contents.lr | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/content/mobile-tor/contents.lr b/content/mobile-tor/contents.lr index f5eb373..5ccbceb 100644 --- a/content/mobile-tor/contents.lr +++ b/content/mobile-tor/contents.lr @@ -67,7 +67,7 @@ When you run Tor Browser for the first time, you will see the option to connect <img style="max-width:300px" class="col-md-6" src="../../static/images/android-connect.png" alt="Connect to Tor Browser for Android"> In most cases, choosing "Connect" will allow you to connect to the Tor network without any further configuration. -Once clicked, changing sentences will appear at the bottom of the screen, indicating Tor’s connection progress. +Once tapped, changing sentences will appear at the bottom of the screen, indicating Tor’s connection progress. If you are on a relatively fast connection, but this text seems to get stuck at a certain point, see the [Troubleshooting](../troubleshooting) page for help solving the problem. #### Configure @@ -77,7 +77,7 @@ If you are on a relatively fast connection, but this text seems to get stuck at If you know that your connection is censored, you should select the settings icon. Tor Browser will take you through a series of configuration options. The first screen asks if access to the Tor network is blocked or censored on your connection. -If you know your connection is censored, or you have tried and failed to connect to the Tor network and no other solutions have worked, click the switch. +If you know your connection is censored, or you have tried and failed to connect to the Tor network and no other solutions have worked, tap the switch. You will then be taken to the [Circumvention](../circumvention) screen to configure a pluggable transport. ### CIRCUMVENTION @@ -85,8 +85,8 @@ You will then be taken to the [Circumvention](../circumvention) screen to config Bridge relays are Tor relays that are not listed in the public Tor directory. Bridges are useful for Tor users under oppressive regimes, and for people who want an extra layer of security because they're worried somebody will recognize that they are contacting a public Tor relay IP address. -To use a pluggable transport, click on the settings icon when starting Tor Browser for the first time. -The first screen asks if access to the Tor network is censored on your connection. Click on the switch to toggle it. +To use a pluggable transport, tap on the settings icon when starting Tor Browser for the first time. +The first screen asks if access to the Tor network is censored on your connection. Tap on the switch to toggle it. <img style="max-width:300px" class="col-md-6" src="../../static/images/android-censored.png" alt="Censored internet on Tor Browser for Android"> @@ -111,7 +111,7 @@ If you choose the "Provide a Bridge I know" option, then you have to enter a [br <img style="max-width:300px" class="col-md-6" src="../../static/images/android-new-identity.png" alt="New Identity on Tor Browser for Android"> When Tor Browser is running, you would see so in your phone's notification panel along with the button "NEW IDENTITY". -Clicking on this button will provide you with a new identity. +Tapping on this button will provide you with a new identity. Unlike in Tor Browser for Desktop, the "NEW IDENTITY" button in Tor Browser for Android does not prevent your subsequent browser activity from being linkable to what you were doing before. Selecting it will only change your Tor circuit. @@ -139,15 +139,15 @@ This method assumes that you have either Google Play or F-droid installed on you <img style="max-width:300px" class="col-md-6" src="../../static/images/android-update-google-play.png" alt="Updating Tor Browser for Android on Google Play"> -Click on the hamburger menu next to the search bar and navigate to "My apps & games" > "Updates". -If you find Tor Browser on the list of apps which need updating, select it and click the "Update" button. +Tap on the hamburger menu next to the search bar and navigate to "My apps & games" > "Updates". +If you find Tor Browser on the list of apps which need updating, select it and tap the "Update" button. ##### F-Droid <img style="max-width:300px" class="col-md-6" src="../../static/images/android-update-f-droid.png" alt="Updating Tor Browser for Android on F-droid"> -Click on "Settings", then go to "Manage installed apps". -On the next screen, select Tor Browser and finally click on the "Update" button. +Tap on "Settings", then go to "Manage installed apps". +On the next screen, select Tor Browser and finally tap on the "Update" button. #### Updating Tor Browser for Android manually @@ -156,7 +156,7 @@ Visit the [Tor Project website](https://www.torproject.org/download/#android) an In most cases, this latest version of Tor Browser will install over the older version, thereby upgrading the browser. If doing this fails to update the browser, you may have to uninstall Tor Browser before reinstalling it. With Tor Browser closed, remove it from your system by uninstalling it using your device's settings. -Depending on your mobile device's brand, navigate to Settings > Apps, then select Tor Browser and click on the "Uninstall" button. Afterwards,download the latest Tor Browser release and install it. +Depending on your mobile device's brand, navigate to Settings > Apps, then select Tor Browser and tap on the "Uninstall" button. Afterwards,download the latest Tor Browser release and install it. ### UNINSTALLING @@ -166,21 +166,21 @@ Tor Browser for Android can be uninstalled directly from F-droid, Google Play or <img style="max-width:300px" class="col-md-6" src="../../static/images/android-uninstall-google-play.png" alt="Uninstalling Tor Browser for Android on Google Play"> -Click on the hamburger menu next to the search bar and navigate to "My apps & games" > "Installed". +Tap on the hamburger menu next to the search bar and navigate to "My apps & games" > "Installed". Select Tor Browser from the list of installed apps, then press the "Uninstall" button. #### F-Droid <img style="max-width:300px" class="col-md-6" src="../../static/images/android-uninstall-f-droid.png" alt="Uninstalling Tor Browser for Android on F-droid"> -Click on "Settings", then go to "Manage installed apps". -On the next screen, select Tor Browser and finally click on the "Uninstall" button. +Tap on "Settings", then go to "Manage installed apps". +On the next screen, select Tor Browser and finally tap on the "Uninstall" button. #### Mobile device app settings <img style="max-width:300px" class="col-md-6" src="../../static/images/android-uninstall-device-settings.png" alt="Uninstalling Tor Browser for Android using device app settings"> -Depending on your mobile device's brand, navigate to Settings > Apps, then select Tor Browser and click on the "Uninstall" button. +Depending on your mobile device's brand, navigate to Settings > Apps, then select Tor Browser and tap on the "Uninstall" button. ### KNOWN ISSUES

1 0

[manual/master] Merge branch 'tap-tor-browser'
by gus＠torproject.org 13 Oct '20

13 Oct '20

commit 97fb8631db2c1c71d224429f0c076dec95b36fd2 Merge: f3988aa d1ab844 Author: gus <gus(a)torproject.org> Date: Tue Oct 13 14:48:12 2020 -0400 Merge branch 'tap-tor-browser' content/mobile-tor/contents.lr | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-)

1 0

[donate-static/master] Removed .htaccess-membership and lego
by peterh＠torproject.org 13 Oct '20

13 Oct '20

commit 9b4883d310ce9b312db0c009f8164b75f0d4cebc Author: Peter Haight <peterh(a)giantrabbit.com> Date: Tue Oct 13 11:30:30 2020 -0700 Removed .htaccess-membership and lego .htaccess-membership was only necessary on the tpo site which this site was cloned from. I rebased the lego branch, so this needed to be updated. --- .htaccess-membership | 4 ---- lego | 2 +- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/.htaccess-membership b/.htaccess-membership deleted file mode 100644 index 64537967..00000000 --- a/.htaccess-membership +++ /dev/null @@ -1,4 +0,0 @@ -AuthType Basic - AuthName "Secure Content" - AuthUserFile .htpasswd - require valid-user diff --git a/lego b/lego index 541634e9..600dcb3e 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 541634e97871df03dcfe17c4fe34ecd0dba16849 +Subproject commit 600dcb3e259b56108a371bdda7871ac52e90ff6c

1 0

[donate-static/master] Updated to latest lego
by peterh＠torproject.org 13 Oct '20

13 Oct '20

commit 4f0a613c7c8c441f70b7453b8c84a1514c89be0d Author: Peter Haight <peterh(a)giantrabbit.com> Date: Tue Oct 13 11:14:04 2020 -0700 Updated to latest lego This new lego has the packages installed locally. --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 4d01aa3d..541634e9 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 4d01aa3d1cb279ae1b484ae2da707591a841b1f6 +Subproject commit 541634e97871df03dcfe17c4fe34ecd0dba16849

1 0