- tor-dev - lists.torproject.org

GSoC: making tor daemon using more cores
by Белоус Михаил 04 Aug '14

04 Aug '14

Hi all, This my first report since my return, from millitary camp. Last week I have been watching tor daemon code and make little refactor. I think I found place where I can use my threadpool to make daemon multicore. I'm going to implement it as soon as I disquise my idea with Nick. Cheers, Mikhail

1 0

Needed improvements to the PT website
by George Kadianakis 03 Aug '14

03 Aug '14

Hello list, in my monthly status report [0] I mentioned that some PT-related parts of the website are in need of improvement. As a response, a few people sent me a private email asking me what kind of improvements I was thinking about. Instead of replying individually, I decided to send a mail to this list. Here are some of the needed improvements: - In the past, our main PT page was the obfsproxy page: https://www.torproject.org/projects/obfsproxy.html.en However, now that the scene is growing and the obfsproxy fad is shrinking, the main PT page should actually be: https://www.torproject.org/docs/pluggable-transports.html.en . Users, bridge sysadmins and researchers who want to learn about PTs will probably encounter that page. I suggest we optimize that page towards users and bridge syadmins and let researchers get their information from the "unofficial" wiki page: https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports - To make the PT page a bit more end-user-friendly, we could remove non-Tor-deployed PTs from the list, like Stegotorus, Skypemorph and Dust. These are better suited for the wiki, I think. Things that users see in the PT page should be ready to use. Also, it would be great if there was a "How to use PTs" document linked by the "Download PT bundles" section. Unfortunately, I don't think there is such a document atm. Sheried wanted to write one (with screenshots etc.) but I'm not sure if it was ever made. - To make the PT page a bit more bridge-sysadmin friendly, we could link to a "How to become an obfsbridge" document. Currently, the only such document is linked from the obfsproxy page: https://www.torproject.org/projects/obfsproxy.html.en#instructions and it only suggests installing obfsproxy. Nowadays, such a guide should also be guiding readers to install fteproxy. And Real Soon Now it will need to be guiding readers to install Yawning's obfs4proxy or gobfsproxy. Also, weasel read the guide and was not very happy. For example, the guide _suggests_ using pip as root, this is probably not sound advice and some workaround should be found. - Another document that is needed for bridge sysadmins is a "Best practices for running obfsbridges" document. Such a document could have the following advices: - Which PTs should be installed. - How to install ExtORPort and geoip. - How to find geoip stats from your bridge. - How to check whether your bridge and PTs are used. - How to enable logging in your PTs and general debugging tips. - etc. There are probably other improvements that could be suggested, but this is a good start, I think. Also, those tasks don't have any tickets at the moment. Please feel welcome to make tickets if you'd like, or I can do it at a later time :) BTW, I don't know much about UI or product marketing (#11501), so my advices might be totally off :) [0]: https://lists.torproject.org/pipermail/tor-reports/2014-August/000608.html

1 0

GSoC : Rewrite Tor Weather (Status Update 5)
by Sreenatha Bhatlapenumarthi 03 Aug '14

03 Aug '14

Hi all, This report includes my 4th status update as well. Here is a list of things I've been working on regarding the weather rewrite project. - Fixed some django/database issues that were causing errors(seen with Debug=True in settings) during user subscription in the weather webform. - Added a config option to consider the deployment time only in production mode. This was causing an issue previously because not many relays are filtered(considered recent) due to the presence of deploy time in the consideration criteria. - Made use of django's setup_environ method to ensure the standalone backend scripts running as cron jobs can operate with the proper settings. - Updated the daily script to ensure Tshirt emails are not sent to relay operators more than once. For the changes made, check out https://github.com/meejah/tor-weather/pull/10/ Here's what I'll be working on in the coming weeks. - Squash any remaining bugs with the backend scripts. - Get rid of previous mechanism of fetching data like listeners, updaters etc. - Write down test cases for various usage scenarios(e.g., check if emails are being sent to subscribers) within the vagrant environment. Cheers, Sreenatha

1 0

[GSoC] Consensus diffs - Fifth report
by Daniel Martí 03 Aug '14

03 Aug '14

