tor-commits February 2016

tor-commits@lists.torproject.org

18 participants
833 discussions

[translation/tor-messenger-authproperties_completed] Update translations for tor-messenger-authproperties_completed
by translation＠torproject.org 29 Feb '16

29 Feb '16

commit 0ffba924f1ad42b43b2845e154a469a421e6bd6f Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 29 22:16:19 2016 +0000 Update translations for tor-messenger-authproperties_completed --- sv/auth.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/auth.properties b/sv/auth.properties index 66d2cac..a8045ba 100644 --- a/sv/auth.properties +++ b/sv/auth.properties @@ -1,6 +1,6 @@ auth.title=Verifiera identiteten hos %S auth.… [View More]

1 0

[translation/tor-messenger-authproperties] Update translations for tor-messenger-authproperties
by translation＠torproject.org 29 Feb '16

29 Feb '16

commit 51347e56269dbfea3fbe01227fe0dfbf5774a505 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 29 22:16:15 2016 +0000 Update translations for tor-messenger-authproperties --- sv/auth.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/auth.properties b/sv/auth.properties index 66d2cac..a8045ba 100644 --- a/sv/auth.properties +++ b/sv/auth.properties @@ -1,6 +1,6 @@ auth.title=Verifiera identiteten hos %S auth.… [View More]

1 0

[tor-messenger-build/master] Update participants list with new followers
by arlo＠torproject.org 29 Feb '16

29 Feb '16

commit df9d65b1bebb00d294fbc8187f0395c2c75c8f7a Author: Arlo Breault <arlolra(a)gmail.com> Date: Mon Feb 29 12:56:10 2016 -0800 Update participants list with new followers --- projects/instantbird/bug-955324.patch | 52 +++++++++++++++++++++++++++++++++++ projects/instantbird/config | 1 + 2 files changed, 53 insertions(+) diff --git a/projects/instantbird/bug-955324.patch b/projects/instantbird/bug-955324.patch new file mode 100644 index 0000000..c16b0db --- /dev/null … [View More]+++ b/projects/instantbird/bug-955324.patch @@ -0,0 +1,52 @@ +# HG changeset patch +# User Arlo Breault <arlolra(a)gmail.com> +# Date 1456775633 28800 +# Mon Feb 29 11:53:53 2016 -0800 +# Node ID 6e6444a94b87a64b6ac316280f810709b632d461 +# Parent f2acd8984cea1a68e57a2c30e93a3089a9bce76d +Bug 955324 - Starting/stopping to follow someone doesn't update the participant list of the timeline + +diff --git a/chat/protocols/twitter/twitter.js b/chat/protocols/twitter/twitter.js +--- a/chat/protocols/twitter/twitter.js ++++ b/chat/protocols/twitter/twitter.js +@@ -569,16 +569,17 @@ Account.prototype = { + // friendships/destroy will return the user in case of success. + // Error cases would return a non 200 HTTP code and not call our callback. + this.signAndSend("1.1/friendships/destroy.json", null, + [["screen_name", aUserName]], function(aData, aXHR) { + let user = JSON.parse(aData); + if (!("id_str" in user)) + return; // Unexpected response... + this._friends.delete(user.id_str); ++ this.timeline.removeParticipant(user.screen_name); + let date = aXHR.getResponseHeader("Date"); + this.timeline.systemMessage(_("event.unfollow", user.screen_name), false, + new Date(date) / 1000); + }, null, this); + }, + addBuddy: function(aTag, aName) { + this.follow(aName); + }, +@@ -775,19 +776,21 @@ Account.prototype = { + // Overwrite the existing _friends list (if any). + this._friends = new Set(msg.friends.map(aId => aId.toString())); + } + else if ("event" in msg) { + let user, event; + switch(msg.event) { + case "follow": + if (msg.source.screen_name == this.name) { +- this._friends.add(msg.target.id_str); + user = msg.target; + event = "follow"; ++ this.setUserInfo(user); ++ this._friends.add(user.id_str); ++ this.timeline._ensureParticipantExists(user.screen_name); + } + else if (msg.target.screen_name == this.name) { + user = msg.source; + event = "followed"; + } + if (user) { + this.setUserInfo(user); + this.timeline.systemMessage(_("event." + event, user.screen_name), diff --git a/projects/instantbird/config b/projects/instantbird/config index 8fb173e..b9d846c 100644 --- a/projects/instantbird/config +++ b/projects/instantbird/config @@ -76,6 +76,7 @@ input_files: - filename: trac-17896.patch - filename: trac-17494.patch - filename: trac-13312.patch + - filename: bug-955324.patch - filename: version.patch - filename: search-context-menu.patch - filename: search-preferences-xul.patch [View Less]

