tor-commits September 2017

tor-commits@lists.torproject.org

16 participants
2950 discussions

[webwml/staging] add android os dev job
by hiro＠torproject.org 07 Sep '17

07 Sep '17

commit 9656a69e8fe8b005eae100928c84833f894ffa25 Author: hiromipaw <hiro(a)torproject.org> Date: Fri Aug 25 12:45:52 2017 +0200 add android os dev job --- about/en/jobs-osdeveloperandroid.wml | 139 +++++++++++++++++++++++++++++++++++ 1 file changed, 139 insertions(+) diff --git a/about/en/jobs-osdeveloperandroid.wml b/about/en/jobs-osdeveloperandroid.wml new file mode 100644 index 00000000..1ef85c08 --- /dev/null +++ b/about/en/jobs-osdeveloperandroid.wml @@ -0,0 +1,139 @@ +## translation metadata +# Revision: $Revision: 25666 $ +# Translation-Priority: 3-low + +#include "head.wmi" TITLE="Tor Project: Jobs (os developer android)" CHARSET="UTF-8" +<div id="content" class="clearfix"> + <div id="breadcrumbs"> + <a href="<page index>">Home » </a> + <a href="<page about/overview>">About » </a> + <a href="<page about/jobs>">Jobs</a> + </div> + <div id="maincol"> +<h1> The Tor Project is looking for an Android OS developer!</h1> +<h2>(Posted 27 Jul 2017)</h2> + +<p> +August23, 2017 +</p> +<p> +The Tor Project is looking for an Android OS Developer! +</p> +<p> + As an Android OS Developer, your job will be to work closely with other + members of the development team to build and release a Tor Browser for + Android with functionality and build processes in parity with the desktop + browser. This is a full-time position. +</p> +<p> + Being a Tor developer includes triaging, diagnosing, and fixing bugs; + looking for and resolving mobile privacy issues; responding on short + notice to urgent security issues; and working collaboratively with + coworkers and volunteers to implement new features and mobile behavior + changes. We also need help making our code more maintainable, testable, + and mergeable by upstream. The person in this position will review other + people's code, designs, and academic research papers to make suggestions + for improvement. +</p> + +<h2>This position will also focus on the following tasks/projects:</h2> +<ul> + <li> + Design TorService API/integration with Fennec Mobile Android Java code. + </li> + <li> + Automate a continuous build process. + </li> + <li> + Make Tor Browser for Android a standalone application by porting the Orbot connection to Tor. + </li> + <li> + Create a Gradle-dependent standalone Tor Service Library for Android. + </li> + <li> + Coordinate uplifting of mobile patches. + </li> +</ul> + +<h2>Required Qualifications:</h2> +<ul> + <li> + 5+ years experience with developing and testing Java/JNI, Android APIs, and library dependencies. + </li> + <li> + Experience with process management services on Android. + </li> + <li> + Experience with Android Software Development Kit (SDK). + </li> + <li> + Experience in cross-compiling Linux/C/C++ code and libraries to mobile devices via Android Native Development Kit (NDK). + </li> + <li> + Experience using network traffic capture and monitoring tools (Wireshark, PCAP). + </li> + <li> + Test writing in Espresso, Robotum, JUnit, and/or comparable environment. + </li> + <li> + Good interpersonal and open-source collaboration skills. + </li> +</ul> + +<h2>Desired qualifications:</h2> +<ul> + <li> + Experience with reproducible builds on desktop or mobile. + </li> + <li> + User interface and usability skills (nice, but not essential for this role). + </li> + <li> + Shipped public applications with NDK features. + </li> + <li> + Experience with Rust and Go on Android. + </li> + <li> + Automated testing and continuous integration using cloud based services. + </li> + <li> + Network knowledge and/or experience; experience investigating leaks. + </li> +</ul> +<h2> +Other notes: +</h2> +<p> +Academic degrees are great, but not required if you have the right experience! +</p> +<p> +The team coordinates via IRC, email, and bug trackers. This position may be performed remotely, but we would be happy to provide a desk at our office in Seattle, Washington. We also have informal shared workspace arrangements in NYC and San Francisco. +</p> +<p> +The Tor Project, Inc., is a 501(c)(3) non-profit organization that provides the technical infrastructure for privacy protection over the Internet. With paid staff and contractors of around 30 technologists and operational support people, plus many volunteers all over the world who contribute to our work, the Tor Project is funded in part by government grants and contracts, as well as by individual, foundation, and corporate donations. We only write free and open source software, and we don't believe in software patents. +</p> +<p> +The Tor Project has a competitive benefits package, including a generous PTO policy; 14 paid holidays per year (including the week between Christmas and New Year's, when the office is closed); health, vision, dental, disability, and life insurance paid in full for employee; flexible work schedule; and occasional travel opportunities. +</p> +<p> +The Tor Project, Inc., is an equal opportunity, affirmative action employer. +</p> +<h2> +To apply: +</h2> +<p> +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, including why you want to work on Tor. Email should be sent to hr at torproject.org with "Browser Developer" in the subject line. +Link to at least one of your code samples (ideally, more than one and all of which we will presume you are authorized to disclose). No phone calls, please! +</p> + + </div> +  + <div id = "sidecol"> +#include "side.wmi" +#include "info.wmi" + </div> +  +</div> + +#include <foot.wmi>