Hello everyone, This is the fifth status report of my Google Summer of Code project, which is to implement consensus diffs for Tor. My mentors - Sebastian and Nick - and myself usually hold meetings on IRC on wednesday at 16h UTC. As described in my last report, I have spent the past couple of weeks integrating my work into the main Tor repository. It builds fine with the rest, all gcc/clang warnings were solved (mostly just C89 declaration errors) and all make check-spaces warnings were also fixed. You can see the result on the repository I created a few weeks ago on github [1]. You want the branch 'consdiff-1', where you will find src/or/consdiff.{h,c} and src/test/test_consdiff.c. I also added some very basic logging, so that the public consdiff_* functions will log what went wrong when returning NULL. I used LD_GENERAL for now, which I assume is wrong - suggestions welcome. I also simplified some bits for easier readability and usage, which can be found in the commit history. But most notably, I improved the docs and comments. The idea is to be able to stumble upon consdiff.c for the first time and be able to understand what it does, how and why in just a few minutes. It's hard to tell whether I did a good job at that - criticism very much appreciated. Most of that happened during the first week, as I was on a quick holiday during the second. Nick gave me some pointers on how to continue with the integration, and that's what I'll be doing in the next few days. The first thing to do is figure out a way to store multiple consensuses on disk, to be used to fetch and create diffs accordingly. There are now just over two weeks left, but I am confident that I can finish all the coding early enough to be able to test the whole thing properly. Regards. [1] https://github.com/mvdan/tor -- Daniel Martí - mvdan(a)mvdan.cc - http://mvdan.cc/ PGP: A9DA 13CD F7A1 4ACD D3DE E530 F4CA FFDB 4348 041C

2 2

GSoC Stegotorus status update
by Noah Rahman 02 Aug '14

02 Aug '14