1 0

[translation/mat-gui_completed] Update translations for mat-gui_completed
by translation＠torproject.org 29 Feb '16

29 Feb '16

commit 9c3cc24469930823b9d114b8a76d88ebf607011c Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 29 20:45:37 2016 +0000 Update translations for mat-gui_completed --- sv.po | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/sv.po b/sv.po index 545a1cc..d99890b 100644 --- a/sv.po +++ b/sv.po @@ -8,14 +8,15 @@ # Foo Bar, 2014 # Henry Blom <info(a)sweportal.com>, 2015 # Jimmy Jägerström, 2013 +# T <tonys(a)… [View More]

1 0

[translation/mat-gui] Update translations for mat-gui
by translation＠torproject.org 29 Feb '16

29 Feb '16

commit 7b08989e8ebf98d656abe44a5f058d8514cc38e0 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 29 20:45:33 2016 +0000 Update translations for mat-gui --- sv.po | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sv.po b/sv.po index d0d66e2..d99890b 100644 --- a/sv.po +++ b/sv.po @@ -8,15 +8,15 @@ # Foo Bar, 2014 # Henry Blom <info(a)sweportal.com>, 2015 # Jimmy Jägerström, 2013 -# T N <tonys(a)labrinth.eu>, … [View More]

1 0

[translation/tor-messenger-privproperties_completed] Update translations for tor-messenger-privproperties_completed
by translation＠torproject.org 29 Feb '16

29 Feb '16

commit 1cdd9bc5ed30f167719eaed6da662ab42ec466d5 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 29 19:46:43 2016 +0000 Update translations for tor-messenger-privproperties_completed --- sv/priv.properties | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sv/priv.properties b/sv/priv.properties index 50a8790..ae9acc8 100644 --- a/sv/priv.properties +++ b/sv/priv.properties @@ -1 +1,2 @@ -priv.account=Skapar privat nyckel för %S (%S) ..… [View More]

1 0

[translation/mat-gui] Update translations for mat-gui
by translation＠torproject.org 29 Feb '16

29 Feb '16

commit ab5fb7caac12d4ed2b36b6dac6bd788be2362aff Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 29 19:45:32 2016 +0000 Update translations for mat-gui --- sv.po | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/sv.po b/sv.po index cdfc8c1..d0d66e2 100644 --- a/sv.po +++ b/sv.po @@ -8,14 +8,15 @@ # Foo Bar, 2014 # Henry Blom <info(a)sweportal.com>, 2015 # Jimmy Jägerström, 2013 +# T N <tonys(a)labrinth.eu>, 2016 # … [View More]

1 0

[webwml/master] Drop projects/mentors we haven't heard from
by atagar＠torproject.org 29 Feb '16

29 Feb '16

