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

[tor/master] Added a section for Dormant mode options
by nickm＠torproject.org 10 Feb '20

10 Feb '20

commit 05adecf2115fe8e95a888a6ad5cdc0322181a332 Author: swati <swati.thacker(a)oracle.com> Date: Thu Feb 6 21:33:58 2020 +0530 Added a section for Dormant mode options --- doc/tor.1.txt | 70 +++++++++++++++++++++++++++++++++-------------------------- 1 file changed, 39 insertions(+), 31 deletions(-) diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 43a014c60..73f9dd385 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -1138,31 +1138,6 @@ The following options are useful only for clients (that is, if addresses/ports. See SocksPort for an explanation of isolation flags. (Default: 0) -[[DormantCanceledByStartup]] **DormantCanceledByStartup** **0**|**1**:: - By default, Tor starts in active mode if it was active the last time - it was shut down, and in dormant mode if it was dormant. But if - this option is true, Tor treats every startup event as user - activity, and Tor will never start in Dormant mode, even if it has - been unused for a long time on previous runs. (Default: 0) - + - Note: Packagers and application developers should change the value of - this option only with great caution: it has the potential to - create spurious traffic on the network. This option should only - be used if Tor is started by an affirmative user activity (like - clicking on an applcation or running a command), and not if Tor - is launched for some other reason (for example, by a startup - process, or by an application that launches itself on every login.) - -[[DormantOnFirstStartup]] **DormantOnFirstStartup** **0**|**1**:: - If true, then the first time Tor starts up with a fresh DataDirectory, - it starts in dormant mode, and takes no actions until the user has made - a request. (This mode is recommended if installing a Tor client for a - user who might not actually use it.) If false, Tor bootstraps the first - time it is started, whether it sees a user request or not. - + - After the first time Tor starts, it begins in dormant mode if it was - dormant before, and not otherwise. (Default: 0) - [[DownloadExtraInfo]] **DownloadExtraInfo** **0**|**1**:: If true, Tor downloads and caches "extra-info" documents. These documents contain information about servers other than the information in their @@ -1757,7 +1732,7 @@ The following options are useful only for clients (that is, if used IP. For local use, no change to the default VirtualAddrNetwork setting is needed. -== TIMEOUT OPTIONS +== CIRCUIT TIMEOUT OPTIONS // These options are in alphabetical order, with exceptions as noted. // Please keep them that way! @@ -1791,6 +1766,34 @@ The following options are useful for configuring timeouts: If your network is particularly slow, you might want to set this to a number like 60. (Default: 0) +[[SocksTimeout]] **SocksTimeout** __NUM__:: + Let a socks connection wait NUM seconds handshaking, and NUM seconds + unattached waiting for an appropriate circuit, before we fail it. (Default: + 2 minutes) + +== DORMANT MODE OPTIONS + +// These options are in alphabetical order, with exceptions as noted. +// Please keep them that way! + +The following options can be used to configure Tor +when the client is running in dormant mode: + +[[DormantCanceledByStartup]] **DormantCanceledByStartup** **0**|**1**:: + By default, Tor starts in active mode if it was active the last time + it was shut down, and in dormant mode if it was dormant. But if + this option is true, Tor treats every startup event as user + activity, and Tor will never start in Dormant mode, even if it has + been unused for a long time on previous runs. (Default: 0) + + + Note: Packagers and application developers should change the value of + this option only with great caution: it has the potential to + create spurious traffic on the network. This option should only + be used if Tor is started by an affirmative user activity (like + clicking on an applcation or running a command), and not if Tor + is launched for some other reason (for example, by a startup + process, or by an application that launches itself on every login.) + [[DormantClientTimeout]] **DormantClientTimeout** __N__ **minutes**|**hours**|**days**|**weeks**:: If Tor spends this much time without any client activity, enter a dormant state where automatic circuits are not built, and @@ -1798,16 +1801,21 @@ The following options are useful for configuring timeouts: Does not affect servers or onion services. Must be at least 10 minutes. (Default: 24 hours) +[[DormantOnFirstStartup]] **DormantOnFirstStartup** **0**|**1**:: + If true, then the first time Tor starts up with a fresh DataDirectory, + it starts in dormant mode, and takes no actions until the user has made + a request. (This mode is recommended if installing a Tor client for a + user who might not actually use it.) If false, Tor bootstraps the first + time it is started, whether it sees a user request or not. + + + After the first time Tor starts, it begins in dormant mode if it was + dormant before, and not otherwise. (Default: 0) + [[DormantTimeoutDisabledByIdleStreams]] **DormantTimeoutDisabledByIdleStreams** **0**|**1**:: If true, then any open client stream (even one not reading or writing) counts as client activity for the purpose of DormantClientTimeout. If false, then only network activity counts. (Default: 1) -[[SocksTimeout]] **SocksTimeout** __NUM__:: - Let a socks connection wait NUM seconds handshaking, and NUM seconds - unattached waiting for an appropriate circuit, before we fail it. (Default: - 2 minutes) - == NODE SELECTION OPTIONS // These options are in alphabetical order, with exceptions as noted.

1 0

[tor/master] Added the NodeFamily option to Node Selection Options section
by nickm＠torproject.org 10 Feb '20

10 Feb '20

commit 1b65024ae21ba5ad19107121be76327d6ffbc9c3 Author: swati <swati.thacker(a)oracle.com> Date: Wed Feb 5 23:13:41 2020 +0530 Added the NodeFamily option to Node Selection Options section --- doc/tor.1.txt | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 77423f804..43a014c60 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -1298,16 +1298,6 @@ The following options are useful only for clients (that is, if Every NUM seconds consider whether to build a new circuit. (Default: 30 seconds) -[[NodeFamily]] **NodeFamily** __node__,__node__,__...__:: - The Tor servers, defined by their identity fingerprints, - constitute a "family" of similar or co-administered servers, so never use - any two of them in the same circuit. Defining a NodeFamily is only needed - when a server doesn't list the family itself (with MyFamily). This option - can be used multiple times; each instance defines a separate family. In - addition to nodes, you can also list IP address and ranges and country - codes in {curly braces}. See the **ExcludeNodes** option for more - information on how to specify nodes. - [[OptimisticData]] **OptimisticData** **0**|**1**|**auto**:: When this option is set, and Tor is using an exit node that supports the feature, it will try optimistically to send data to the exit node @@ -1824,9 +1814,9 @@ The following options are useful for configuring timeouts: // Please keep them that way! The following options restrict the nodes that a tor client -(or onion service) can use while building a circuit: - -These options can weaken your anonymity by making your client behavior different from other Tor clients: +(or onion service) can use while building a circuit. +These options can weaken your anonymity by making your client behavior +different from other Tor clients: [[EntryNodes]] **EntryNodes** __node__,__node__,__...__:: A list of identity fingerprints and country codes of nodes @@ -2036,6 +2026,16 @@ These options can weaken your anonymity by making your client behavior different MiddleNodes and ExcludeNodes is treated as excluded. See the **ExcludeNodes** option for more information on how to specify nodes. +[[NodeFamily]] **NodeFamily** __node__,__node__,__...__:: + The Tor servers, defined by their identity fingerprints, + constitute a "family" of similar or co-administered servers, so never use + any two of them in the same circuit. Defining a NodeFamily is only needed + when a server doesn't list the family itself (with MyFamily). This option + can be used multiple times; each instance defines a separate family. In + addition to nodes, you can also list IP address and ranges and country + codes in {curly braces}. See the **ExcludeNodes** option for more + information on how to specify nodes. + [[StrictNodes]] **StrictNodes** **0**|**1**:: If StrictNodes is set to 1, Tor will treat solely the ExcludeNodes option as a requirement to follow for all the circuits you generate, even if

1 0

[tor/master] Updated the introductory text and titles of Timeout and Node selection options
by nickm＠torproject.org 10 Feb '20

10 Feb '20

commit d75d763155335f29ae75530d524af8f2e81e425e Author: swati <swati.thacker(a)oracle.com> Date: Wed Feb 5 00:28:27 2020 +0530 Updated the introductory text and titles of Timeout and Node selection options --- doc/tor.1.txt | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/doc/tor.1.txt b/doc/tor.1.txt index dde9ffd54..77423f804 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -1769,6 +1769,9 @@ The following options are useful only for clients (that is, if == TIMEOUT OPTIONS +// These options are in alphabetical order, with exceptions as noted. +// Please keep them that way! + The following options are useful for configuring timeouts: [[CircuitsAvailableTimeout]] **CircuitsAvailableTimeout** __NUM__:: @@ -1815,9 +1818,15 @@ The following options are useful for configuring timeouts: unattached waiting for an appropriate circuit, before we fail it. (Default: 2 minutes) -== ADVANCED OPTIONS +== NODE SELECTION OPTIONS + +// These options are in alphabetical order, with exceptions as noted. +// Please keep them that way! + +The following options restrict the nodes that a tor client +(or onion service) can use while building a circuit: -The following options include Tor nodes: +These options can weaken your anonymity by making your client behavior different from other Tor clients: [[EntryNodes]] **EntryNodes** __node__,__node__,__...__:: A list of identity fingerprints and country codes of nodes

1 0

[tor/master] Merge remote-tracking branch 'tor-github/pr/1711'
by nickm＠torproject.org 10 Feb '20

10 Feb '20

commit 05a05773f284dd870282e05ae918d74300ddbc19 Merge: 5e6021bda cb757b30a Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Feb 10 10:23:50 2020 -0500 Merge remote-tracking branch 'tor-github/pr/1711' changes/ticket32928 | 7 + doc/tor.1.txt | 628 +++++++++++++++++++++++++++------------------------- 2 files changed, 333 insertions(+), 302 deletions(-)

1 0

[tor/master] changes file for tickets 32928, 32929
by nickm＠torproject.org 10 Feb '20

10 Feb '20

commit cb757b30a208f027ca36d7acceade61faf348009 Author: Taylor Yu <catalyst(a)torproject.org> Date: Fri Feb 7 12:54:55 2020 -0600 changes file for tickets 32928, 32929 --- changes/ticket32928 | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/changes/ticket32928 b/changes/ticket32928 new file mode 100644 index 000000000..f7739e928 --- /dev/null +++ b/changes/ticket32928 @@ -0,0 +1,7 @@ + o Documentation (manpage): + - Split Circuit Timeout options into their own section of the tor + manpage. Closes ticket 32928. Work by Swati Thacker as part of + Google Season of Docs. + - Split Node selection options into their own section of the tor + manpage. Closes ticket 32929. Work by Swati Thacker as part of + Google Season of Docs.

1 0

[tpo/master] Update lego
by hiro＠torproject.org 10 Feb '20

10 Feb '20

commit 86bc2f555cec76be39573cf47a320d5e4fc12048 Author: hiro <hiro(a)torproject.org> Date: Mon Feb 10 15:46:30 2020 +0100 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index e058aee..e9dd081 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit e058aee7e40a97434ddbffbb1d5ffe18a610076b +Subproject commit e9dd081027132aa21f6abd74be708323ff3b9180

1 0

[tpo/master] Add new job post
by hiro＠torproject.org 10 Feb '20

10 Feb '20

commit f72483b4bd122a16e0c20b1619ab3ece50442cd1 Author: hiro <hiro(a)torproject.org> Date: Mon Feb 10 15:45:43 2020 +0100 Add new job post --- content/about/jobs/executive-assistant/contents.lr | 83 ++++++++++++++++++++++ 1 file changed, 83 insertions(+) diff --git a/content/about/jobs/executive-assistant/contents.lr b/content/about/jobs/executive-assistant/contents.lr new file mode 100644 index 0000000..21772ed --- /dev/null +++ b/content/about/jobs/executive-assistant/contents.lr @@ -0,0 +1,83 @@ +_model: job +--- +_template: about.html +--- +section: about +--- +section_id: about +--- +active: False +--- +title: Backend Engineer for OONI +--- +color: primary +--- +summary: +The Tor Project, Inc. is looking for a dedicated backend engineer to work on OONI (https://ooni.torproject.org/) OONI is the Open Observatory of Network Interference: a free and open source software, global observation network for detecting censorship, surveillance, and traffic manipulation on the internet. + +You will be working to improve OONI's data processing pipeline and other backend components responsible for recording measurements collected from our growing global user network. You will also be tasked with improving our network measurement methodologies and data analysis heuristics to increase the accuracy of our experiments. + +--- +description: + +## Backend Engineer for OONI +*January 31, 2018* + +The Tor Project, Inc. is looking for a dedicated backend engineer to work on OONI (https://ooni.torproject.org/) OONI is the Open Observatory of Network Interference: a free and open source software, global observation network for detecting censorship, surveillance, and traffic manipulation on the internet. + +You will be working to improve OONI's data processing pipeline and other backend components responsible for recording measurements collected from our growing global user network. You will also be tasked with improving our network measurement methodologies and data analysis heuristics to increase the accuracy of our experiments. + +This is a full-time 12-month contract position, starting ASAP (no later than mid-May 2019); contract may be extended. + +The OONI team is based in Europe. However, this position may be performed remotely. + +Here are some of our code repositories: + + https://github.com/ooni/api + https://github.com/ooni/pipeline + https://github.com/ooni/orchestra + https://github.com/ooni/collector + https://github.com/ooni/sysadmin + +**Required skills and qualifications:** + + - Extensive experience in python or golang. + - Comfortable working remotely. + - Self-directed, self-disciplined, but good at working and communicating with a team. + - Have experience and be comfortable with others reviewing your code and design; have experience and be comfortable reviewing others' code. + - Experience documenting and designing protocols. + - Be comfortable with transparency! + +**Preferred qualifications:** + + Experience designing, implementing, and maintaining scalable complex network applications. + Working experience with data processing pipelines. + Possess the confidence to refactor code and write unit-tests. + Familiarity with the challenges of developing and scaling data processing pipelines. + Familiarity with the network measurement field. + Experience with open-source software development, including working with distributed teams across different time-zones containing employees and volunteers of differing skill levels. + Basic familiarity with distributed version control systems. + Contributed significant chunks of code to multiple open-source projects in the past. + Be passionate about internet freedom and interested in contributing to it in a concrete way! + +**Other notes:** + +Academic degrees are great but not required if you have the right experience. + +You should be very good at working remotely at communicating with the team on a daily basis via Slack, IRC, instant messaging, email, and issue trackers. + +Salary negotiable. + +**How to apply:** + +Please email a *PDF* of your resume/CV, and a cover letter explaining how your qualifications and experience meet the requirements of this job description. Please include the reasons why you want to work on OONI. Please also include link to one or several code samples (of which you are authorized to share), and also your GitHub or GitLab profile, and three professional references. + +Email should be sent to jobs at openobservatory dot org with "OONI Backend Engineer" in the subject line. + +**About the project:** + +The Open Observatory of Network Interference (OONI) is a free software project under the Tor Project. OONI collects and processes network measurements with the aim of detecting network interferences, such as censorship, surveillance, and traffic manipulation. Since late 2012, OONI has collected millions of measurements across more than 90 countries around the world. + +The Tor Project, Inc., is a 501(c)(3) organization headquartered in Seattle with paid staff and contractors of around 45 engineers and operational support people, plus many volunteers all over the world. Tor develops free and open source software for privacy and freedom online, protecting people from tracking, surveillance, and censorship. The Tor Project is funded in part by government grants and contracts, as well as by individual, foundation, and corporate donations. The Tor Project's mission is to advance human rights and freedoms by creating and deploying free and open source anonymity and privacy technologies, support their unrestricted availability and use, and further their scientific and popular understanding. + +The Tor Project, Inc., is an equal opportunity, affirmative action employer.

1 0

[translation/donatepages-messagespot] https://gitweb.torproject.org/translation.git/commit/?h=donatepages-messagespot
by translation＠torproject.org 10 Feb '20

10 Feb '20

commit 76aab61cb256b19400b8845d6576a49686fd1e1b Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 10 06:45:36 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=donatepages-message… --- locale/ro/LC_MESSAGES/messages.po | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/locale/ro/LC_MESSAGES/messages.po b/locale/ro/LC_MESSAGES/messages.po index b01d9598fe..16dcaacb68 100644 --- a/locale/ro/LC_MESSAGES/messages.po +++ b/locale/ro/LC_MESSAGES/messages.po @@ -6,14 +6,14 @@ # Claudiu Popescu <claudiu94(a)gmail.com>, 2018 # Vlad Stoica <vlad(a)vlads.me>, 2019 # erinm, 2019 -# eduard pintilie <eduard.pintilie(a)gmail.com>, 2019 # A C <ana(a)shiftout.net>, 2019 # k piticu <k.piticu(a)gmail.com>, 2019 # Cristina Lupu <cristina(a)cji.ro>, 2019 +# eduard pintilie <eduard.pintilie(a)gmail.com>, 2020 # msgid "" msgstr "" -"Last-Translator: Cristina Lupu <cristina(a)cji.ro>, 2019\n" +"Last-Translator: eduard pintilie <eduard.pintilie(a)gmail.com>, 2020\n" "Language-Team: Romanian (https://www.transifex.com/otf/teams/1519/ro/)\n" "Language: ro\n" "Plural-Forms: nplurals=3; plural=(n==1?0:(((n%100>19)||((n%100==0)&&(n!=0)))?2:1));\n" @@ -2887,6 +2887,11 @@ msgid "" "reliable source of funds to help us be agile in an ever-changing privacy " "landscape and we send exclusive gifts to show our appreciation!" msgstr "" +"Apărătorii Confidențialității - Defenders of Privacy - donează în fiecare " +"lună o sumă modestă - creând o sursă constantă și fiabilă de fonduri care să" +" ne ajute să fim agili într-un peisaj de confidențialitate în continuă " +"schimbare și le trimitem cadouri exclusive pentru a le arăta aprecierea " +"noastră!" #: tmp/cache_locale/66/666e9197f427d70c0743bcdae2c3e34f41f9d7acf2b2dddb2c21c21723e73d10.php:113 msgid "" @@ -2951,6 +2956,10 @@ msgid "" "summary is available upon request at The Tor Project, Inc.; 217 First Avenue" " South #4903; Seattle, WA 98194 and phone number 206-420-3136." msgstr "" +"O descriere completă și corectă a programelor noastre și rezumatul situației" +" financiare sunt disponibile la cerere la The Tor Project, Inc.; 217 First " +"Avenue South # 4903; Seattle, WA 98194 și la numărul de telefon " +"206-420-3136." #: tmp/cache_locale/17/179dc1a0f488d5bbb8c128dc5c0fb35d6240d83414df10335a1cf4031139609a.php:99 msgid "Maryland"

1 0

[translation/tbmanual-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot
by translation＠torproject.org 10 Feb '20

10 Feb '20

commit c5d6e32b52aab4ef4303747dec757061c7b2bfc4 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 10 06:19:57 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot --- contents+ro.po | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/contents+ro.po b/contents+ro.po index db5172d8a3..fdc5b8cd23 100644 --- a/contents+ro.po +++ b/contents+ro.po @@ -1538,6 +1538,8 @@ msgid "" "You can do this by increasing Tor Browser's Security Levels in the shield " "menu." msgstr "" +"Puteți face acest lucru prin creșterea nivelului de securitate al Tor " +"Browser din meniul de securitate." #: https//tb-manual.torproject.org/security-settings/ #: (content/security-settings/contents+en.lrtopic.body) @@ -1989,6 +1991,13 @@ msgid "" " displaying correctly, so Tor Browser’s default setting is to allow all " "websites to run scripts in \"Standard\" mode." msgstr "" +"Utilizatorii care vor un grad ridicat de securitate în navigarea lor web ar " +"trebui să configureze [Nivelul de securitate] (../security-settings/) al Tor" +" Browser pe „Safer” (care dezactivează JavaScript pentru site-urile non-" +"HTTPS) sau „Safest” (care face asta pentru toate site-urile web). Cu toate " +"acestea, dezactivarea JavaScript va împiedica afișarea corectă a mai multor " +"site-uri web, astfel încât setarea implicită a Tor Browser este de a permite" +" tuturor site-urilor să ruleze scripturi în modul „Standard”." #: https//tb-manual.torproject.org/plugins/ #: (content/plugins/contents+en.lrtopic.body)

1 0

[tor/master] stats: Fix a function comment typo in rephist.c
by teor＠torproject.org 10 Feb '20

10 Feb '20

commit 5e6021bdaeaf5d49cb3854a7a3d336849650ad10 Author: teor <teor(a)torproject.org> Date: Mon Feb 10 15:58:25 2020 +1000 stats: Fix a function comment typo in rephist.c Comment-only change. --- src/feature/stats/rephist.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/feature/stats/rephist.c b/src/feature/stats/rephist.c index b2817ee76..d229c755b 100644 --- a/src/feature/stats/rephist.c +++ b/src/feature/stats/rephist.c @@ -1122,7 +1122,7 @@ static bw_array_t *dir_read_array = NULL; directory protocol. */ static bw_array_t *dir_write_array = NULL; -/** Set up [dir-]read_array and [dir-]write_array, freeing them if they +/** Set up [dir_]read_array and [dir_]write_array, freeing them if they * already exist. */ static void bw_arrays_init(void)

1 0