1 0

[webwml/staging] Fix torbutton missing jquery error
by hiro＠torproject.org 07 Sep '17

07 Sep '17

commit 1b8063138301abf86c961c35417cd0bfb48b79e5 Author: hiromipaw <hiro(a)torproject.org> Date: Thu Sep 7 15:56:35 2017 +0200 Fix torbutton missing jquery error --- docs/torbutton/en/index.wml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/torbutton/en/index.wml b/docs/torbutton/en/index.wml index c8fe7a44..18f5157e 100644 --- a/docs/torbutton/en/index.wml +++ b/docs/torbutton/en/index.wml @@ -14,6 +14,8 @@ <link rel="search" type="application/opensearchdescription+xml" title="Google Canada" href="search/google-ca.xml"/> <link rel="search" type="application/opensearchdescription+xml" title="Google UK" href="search/google-uk.xml"/> <link rel="search" type="application/opensearchdescription+xml" title="Google USA" href="search/google-us.xml"/> + <script type="text/javascript" src="$(DOCROOT)/js/jquery.min.js" charset="utf-8"></script> + <script type="text/javascript" src="$(DOCROOT)/js/jquery.infieldlabel.min.js" charset="utf-8"></script> <script type="text/javascript" src="$(DOCROOT)/js/functions.min.js" charset="utf-8"></script> <h2>Torbutton</h2>

1 0

[webwml/staging] Merge branch 'master' of ssh://git-rw.torproject.org/project/web/webwml
by hiro＠torproject.org 07 Sep '17

07 Sep '17

commit 616edbb9b49fe160dd517fde066b472390548536 Merge: 1b806313 88b17d9e Author: hiromipaw <hiro(a)torproject.org> Date: Thu Sep 7 15:56:40 2017 +0200 Merge branch 'master' of ssh://git-rw.torproject.org/project/web/webwml Makefile | 2 +- include/versions.wmi | 22 +++++++++++----------- projects/torbrowser/RecommendedTBBVersions | 4 ++++ 3 files changed, 16 insertions(+), 12 deletions(-)

1 0

[webwml/staging] Add new Tor Browser version: 7.0.5
by hiro＠torproject.org 07 Sep '17

07 Sep '17

