tor-commits March 2016

tor-commits@lists.torproject.org

16 participants
1259 discussions

[webwml/staging] Add new Tor Browser versions
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit e85cab01121b8d972e7e0d8c22e6b0428f783966 Author: Georg Koppen <gk(a)torproject.org> Date: Mon Feb 15 13:40:57 2016 +0000 Add new Tor Browser versions --- include/versions.wmi | 10 +++++----- projects/torbrowser/RecommendedTBBVersions | 8 +++++++- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/include/versions.wmi b/include/versions.wmi index 3f59644..f135692 100644 --- a/include/versions.wmi +++ b/include/versions.wmi @@ -5,19 +5,19 @@ <define-tag version-torbrowserdevelopbranch whitespace=delete>maint-5.5</define-tag> <define-tag version-torbrowserbundledir whitespace=delete>5.5.2</define-tag> -<define-tag version-torbrowserbundlebetadir whitespace=delete>6.0a1</define-tag> +<define-tag version-torbrowserbundlebetadir whitespace=delete>6.0a2</define-tag> <define-tag version-torbrowserbundle whitespace=delete>5.5.2</define-tag> -<define-tag version-torbrowserbundlebeta whitespace=delete>6.0a1</define-tag> +<define-tag version-torbrowserbundlebeta whitespace=delete>6.0a2</define-tag> <define-tag version-torbrowserbundlelinux32 whitespace=delete>5.5.2</define-tag> <define-tag version-torbrowserbundlelinux64 whitespace=delete>5.5.2</define-tag> -<define-tag version-torbrowserbundlelinux32beta whitespace=delete>6.0a1</define-tag> -<define-tag version-torbrowserbundlelinux64beta whitespace=delete>6.0a1</define-tag> +<define-tag version-torbrowserbundlelinux32beta whitespace=delete>6.0a2</define-tag> +<define-tag version-torbrowserbundlelinux64beta whitespace=delete>6.0a2</define-tag> <define-tag version-torbrowserbundleosx32 whitespace=delete>5.5.2</define-tag> <define-tag version-torbrowserbundleosx64 whitespace=delete>5.5.2</define-tag> -<define-tag version-torbrowserbundleosx64beta whitespace=delete>6.0a1</define-tag> +<define-tag version-torbrowserbundleosx64beta whitespace=delete>6.0a2</define-tag> <define-tag package-win32-stable whitespace=delete>../dist/torbrowser/<version-torbrowserbundledir>/tor-win32-<version-win32-stable>.zip</define-tag> diff --git a/projects/torbrowser/RecommendedTBBVersions b/projects/torbrowser/RecommendedTBBVersions index c7e8114..7fabb7e 100644 --- a/projects/torbrowser/RecommendedTBBVersions +++ b/projects/torbrowser/RecommendedTBBVersions @@ -7,6 +7,12 @@ "6.0a1-Linux", "6.0a1-MacOS", "6.0a1-Windows", +"6.0a2", +"6.0a2-Linux", +"6.0a2-MacOS", +"6.0a2-Windows", "6.0a1-hardened", -"6.0a1-hardened-Linux" +"6.0a1-hardened-Linux", +"6.0a2-hardened", +"6.0a2-hardened-Linux" ]

1 0

[webwml/staging] make it clearer we're not accepted to gsoc 2016 yet
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit 04a21f6daa6f9551657e2831ed69414fb8846f2f Author: Roger Dingledine <arma(a)torproject.org> Date: Fri Feb 19 22:02:10 2016 -0500 make it clearer we're not accepted to gsoc 2016 yet --- about/en/gsoc.wml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/about/en/gsoc.wml b/about/en/gsoc.wml index 7d77410..59046fe 100644 --- a/about/en/gsoc.wml +++ b/about/en/gsoc.wml @@ -26,6 +26,8 @@ href="https://www.google-melange.com/gsoc/homepage/google/gsoc2015">Google Summer of Code 2016</a>! --> + We have applied to GSoC 2016, and we should know at the end of February + whether we are in this year.

1 0

[webwml/staging] Deprecate old Tor Browser versions
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit e6d27a580d814cc30f1b9903ef65994f295dc36d Author: Georg Koppen <gk(a)torproject.org> Date: Fri Feb 19 13:39:59 2016 +0000 Deprecate old Tor Browser versions --- projects/torbrowser/RecommendedTBBVersions | 6 ------ 1 file changed, 6 deletions(-) diff --git a/projects/torbrowser/RecommendedTBBVersions b/projects/torbrowser/RecommendedTBBVersions index 7fabb7e..17aaaff 100644 --- a/projects/torbrowser/RecommendedTBBVersions +++ b/projects/torbrowser/RecommendedTBBVersions @@ -3,16 +3,10 @@ "5.5.2-Linux", "5.5.2-MacOS", "5.5.2-Windows", -"6.0a1", -"6.0a1-Linux", -"6.0a1-MacOS", -"6.0a1-Windows", "6.0a2", "6.0a2-Linux", "6.0a2-MacOS", "6.0a2-Windows", -"6.0a1-hardened", -"6.0a1-hardened-Linux", "6.0a2-hardened", "6.0a2-hardened-Linux" ]