commit 3ddd63efa5296a221daa8a295280b37b2546e2bf Author: Damian Johnson <atagar(a)torproject.org> Date: Mon Feb 29 09:07:37 2016 -0800 Drop projects/mentors we haven't heard from Dropping the folks we haven't heard from with regard to GSoC. For projects where they're the last names remaining dropping the project itself too. --- getinvolved/en/volunteer.wml | 307 +------------------------------------------ 1 file changed, 3 insertions(+), 304 deletions(-) diff --git a/… [View More]getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index aa53608..0b6d497 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -416,11 +416,7 @@ meetings around the world.</li> Project Ideas: - <a href="#torCleanup">Tor Codebase Cleanup</a> - <a href="#improveTorTestCoverage">Improve test coverage in Tor</a> - <a href="#useMoreCores">Have the Tor daemon use more cores</a> - <a href="#improveHiddenServices">Help improve Tor hidden services</a> - <a href="#improvedDnsSupport">Improved DNS support for Tor</a> + <a href="#improveHiddenServices">Help improve Tor hidden services</a> <a id="project-torbrowser"></a> @@ -558,12 +554,6 @@ meetings around the world.</li> block Tor. This has both a C and python implementation. - - Project Ideas: - <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Helpn…">Various coding tasks</a> - <a href="#betterPluggableTransports">Build Better Pluggable Transports</a> - - <a id="project-flash-proxy"></a> <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a @@ -795,11 +785,6 @@ meetings around the world.</li> content. - - Project Ideas: - <a href="#ooniprobePcapsSupport">Add Support for Reporting Pcaps to OoniBackend and OoniProbe</a> - - <a id="project-torps"></a> <h3>TorPS</a> (<a href="https://github.com/torps/torps">code</a>)</h3> @@ -866,125 +851,13 @@ meetings around the world.</li> <ol> - <a id="torCleanup"></a> - <li> - Tor Codebase Cleanup - - Language: C - - Likely Mentors: David (dgoulet) - - - The Tor code is more than 10 years old in places, and we haven't always had - enough time or wisdom to write things as well as we could have. Our unit - test coverage is shamefully low, and the dependency graph of our modules is - shamefully convoluted . We could use refactoring and unit tests! Please - look through the Tor source code and look for ugly or tricky code or - dependencies -- the uglier and trickier the better -- and think about how - you could make the code look better, read better, and (subject to testing) - work better. - - - - If this is for a fun side-project, it would be great for you to work on - anything that can be made better and more tested. For an internship-level - position, we'd hope that you could find a number of particularly tricky or - knotty piece of the code to clean up, and aim for resolving the ugliest - problems, not necessarily the easiest. - - - - For a big project here, it would be great to pick one of the major - "submodules" of Tor -- path selection, node discovery, directory authority - operations, directory service -- and refactor its interface completely, to - minify and codify its points of contact with the rest of Tor. - - - - As part of your application for this project please identify one of the - thorniest Tor functions and submit a patch refactoring it to be better. If - you find this to be difficult then this likely isn't the project for - you. - - </li> - - <a id="betterPluggableTransports"></a> - <li> - Build Better Pluggable Transports - - Language: C, Python - - Likely Mentors: Ximin (infinity0) - - - For Tor users in censored countries, we have a <a - href="<page docs/pluggable-transports>"> - pluggable transports</a> framework that uses external programs to bypass - censorship in different ways. Each of these have their own strengths and - weaknesses. - - - - We have deployed <a - href="<page projects/obfsproxy>">obfsproxy</a>, - <a href="http://crypto.stanford.edu/flashproxy/">flashproxy</a>, - <a href="http://www.cs.kau.se/philwint/scramblesuit/">scramblesuit</a>, - <a href="https://trac.torproject.org/projects/tor/wiki/doc/meek">meek</a>, - and <a href="https://fteproxy.org/about">FTE</a> bridges into the main - Tor Browser.</a> - - - - There are several possible directions for this project. Ideas include: - <ol> - <li>Address gaps or weaknesses in our existing pluggable transports - <ul> - <li>Flashproxy: Add WebRTC support to traverse NATs.</li> - <li>Flashproxy: Improve the facilitator's resistance against DoS - and poisoning attacks.</li> - </ul> - </li> - <li>Finish and release our pluggable transport combiner, that chains - several transports together to take advantage of orthogonal types of - blocking resistance.</li> - <li>Improve the UX for selecting the appropriate pluggable transport in - the new Tor Browser, whilst maintaining user security.</li> - <li>Implement a new pluggable transport that resists blocking in a - novel way. - <ul> - <li>Impersonate a voice-over-IP protocol</li> - <li>Impersonate HTTP <a - href="http://www.cs.utexas.edu/~amir/papers/parrot.pdf">sufficiently - well</a> that traffic will go through a HTTP-only proxy</li> - <li>Implement <a - href="http://cacr.uwaterloo.ca/techreports/2011/cacr2011-21.pdf">scanning - resistance</a></li> - </ul> - </li> - </ol> - - - - Applicants should be familiar with asynchronous/reactive programming, in - particular the <a href="https://twistedmatrix.com/">Twisted framework</a> - or something related. Most of the existing code is written in Python, with - some parts in JavaScript and Go, so you should know at least one of these. - You are invited to talk to us and ask questions, via our mailing lists - or IRC. As part of your application, please contribute a patch that - implements a small feature or fixes a bug related to this area, e.g. <a - href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Plu…">1</a>, - <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Obf…">2</a>, - <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Fla…">3</a>. - - - <a id="makeTorbirdyBetter"></a> <li> Make TorBirdy Better Language: JavaScript, C++ - Likely Mentors: Sukhbir Singh (sukhe), Jacob Appelbaum (ioerror) + Likely Mentors: Sukhbir Singh (sukhe) TorBirdy is an extension that configures Thunderbird to make connections over @@ -1021,152 +894,13 @@ You may contact the mentors on IRC for more information. (sukhe on #tor-dev, #to </li> - <a id="ooniprobePcapsSupport"></a> - <li> - Add Support for Reporting Pcaps to OoniBackend and OoniProbe - - Language: Python - - Likely Mentors: Arturo (hellais) - - -The feature should also add support for including only packet capture data that -is relevant to the test being run. This means that the pcap should not contain -all the data sniffed on the users machine, but only that which was generated -and intended to be received by ooniprobe. - - - -This can probably be implemented by setting up a tun/tap device and routing all -the ooniprobe traffic through it and only capturing data sent and received from -that device. The task for the student will also be that of doing research into -what are possible strategies for doing this. <a -href="https://trac.torproject.org/projects/tor/ticket/7416">For more -information see ticket 7416.</a> - - </li> - - <a id="improveTorTestCoverage"></a> - <li> - Improve test coverage in Tor - - Language: C, Python - - Likely Mentors: David (dgoulet) - - -Right now, our unit test coverage with the tests we ship is around 30% --- only 30% of the executable lines in our source are reached by the -unit tests. Improving this test coverage could make Tor development -much more reliable. - - - -So we need better unit tests, and we need better integration tests too. - - - -Improving unit tests would involve refactoring functions to be more -testable, and writing a bunch of unit tests. - - - -Improving integration tests would involve refactoring and improving -the "chutney" program that launches a test tor network, and writing a -bunch of tests to see what works and what doesn't work on such a -network. It could also involve writing tests using the library "<a -href="https://stem.torproject.org/">stem</a>" to script individual clients on a -Chutney network. - - - -To get a feel for how testing works in Tor today, download Tor and -Chutney, and make sure you can build Tor and use Chutney. See how the -unit tests work by skimming some of the test code in the src/test -subdirectory. Try computing test coverage (according to the -instructions in the doc/HACKING file. - - - -Also, have a look at the one current integration test that works on -chutney today: it is a shell script distributed with Tor as -src/test/test-tor-network.sh . We probably don't want to have all of -our integration tests be written as shell scripts, but it's interesting -to see how one works. - - - -If working on designs for an improved or refactored Chutney, watch out for <a -href="http://www.joelonsoftware.com/articles/fog0000000018.html">"archicture -astronautics"</a>: while it's important that we have a well-designed and -maintainable Chutney architecture, it wouldn't be very useful if a good -architecture were the only outcome here: we need tests too. - - - -As part of the application process, please contribute a patch that makes -a non-trivial improvement to chutney, and/or include a new test for some -interesting Tor function. (Please pick a function that isn't completely -easy to test.) - - </li> - - <a id="useMoreCores"></a> - <li> - Have the Tor daemon use more cores - - Language: C - - Likely Mentors: David (dgoulet) - - -Right now, if you run a busy Tor server on a multicore computer, most of -the cores are mostly unused. We have a "cpuworker" mechanism to move -expensive computations into worker threads, but that mechanism is -currently only used for a small fraction of our cryptography. Moving -more work into the worker threads could improve performance immensely. - - - -So it would be great to parallelize our cryptography more in order to -better handle more cores. See -<a href="https://trac.torproject.org/projects/tor/wiki/org/projects/Tor/Multithreade…">MultithreadedCrypto</a> -for some background info, and -<a href="https://trac.torproject.org/projects/tor/ticket/7572">ticket 7572</a> for some subtickets -on our tracker. - - - -(If you're reading through the code to see how it works today, you will -also want to have a look at the new implementation for cpuworkers -described in <a href="https://trac.torproject.org/projects/tor/ticket/9682">9682</a>.) - - - -Completing the implementation of ticket #7572 --which would move our -circuit crypto onto separate threads-- could be a good summer project. -Alternatively, moving all of the signature generation and verification -code onto the cpuworkers could be fun. In either case, you will have -some important architectural decisions to make about how to minimize -shared data between the main thread and the workers, how to avoid -race conditions between them, and how to test it all to make sure it has -no hidden failure cases. - - - -As part of the application process for this project, please contribute a -nontrivial patch to Tor -- ideally, one that will affect some part of -the codebase that you want to work on. - - </li> - <a id="improveHiddenServices"></a> <li> Help improve Tor hidden services Language: C - Likely Mentors: David (dgoulet), George (asn) + Likely Mentors: George (asn) We're working on a revamp of the entire Tor hidden service design to @@ -1196,41 +930,6 @@ the codebase that you want to work on. </li> - <a id="improvedDnsSupport"></a> - <li> - Improved DNS support for Tor - - Language: C - - Likely Mentors: David (dgoulet) - - -Right now, you can only use Tor's DNS support to look up IPv4 and IPv6 -addresses, and to fetch PTR records. But DNS can do so much more! - - - -<a -href="https://gitweb.torproject.org/torspec.git/tree/proposals/219-expanded-dns.t…">Proposal -219</a> describes some new cell types that Tor could use to support -more types of DNS over Tor. - - - -To see how Tor implements its existing DNS lookups, start by tracing the -the connection_exit_begin_resolve() function in src/or/connection_edge.c , -and see how we pass these requests downwards through src/or/dns.c to the -underlying resolver. It's not too complicated, but there are some -tricky parts to understand. - - - -As part of the application process for this project, please contribute a -nontrivial patch to Tor -- ideally, one that will affect some part of -the codebase that you want to work on. - - </li> - <a id="exitmap_improvements"></a> <li> Exitmap Improvements [View Less]