commit 815a9f49bb1d855c4644cd976cc381669ba0c430 Author: Nicolas Vigier <boklm(a)torproject.org> Date: Mon Sep 4 18:53:04 2017 +0200 Add new Tor Browser version: 7.0.5 --- include/versions.wmi | 20 ++++++++++---------- projects/torbrowser/RecommendedTBBVersions | 4 ++++ 2 files changed, 14 insertions(+), 10 deletions(-) diff --git a/include/versions.wmi b/include/versions.wmi index 5319a08e..6e11eba7 100644 --- a/include/versions.wmi +++ b/include/versions.wmi @@ -5,24 +5,24 @@ <define-tag version-torbrowserdevelopbranch whitespace=delete>maint-7.0</define-tag> -<define-tag version-torbrowserbundle whitespace=delete>7.0.4</define-tag> -<define-tag releasedate-torbrowserbundle whitespace=delete>2017-08-08</define-tag> +<define-tag version-torbrowserbundle whitespace=delete>7.0.5</define-tag> +<define-tag releasedate-torbrowserbundle whitespace=delete>2017-09-04</define-tag> <define-tag version-torbrowserbundlebeta whitespace=delete>7.5a4</define-tag> <define-tag releasedate-torbrowserbundlebeta whitespace=delete>2017-08-08</define-tag> -<define-tag version-torbrowserbundlelinux32 whitespace=delete>7.0.4</define-tag> -<define-tag releasedate-torbrowserbundlelinux32 whitespace=delete>2017-08-08</define-tag> -<define-tag version-torbrowserbundlelinux64 whitespace=delete>7.0.4</define-tag> -<define-tag releasedate-torbrowserbundlelinux64 whitespace=delete>2017-08-08</define-tag> +<define-tag version-torbrowserbundlelinux32 whitespace=delete>7.0.5</define-tag> +<define-tag releasedate-torbrowserbundlelinux32 whitespace=delete>2017-09-04</define-tag> +<define-tag version-torbrowserbundlelinux64 whitespace=delete>7.0.5</define-tag> +<define-tag releasedate-torbrowserbundlelinux64 whitespace=delete>2017-09-04</define-tag> <define-tag version-torbrowserbundlelinux32beta whitespace=delete>7.5a4</define-tag> <define-tag releasedate-torbrowserbundlelinux32beta whitespace=delete>2017-08-08</define-tag> <define-tag version-torbrowserbundlelinux64beta whitespace=delete>7.5a4</define-tag> <define-tag releasedate-torbrowserbundlelinux64beta whitespace=delete>2017-08-08</define-tag> -<define-tag version-torbrowserbundleosx32 whitespace=delete>7.0.4</define-tag> -<define-tag releasedate-torbrowserbundleosx32 whitespace=delete>2017-08-08</define-tag> -<define-tag version-torbrowserbundleosx64 whitespace=delete>7.0.4</define-tag> -<define-tag releasedate-torbrowserbundleosx64 whitespace=delete>2017-08-08</define-tag> +<define-tag version-torbrowserbundleosx32 whitespace=delete>7.0.5</define-tag> +<define-tag releasedate-torbrowserbundleosx32 whitespace=delete>2017-09-04</define-tag> +<define-tag version-torbrowserbundleosx64 whitespace=delete>7.0.5</define-tag> +<define-tag releasedate-torbrowserbundleosx64 whitespace=delete>2017-09-04</define-tag> <define-tag version-torbrowserbundleosx64beta whitespace=delete>7.5a4</define-tag> <define-tag releasedate-torbrowserbundleosx64beta whitespace=delete>2017-08-08</define-tag> <define-tag version-torbrowsersandboxlinux whitespace=delete>0.0.12</define-tag> diff --git a/projects/torbrowser/RecommendedTBBVersions b/projects/torbrowser/RecommendedTBBVersions index fdf796fe..71006442 100644 --- a/projects/torbrowser/RecommendedTBBVersions +++ b/projects/torbrowser/RecommendedTBBVersions @@ -3,6 +3,10 @@ "7.0.4-MacOS", "7.0.4-Windows", "7.0.4-Linux", +"7.0.5", +"7.0.5-MacOS", +"7.0.5-Windows", +"7.0.5-Linux", "7.5a4", "7.5a4-MacOS", "7.5a4-Windows",