1 0

[webwml/staging] remove censorship analyzer
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit cc82184754dbd6665966d57205e2c740a3c59fd7 Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Tue Feb 23 00:02:41 2016 +0100 remove censorship analyzer --- getinvolved/en/volunteer.wml | 38 -------------------------------------- 1 file changed, 38 deletions(-) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index f6847ec..25e7621 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -764,7 +764,6 @@ meetings around the world.</li> Project Ideas: - <a href="#censorshipAnalyzer">Develop a Censorship Analyzer</a> <a href="#ooniprobePcapsSupport">Add Support for Reporting Pcaps to OoniBackend and OoniProbe</a> @@ -1010,43 +1009,6 @@ meetings around the world.</li> </li> - <a id="censorshipAnalyzer"></a> - <li> - Develop a Censorship Analyzer - - Effort Level: Medium - - Skill Level: Medium to High (depends on the implemented tests) - - Likely Mentors: Philipp (phw) - -Tor is documented to be blocked in <a -href="https://censorshipwiki.torproject.org">several countries</a>. Analyzing -these censorship incidents can be a tedious task; especially without access to -machines inside the censoring networks. To make analysis easier, it would be -great to have a lightweight analysis tool which can be run by censored users. -This tool would conduct a number of networking tests and figure out if and how -Tor could be blocked. The tool's final report should then somehow make it back -to the Tor project. - - - -The theory behind this tool is already <a -href="http://www.cs.kau.se/philwint/pdf/foci2013.pdf">documented -in a research paper</a>. What we now need is code! Implementing it would first -mean getting familiar with <a href="https://ooni.torproject.org">OONI</a> and -<a href="http://twistedmatrix.com/trac/">Twisted</a>. After that, the tool -should be implemented as a number of OONI-specific networking tests. - - - -Applicants should be familiar with Python and asynchronous programming, -e.g., as it is used in Twisted. As part of your application for this -project please contribute a patch for a bug in <a -href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Ooni">OONI</a>. - - </li> - <a id="makeTorbirdyBetter"></a> <li> Make TorBirdy Better

1 0

[webwml/staging] Drop 'Relay Web Status Dashboard' project idea
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit 1c6d7d723160af9477d20e0455c02df7001af92b Author: Damian Johnson <atagar(a)torproject.org> Date: Sat Feb 13 18:03:28 2016 -0800 Drop 'Relay Web Status Dashboard' project idea Cristobal Leiva did this last year, so no longer relevant... https://leivaburto.github.io/sop-proposal/ --- getinvolved/en/volunteer.wml | 49 -------------------------------------------- 1 file changed, 49 deletions(-) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index 75d55d6..c0f0873 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -595,7 +595,6 @@ meetings around the world.</li> Project Ideas: <a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a> - <a href="#relayWebPanel">Relay Web Status Panel</a> <a id="project-txtorcon"></a> @@ -896,54 +895,6 @@ meetings around the world.</li> bonus points if it's Twisted. </li> - <a id="relayWebPanel"></a> - <li> - Relay Web Status Dashboard - - Effort Level: Medium - - Skill Level: Medium - - Likely Mentors: Damian (atagar) - - Relay operators presently have a good option for monitoring the status - of their relay: - <a href="https://www.atagar.com/arm/">arm</a> which uses - curses. This project would be to make a new kind of monitor specifically - for relay operators that provides a status dashboard site on localhost. - - - The interface will likely <a - href="https://www.atagar.com/arm/screenshots.php">borrow heavily from - arm</a>, except of course in areas where we can improve upon it. Two - important design constraints is that a localhost controller provides a - bigger attack surface than guis or curses, so we should be a little more - wary of what it does. This should be a read-only controller (ie, you can't - *do* anything to the relay) and by default not surface any sensitive - information (such as arm's connection panel). Also take a peek at <a - href="http://www.ntop.org/products/ntop/">ntop</a> for ideas on what we can - do with a web interface. - - - This project will likely include two parts: an AJAX site and a localhost - daemon to fulfill those requests. <a - href="https://stem.torproject.org/">Stem</a> is the backend of arm, and can - be used to get everything you see in arm's interface (making it a natural - choice for the daemon). That said, this project might entail some Stem - improvements if we run across any gaps. - - - Applicants should be familiar with Python, JavaScript, and learn about - <a href="https://stem.torproject.org/">Stem</a>. As part of your - application for this project please make both mockups of the interface and - a proof of concept demo application using JS to surface something with - Stem. <a - href="https://trac.torproject.org/projects/tor/wiki/doc/stem/bugs">Involvement - with Stem development</a> during the application process is also a big - plus. - - </li> - <a id="torCleanup"></a> <li> Tor Codebase Cleanup