1 0

[webwml/master] Add 'Make Stegotorus deployment ready' project idea
by atagar＠torproject.org 29 Feb '16

29 Feb '16

commit fb8533f7efb33698413519fa391f400265ba994d Author: Damian Johnson <atagar(a)torproject.org> Date: Mon Feb 29 09:00:35 2016 -0800 Add 'Make Stegotorus deployment ready' project idea --- getinvolved/en/volunteer.wml | 138 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 138 insertions(+) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index 6c73977..aa53608 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -… [View More]1527,6 +1527,144 @@ implementation. </li> + <a id="stegotorus"></a> + <li> + Make Stegotorus deployment ready + + Language: C++ + + Likely Mentors: vmon + + + <a + href="https://github.com/TheTorProject/stegotorus/tree/master/src">Stegotorus</a> + is a PT framework which streamline the development stealthier pluggable + transport. An HTTP pluggable transport is already implemented in Stegotorus + framework and can be used when encrypted payloads are throttled and only + ephemeral connections are tolerated. + + + + The majority of work on Stegotorus is done and it can be deployed with a relatively minor improvements including: + + + <ul> + <li>#8098 A config file file for Stegotorus + + Stegotorus needs many configuration settings specially on the bridge + side. This include also the configuration required by each steg module. + Currently the configuration is fed to Stegotorus as command line + arguments but a file like torrc is needed so all tweaking can be read + from there. + + + + Current Status and work needed to be done: The code for reading the + config file is written by SRI but it is not yet used in the Stegotorus + to read the config. + + </li> + + <li>#8101 Debugging the transparent proxy + + Stegotorus http module uses other websites payload to hide and serve + censored traffic. As such it needs to decide if the request is + genuinely to the auxiliary website, in that case becomes a transparent + proxy and serves the website content as requested, or if the request is + actually a request to serve censored material which should be delivered + to steg modules. + + + + Current Status: This is completely implemented. However, the transparent proxy sometimes crashes and need to be triaged, debugged and fixed. + + </li> + + <li>#11337 refactoring the steg module code + + The http steg module code, although not essentials to the core of the + Stegotorus. needs some improvement and clean up. The solution is to + refactor the steg modules as children of FileStegMod. + + + + Current status and work needed to be done: This has already been done + but still needs testing and refactoring before it can be reliably merge + to the master branch. + + </li> + + <li>#8089 Adding Elligator to Stegotorus handshake and test + + The current Stegotorus handshake is distinguishable from random byte + string, which can be used to flag and detect Stegotorus traffic + deterministically and need to be implemented similar to + ScrambleSuite. Also because the capacity of client to server channel + might be slim depending on the choice of steg module it is desirable + to be implemented using Elliptic curve crypto. Hence, Elligator + protocol is ideal solution for this situation. All we need is to replace Stegotorus handshake by Elligator. + + + + Current Status and work needed to be done: Elligator handshake code is + included in stegotorus code base, it is only needed to be called by + instead of the current handshake and be tested. + + </li> + + <li>Make Stegotorus memory safe by using shared pointers + + Stegotorus has large code base and it is not written in a memory safe + languages. To facilitate its audit, we need to replace (almost all) use + of pointers to shared pointers. + + + + Current Status: No progress has not been done. + + </li> + + <li>Security Audit and writing more unit test + + To be able to deploy Stegotorus for real world use we need to audit the + code and write more unit test covering new aspects of the Stegotorus + (new http transport, proxy server, Elligator handshake) + + + + Current Status: No progress has been done. + + </li> + + <li>SRI branch merging + + Stegotorus has been forked from the initial development from SRI. Now + that SRI is hosting Stegotorus publicly it is desirable to merge the + two branches so we can benefit from both developments. + + + + Current Status: No progress has been done. + + </li> + + <li>#8099 deterministic build + + To make deterministic build possible we need to build many of + Stegotorus dependency from scratch. Boost library is a a huge + dependency for Stegotorus to access the file system. As we are only + planning to deploy Stegotorus bridges on Linux machines we can simplify + such access without that dependency. By dropping such dependency, it + should be straight forward to have deterministic build for Stegotorus. + + + + Current Status: No progress has been done. + + </li> + </ul> + </li> + <!-- <a id=""></a> <li> [View Less]

1 0

[tor-commits] [translation/tor-messenger-commandsproperties_completed] Update translations for tor-messenger-commandsproperties_completed
by translation＠torproject.org 29 Feb '16

29 Feb '16

commit 2432f4e158957ef7d8aef3f92e10e75173a92b70 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Feb 29 12:46:18 2016 +0000 Update translations for tor-messenger-commandsproperties_completed --- ko/commands.properties | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/ko/commands.properties b/ko/commands.properties new file mode 100644 index 0000000..6755bf9 --- /dev/null +++ b/ko/commands.properties @@ -0,0 +1,27 @@ +# This … [View More]

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits February 2016