1 0

[webwml/staging] Fix typo in url in press article
by hiro＠torproject.org 07 Sep '17

07 Sep '17

commit 72eb2dcfa4b5fa5df5e7591159f1e673d192e32a Author: hiromipaw <hiro(a)torproject.org> Date: Thu Aug 31 18:46:56 2017 +0200 Fix typo in url in press article --- press/en/press.wml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/press/en/press.wml b/press/en/press.wml index 6089c1d4..cb642cb1 100644 --- a/press/en/press.wml +++ b/press/en/press.wml @@ -65,7 +65,7 @@ some of the significant Tor-related stories that have popped up.</p> <tr style=""> <td>2017 Aug 17</td> <td>CNET</td> -<td><a href="www.cnet.com/g00/news/tor-project-disgusted-by-daily-stormer-defends-softwa…">Tor Project 'disgusted' by Daily Stormer, defends software ethos</a></td> +<td><a href="https://www.cnet.com/g00/news/tor-project-disgusted-by-daily-stormer-defend…">Tor Project 'disgusted' by Daily Stormer, defends software ethos</a></td> </tr> <tr style="background-color: #e5e5e5;">

1 0

[webwml/staging] Bump alpha version to 0.3.1.6-rc
by hiro＠torproject.org 07 Sep '17

07 Sep '17

commit 88b17d9e069ab2bc704e08809777896b4d41b473 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Sep 5 10:12:58 2017 -0400 Bump alpha version to 0.3.1.6-rc --- Makefile | 2 +- include/versions.wmi | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 56452394..584ad168 100644 --- a/Makefile +++ b/Makefile @@ -15,7 +15,7 @@ # website component, and set it to needs_review. export STABLETAG=tor-0.3.0.10 -export DEVTAG=tor-0.3.1.5-alpha +export DEVTAG=tor-0.3.1.6-rc WMLBASE=. diff --git a/include/versions.wmi b/include/versions.wmi index 6e11eba7..1740e025 100644 --- a/include/versions.wmi +++ b/include/versions.wmi @@ -1,5 +1,5 @@ <define-tag version-stable whitespace=delete>0.3.0.10</define-tag> -<define-tag version-alpha whitespace=delete>0.3.1.5-alpha</define-tag> +<define-tag version-alpha whitespace=delete>0.3.1.6-rc</define-tag> <define-tag version-win32-stable whitespace=delete>0.3.0.10</define-tag>

1 0

[torspec/master] Remove section 5.4.5.
by nickm＠torproject.org 07 Sep '17

07 Sep '17

commit 0951a931f66b5389027e900aaa1af01e81db634f Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 7 09:40:06 2017 -0400 Remove section 5.4.5. This section made sense with the v2 networkstatus algorithm, but we haven't used that one for years and years. --- dir-spec.txt | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index 3c57fb8..20416a6 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -3502,21 +3502,6 @@ The following methods have incorrect implementations; authorities SHOULD ... -5.4.5. Router protocol versions - - A client should believe that a router supports a given feature if that - feature is supported by the router or protocol versions in more than half - of the live networkstatuses' "v" entries for that router. In other words, - if the "v" entries for some router are: - v Tor 0.0.8pre1 (from authority 1) - v Tor 0.1.2.11 (from authority 2) - v FutureProtocolDescription 99 (from authority 3) - then the client should believe that the router supports any feature - supported by 0.1.2.11. - - This is currently equivalent to believing the median declared version for - a router in all live networkstatuses. - 6. Standards compliance All clients and servers MUST support HTTP 1.0. Clients and servers MAY

1 0

[tor/master] Add a module comment to util_bug.h
by nickm＠torproject.org 07 Sep '17

07 Sep '17