1 0

[webwml/staging] remove torbel from projects listing
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit 2d2238c78205343e23883204b8be6288bfc58bef Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Mon Feb 22 23:38:58 2016 +0100 remove torbel from projects listing --- getinvolved/en/volunteer.wml | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index e260318..f6847ec 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -373,14 +373,6 @@ meetings around the world.</li> </tr> <tr> - <td>*<a href="#project-torbel">TorBEL</a></td> - <td>Backend Service</td> - <td>Python</td> - <td>None</td> - <td>Sebastian</td> - </tr> - - <tr> <td><a href="#project-tor2web">Tor2web</a></td> <td>Client Service</td> <td>Python</td> @@ -801,21 +793,6 @@ meetings around the world.</li> has stopped. - <a id="project-torbel"></a> - <h3><a - href="https://blog.torproject.org/blog/torbel-tor-bulk-exit-list-tools">TorBEL</a> (<a - href="https://gitweb.torproject.org/torbel.git">code</a>, <a - href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…">bug - tracker</a>)</h3> - - - The Tor Bulk Exitlist provides a method of identifying if IPs belong to - exit nodes or not. This is a replacement for TorDNSEL which is a stable - (though unmaintained) Haskell application for this purpose. The initial - version of TorBEL was started in GSOC 2010 but since then the project has - been inactive. - - <a id="project-tor2web"></a> <h3><a href="http://wiki.tor2web.org/index.php/Main_Page">Tor2web</a> (<a

1 0

[webwml/staging] List GSoC idea under the project
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit 2a4999e7a887bed84e91cd84919744eae69cf47c Author: Damian Johnson <atagar(a)torproject.org> Date: Wed Feb 24 08:31:18 2016 -0800 List GSoC idea under the project Oops, I've been striving to include task ideas under the project they're related to. --- getinvolved/en/volunteer.wml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index cd4908f..c1a36c9 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -693,6 +693,11 @@ meetings around the world.</li> Onions</a> research paper. + + Project Ideas: + <a href="#exitmap_improvements">Exitmap Improvements</a> + + <a id="project-doctor"></a> <h3>DocTor (<a href="https://gitweb.torproject.org/doctor.git">code</a>, <a

1 0

[webwml/staging] Add 'Implement and Integrate CONIKS for Tor Messenger' project idea
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit a7cbf704197e8494bb63d80885f7b99dfadbb0df Author: Damian Johnson <atagar(a)torproject.org> Date: Tue Feb 23 09:37:14 2016 -0800 Add 'Implement and Integrate CONIKS for Tor Messenger' project idea Project idea courtesy of Arlo. --- getinvolved/en/volunteer.wml | 72 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index 4eda17c..cd4908f 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -1371,6 +1371,78 @@ tampering. Third, unit tests should be added for existing and new code in order to make the code base more robust. </li> + + <a id="coniks_in_messenger"></a> + <li> + Implement and Integrate CONIKS for Tor Messenger + + Effort Level: Medium + + Skill Level: Medium + + Likely Mentors: Marcela, Arlo (arlolra) + +CONIKS is an end-user key management and verification system for end-to-end +secure communication services, which improves upon existing key management +systems by providing both strong security and better usability using a model +called key transparency. CONIKS does this by requiring providers to manage +tamper-evident, publicly-auditable key directories, which contain mappings from +usernames to public keys, on behalf of their users. This design makes it easier +for users (both "default" users and power users) to establish trust since they +don't have to worry about or even see keys, but users also don't have to +trust the provider to be well-behaved because the CONIKS client can run as +part of the secure messaging app and automatically check that the service +provider doesn’t map spurious keys to their users' usernames, and it can +verify that observed name-to-key mappings are consistent with what other +clients in the system are seeing. Unlike existing key transparency solutions, +CONIKS also provides strong privacy guarantees by employing cryptographic +primitives for robust data obfuscation. + + + +The CONIKS system design, protocols, and proof-of-concept are described in +great detail in the <a +href="https://www.usenix.org/system/files/conference/usenixsecurity15/sec15-paper…">CONIKS +research paper</a>, and basic reference implementations of a CONIKS key server +and a CONIKS client are avialable on <a +href="https://github.com/coniks-sys/coniks-ref-implementation">Github</a>. + + + +This project has two main components: (1) designing and implementing a CONIKS +key server tailored to Tor Messenger users, and (2) building a CONIKS client +which integrates with the Tor Messenger client. One challenge the applicant +will face is ensuring that the key server design is efficient and scalable for +large volumes of users, concurrent traffic and guarantees this scalability even +as Tor Messenger's user base grows. On the client side, the main challenges +will be to focus on space efficiency as well as minimizing computational +overhead when implementing the CONIKS consistency checks, and determining how +to best communicate CONIKS consistency check results to users in the UI. Since +Tor Messenger does not hand out online identities per se, as most online +communication services do (like, say, Twitter, in which each user has a unique +handle), the CONIKS key server for Tor Messenger will have to map usernames +from third-party communication services to the encryption keys used in Tor +Messenger. One additional important challenge that the applicant will have to +help address is ensuring that each such third-party username remains unique in +the Tor Messenger space and that such external, third-party identities are +indeed controlled by the expected user of that third-party communication +service. + + + +Some design and implementation questions have been discussed in <a +href="https://trac.torproject.org/projects/tor/ticket/17961">Ticket #17961</a>. + + + +The applicant should have some familiarity with well-known crypto primitives +and algorithms, as well as have a basic understanding of the key transparency +model. Client side integration will require some basic use of JavaScript. +Consider submitting a patch for <a +href="https://github.com/arlolra/ctypes-otr/issues">one of the open key +verification issues</a> as part of the application process. + + </li> <!-- <a id=""></a> <li>

1 0

[webwml/staging] Drop commented out project ideas
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit cfd38ff48e4be6fc21f7d0556073c70f6fc37626 Author: Damian Johnson <atagar(a)torproject.org> Date: Tue Feb 23 09:30:20 2016 -0800 Drop commented out project ideas They're invisible anyway, why burden page load with these? We can always resurrect them later if we want - that's what revision control is for after all! --- getinvolved/en/volunteer.wml | 149 ------------------------------------------- 1 file changed, 149 deletions(-) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index 25e7621..4eda17c 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -1089,55 +1089,6 @@ information see ticket 7416.</a> </li> - - <a id="improveTorTestCoverage"></a> <li> Improve test coverage in Tor @@ -1421,106 +1372,6 @@ in order to make the code base more robust. </li>  - - -<!-- <a id=""></a> <li>

1 0

[webwml/staging] Update TorBirdy description on the volunteer page
by arma＠torproject.org 09 Mar '16

09 Mar '16

commit e1434db26bd3a5930c6fb4095ef95486a61ecc7c Author: Sukhbir Singh <sukhbir(a)torproject.org> Date: Tue Feb 23 15:52:51 2016 -0500 Update TorBirdy description on the volunteer page --- getinvolved/en/volunteer.wml | 32 ++++++++++++-------------------- 1 file changed, 12 insertions(+), 20 deletions(-) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index c1a36c9..4c7d4df 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -1027,40 +1027,32 @@ meetings around the world.</li> TorBirdy is an extension that configures Thunderbird to make connections over the Tor anonymity network. TorBirdy has been under development for quite a while but there are two known leaks that prevent it from being used by a wider -audience. As part of this project, you will be working on plugging the known -leaks and implementing a HTTP proxy. +audience. As part of this project, you will be working on implementing a HTTP +proxy. -Part 1: There are two patches pending with Mozilla that will plug the two known -leaks in Thunderbird where the local time is disclosed through the date and the -message-ID header. As part of your project, you will work on getting these -patches finished/reimplemented and getting them merged with Mozilla. Please -look at tickets <a -href="https://trac.torproject.org/projects/tor/ticket/6314">#6314</a> and <a -href="https://trac.torproject.org/projects/tor/ticket/6315">#6315</a> for more -information. - -Part 2: TorBirdy needs a HTTP proxy or a HTTP -> SOCKS5 shim. Please look at +HTTP Proxy TorBirdy needs a HTTP proxy or a HTTP -> SOCKS5 shim. Please look at ticket <a href="https://trac.torproject.org/projects/tor/ticket/6958">#6958</a> -for more information. Note: this has to be done using JavaScript and not using +for more information. Note: this has to be done using JavaScript and without using an external proxy. If time permits and you are awesome enough to finish the above two tasks, you -will be working on the remaining TorBirdy tickets. +will be working on the <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Tor…"> +remaining TorBirdy tickets</a>. -Applicants should be familiar with C++ and JavaScript. As part of your -application for this project, please submit code samples for previous C++ and -JavaScript projects that you have developed or point us to projects you have -been involved with (links to a public Git/GitHub repository preferred). Prior -extension development is a big plus and will be given preference during -application ranking. +Applicants should be familiar with JavaScript (and preferably C++ as well). As +part of your application for this project, please submit code samples for +previous JavaScript projects that you have developed, or point us to projects +you have been involved with (links to a public Git/GitHub repository +preferred). Prior extension development is a big plus and will be given +preference during application ranking.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2016