Following closely on the heels of my last email ( https://lists.torproject.org/pipermail/tor-dev/2014-July/007248.html) I updated the pluggable transports meeting on Friday to the following effect: - Have identified somewhat of a performance regression in the PDF module and am continuing to see if I can find the source. - Finishing moving the Javascript over and am writing slimmer unit tests for it.

1 0

Hidden service don't work or work???
by Liste 02 Aug '14

02 Aug '14

After tor update the hidden service doesn't work: Client: [notice] Closing stream for '[scrubbed].onion': hidden servie is unavailable (try again later). Server: [notice] Tor 0.2.4.23 (git-417f0cacd726e549) opening log file. [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. [notice] We now have enough directory information to build circuits. [notice] Bootstrapped 80%: Connecting to the Tor network. [notice] Bootstrapped 85%: Finishing handshake with first hop. [notice] Bootstrapped 90%: Establishing a Tor circuit. [notice] Tor has successfully opened a circuit. Looks like client functionality is working. [notice] Bootstrapped 100%: Done. Not work. [notice] New control connection opened. [notice] New control connection opened. [notice] New control connection opened. Unstable. It stil work after change identity (command via control port), but is unstable. Sometime work and sometime doesn't work! (The time clock is ok).

1 0

Tor GSOC Fog Status Report #5
by quinn jarrell 02 Aug '14

02 Aug '14

H, Since the last status report, I've worked on a couple of things - Refactored the fog client code - worked on ticket #12614 [0] This is my second to last GSOC report. For the last two weeks I'll be working on getting a working version of #12614 in and cleaning/adding tests to the fog code. Quinn [0] https://trac.torproject.org/projects/tor/ticket/12614

1 0

[GSoC 2014] Revamp GetTor status update #5
by Israel Leiva 02 Aug '14

02 Aug '14

Hi all! This is my fifth status update for the Revamp GetTor GSoC project. I'll try summarize what I've done so far. If you have any comments, please tell me. Achievements: [*] New file structure of the current work. All modules now inside a gettor package. Everything is cleaner now. [*] Major code cleaning, better comments and error handling. Created exceptions for possible issues on every module. Created new module with utilities for the core module and the others (smtp and xmpp so far). [*] Created XMPP module. It receives messages and reply with links in the given locale (if specified; english by default). [*] Added info about built-in pluggable transports; if somebody mention pt, pluggable transports, obfs, obfsproxy, we reply him/her with additional info about the built-in pluggable transports (dummy message for now). [*] Added sha1 info of packages along with the dropbox links. Goals until next (last) bi-weekly report: [+] Solve pending issues on XMPP module [+] Test SMTP module on a mail server. [+] Create a basic Twitter module. [+] Create basic documentation of what was done during gsoc. As always, you can check what's been done on [0]. Have a nice weekend! [0]: https://github.com/ileiva/gettor/tree/master/src Best, -- israel

1 0

[GSoC] HTTPS Everywhere Secure Ruleset Updater Report
by Red 01 Aug '14

01 Aug '14

Hello everyone! Sorry about the fact that I haven't made a report in a few weeks. It's been a busy time for me. With that said, I have been getting quite a bit of work done on my project to build a secure ruleset updating mechanism for the HTTPS Everywhere Firefox browser extension. In my last report, I talked about the fact that I had been struggling with finding an appropriate solution to the problem of generating an appropriate signature on (the digest of) the update information provided by an update.json file. The problem was brought to some other core developers and it was decided that we would use an existing tool included in recent versions of the NSS tools. Since then, I have been working to integrate my updater into the existing HTTPS Everywhere codebase, which had involved quite a bit of refactoring. I have succeeded in getting the mechanism functional in the extension and have also taken care of keeping the master branch I was working off of up to date. This means that my feature will be able to be pulled into the newly released HTTPS Everywhere 5.0 development release as soon as it's been even more thoroughly tested! I am once again having an issue with signature verification. My mentor, Yan, had found a method of (as described above) using NSS tools to generate a signature that the Mozilla XPCOM component designed to do so could understand and verify. I have not been able to successfully repeat this process in a way that produces a signature that my ruleset updating mechanism has been able to verify the authenticity of the signature produced. The good news is that once this issue is resolved, the feature should be working just right and all that will remain will be to: 1. Add some elements to the UI to configure the updater. 2. Reset some preferences that were provided defaults for testing purposes. 3. Add another simple test to the ruleset update authenticity check to verify that the source URL is an EFF domain. I don't anticipate that these will be difficult changes at all. You can follow my progress by watching my fork of the repository on github and keeping an eye on the branch I am developing: https://github.com/redwire/https-everywhere/tree/rulesetUpdating As always, constructive feedback and ideas are always welcome! Thanks, Zack

1 0

Orbot & Orfox - GSoC bi-weekly report 5
by Amogh Pradeep 01 Aug '14

01 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Status Report 5 August 1st, 2014. Things I did the past couple of weeks: 1) Trying to fix leaks: After finding out that the browser has a dns leak, I went ahead and tried to look for the causes of this leak and came across https://bugzilla.mozilla.org/show_bug.cgi?id=942652 , which stated that not all parts of the browser use the proxy settings. This may or may not be causing the leaks but it is something that has to be fixed for sure, hence I'm trying to get advice on how to go about it. 2) Stripping out the unnecessary parts of fennec: This is something that I have started working on but things seem to be a little harder than I expected, but I'll keep at it. 3) Contributing to Mozilla: As we are using the fennec browser, I felt like helping the Mozillians a bit and hence I worked on a few bugs there and landed about three of them. More to come: - - Trying to fix the dns leak. - - Helping out Mozilla more. - - Working on Orbot a little. -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJT2/5NAAoJELm/SSKdtjUk6/AH/j8GnaMtK1bG7HW78g5p26DU MzVjn/QVDkjTpX0hsFeWzZ9k3vzRWHF5SI2QUFWQCaezTfyJa0WLhj2dpQvLGqVQ y7Nymx+klyNu1Tm/nQt20Hxn7fH04RVdfB+8DmXnp6f/Qerubqqeusw8JvBBh8HX ErhYDrmcAjwRpz7ZOimvO/yMGSfxjPbtcEO+27CSuhXnApckjL0FxFo/T46Kzc4b aPLGZp/oLJ50ThMOCEtb7ZH0gzBmX9EO37vVcZIeB0qMadqTs6PEi77/gHLh+jvB IQ20YRUDTIktG12gDS2/bvQBdroGQFc2m4aOVieSJ6izVV4uyE8qRUgcjjYok0w= =XgSw -----END PGP SIGNATURE-----

1 0