commit 1502bf03fdf8255d4673cc529e02ad69cef9995d Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 7 09:31:30 2017 -0400 Add a module comment to util_bug.h Closes ticket 22824. --- src/common/util_bug.h | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/src/common/util_bug.h b/src/common/util_bug.h index de39317d1..ce6565d92 100644 --- a/src/common/util_bug.h +++ b/src/common/util_bug.h @@ -5,6 +5,32 @@ /** * \file util_bug.h + * + * \brief Macros to manage assertions, fatal and non-fatal. + * + * Guidelines: All the different kinds of assertion in this file are for + * bug-checking only. Don't write code that can assert based on bad inputs. + * + * We provide two kinds of assertion here: "fatal" and "nonfatal". Use + * nonfatal assertions for any bug you can reasonably recover from -- and + * please, try to recover! Many severe bugs in Tor have been caused by using + * a regular assertion when a nonfatal assertion would have been better. + * + * If you need to check a condition with a nonfatal assertion, AND recover + * from that same condition, consider using the BUG() macro inside a + * conditional. For example: + * + * <code> + * // wrong -- use tor_assert_nonfatal() if you just want an assertion. + * BUG(ptr == NULL); + * + * // okay, but needlessly verbose + * tor_assert_nonfatal(ptr != NULL); + * if (ptr == NULL) { ... } + * + * // this is how we do it: + * if (BUG(ptr == NULL)) { ... } + * </code> **/ #ifndef TOR_UTIL_BUG_H

1 0

[tor/master] Talk about assertions in CodingStandards.md
by nickm＠torproject.org 07 Sep '17

07 Sep '17

commit 8421756da3fc3cc116d17fe96b50384c0d79af8b Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 7 09:37:39 2017 -0400 Talk about assertions in CodingStandards.md --- doc/HACKING/CodingStandards.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md index 55c23a7df..a8fca4a77 100644 --- a/doc/HACKING/CodingStandards.md +++ b/doc/HACKING/CodingStandards.md @@ -249,7 +249,25 @@ end-users that they aren't expected to understand the message (perhaps with a string like "internal error"). Option (A) is to be preferred to option (B). +Assertions In Tor +----------------- +Assertions should be used for bug-detection only. Don't use assertions to +detect bad user inputs, network errors, resource exhaustion, or similar +issues. + +Tor is always built with assertions enabled, so try to only use +`tor_assert()` for cases where you are absolutely sure that crashing is the +least bad option. Many bugs have been caused by use of `tor_assert()` when +another kind of check would have been safer. + +If you're writing an assertion to test for a bug that you _can_ recover from, +use `tor_assert_nonfatal()` in place of `tor_assert()`. If you'd like to +write a conditional that incorporates a nonfatal assertion, use the `BUG()` +macro, as in: + + if (BUG(ptr == NULL)) + return -1; Doxygen comment conventions ---------------------------

1 0

[torspec/master] Mention link protocol 5 in section 9.1
by nickm＠torproject.org 07 Sep '17

07 Sep '17

commit 5772170591a11bcdb2ef7ac2675790614c184896 Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Sep 7 09:02:11 2017 -0400 Mention link protocol 5 in section 9.1 Closes ticket 22918. --- tor-spec.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/tor-spec.txt b/tor-spec.txt index 600d457..3431ca5 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -1701,9 +1701,10 @@ see tor-design.pdf. Two Tor instances can make a connection to each other only if they have at least one link protocol in common. - The current "link" versions are: "1" through "4". See section 4.1 for more - information. All current Tor versions support "1-3"; version from - 0.2.4.11-alpha and on support "1-4". Eventually we will drop "1" and "2". + The current "link" versions are: "1" through "5". See section 4.1 for more + information. All current Tor versions support "1-3"; versions from + 0.2.4.11-alpha and on support "1-4"; versions from 0.3.1.1-alpha and on + support "1-5". Eventually we will drop "1" and "2". 9.2. "LinkAuth"

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits September 2017