tor-project

tor-project@lists.torproject.org

16 participants
2324 discussions

GSoC 2017 - Crash Reporter for Tor Browser: Report #2
by Nur-Magomed 23 Jun '17

23 Jun '17

Hi everyone! This is my bi-week status report for GSoC project "Crash Reporter for Tor Browser". Project repository is available on GitHub [1]. # Crash Reporter Client: - added feature: never keep crash reports on disk; - working on blacklist feature (for fields that shouldn't be in reports). # Server side (Mozilla Socorro adaptation): - now working on local run. # What's next Crash Reporter Client isn't ready, but I've started work on server side, while I'm waiting for decisions about what data fields in reports are private[2] and may be about UI design changes. Thanks, Nur-Magomed [1] https://github.com/nmago/tor-browser [2] https://trac.torproject.org/projects/tor/wiki/doc/crashreporter#Analysisoft…

1 0

GSoC 2017 - anon-connection-wizard: Report #2
by iry 22 Jun '17

22 Jun '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello everyone! The following is my bi-week status report for the anon-connection-wizard project. # anon-connection-wizard development ## features implemented - - implemented edit mark approach - - added a help button on proxy page - - implemented torrc_page ## feature improved - - proxy password masked - - minor GUI changes - - update assistance message - - update URL for obtaining bridges ## links - - pull request[0] - - detailed discussion[1] # Other related work ## torrc.d preparation torrc.d[2] has been implemented in tor-alpha. Here is some preparation work [3]. ## Discussion on torrc output line related to obfs4 - - detailed discussion[4] # Next step ## request a parsing include in Debain configuration file ## Implement other features - - anon-connection-wizard will use torrc.d style soon - - figure out if torrc_page is sill necessary - - continue polishing anon-connection-wizard and implementing new feature s Thank you! Best, iry [0]: https://github.com/Whonix/anon-connection-wizard/pull/5 [1]: http://forums.kkkkkkkkkk63ava6.onion/t/graphical-gui-whonix-setup-wizard - -anon-connection-wizard-technical-discussion/650/258 [2]: http://forums.kkkkkkkkkk63ava6.onion/t/graphical-gui-whonix-setup-wizard - -anon-connection-wizard-technical-discussion/650/255 [3]: http://forums.kkkkkkkkkk63ava6.onion/t/torrc-d-is-comming/4041 [4]: http://forums.kkkkkkkkkk63ava6.onion/t/should-obfs4-have-the-managed-lin e/3991 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZTEbcAAoJEKFLTbxtzdU8y6gP/RLClcej3cyVRXKulGcvU2KD DYOwq9dHSf1G4PVW2de67/ALYI00GhZAzWnN5XM0ogMPsGoQCF7tJlRaahr0+nFA SfkLEZYMOy78ChQoouT5pfOMGDYcbAJ0P3KLesH66L7pls8HekMXYoi5eQOIERur WRubV8VVrcQ9Xo5zdVNdsWaeupUL+64dlxcb0b9fcfE5Wqr/0XsMPVXn5aZK2nzx 9VwO593dVPKTa9qC5nqQU+FNfYO1AQvppK6korsXv4nd9IYOWq2isLPIVecL1JOF ShD2X8b3/ctT3dFdw32rdq4EHZo3Eyg1ZgDN0YtVscPOngNxmokcz+1AyZrP6x3K 6Jsk+zHs31zeAuIc/JUeFiBAWNjpqu8ML2K8T1Ijkgijl2GwgsMAvY33LD6Z1zFP XOP9Y7qfltv19xEX364qCzPdNGdM76t3z+9jexhrRudBEG8fkJqK3RSEhekkt9PQ Pcsrs/ptq324j01yubiT3WKPnTndT2NsGGsQS3w3+uPfAY+xHmzirGULbTHd2DmX aCUayR4r+u8gr2lG+3TaCKnhi0lgf2t8rh7MAgtQ3WafHBPYk3pWuZObZEvmYn/w vnqOSIGynYKdSCsejQ8/vU8aKH1oMfnLUKzlpCyKpKjLlspkKFtMzRJ6sSuGIxqY UlyJ4Kq4rmaUTs91EImR =s9r8 -----END PGP SIGNATURE-----

1 0

FYI: Service Announcement - cymrubridge02 - obfs4
by Sina Rabbani 21 Jun '17

21 Jun '17

Dear Tor Project, Our operations team is currently investigating a network event. cymrubridge02 maybe experiencing an outage, and I expect the service to resume shortly. > https://atlas.torproject.org/#details/8F4541EEE3F2306B7B9FEF1795EC302F6B84D… I will send another update if this issue is not resolved within the next 2 hours. All the best, Sina -- Sina Rabbani | Systems Engineer | Team Cymru, Inc. srabbani(a)cymru.com | 0x53B422A8 | http://www.team-cymru.org/

1 1

Network team meeting notes, 19 June.
by Nick Mathewson 19 Jun '17

19 Jun '17

Hi! Our meeting log is here: http://meetbot.debian.net/tor-dev/2017/tor-dev.2017-06-19-17.00.html and our pad is copied below: ====== Network team pad, for 19 June Meeting (or 20 June, for those in UTC+5 or later) Things we should talk about: * What's blocking 0.3.1 bug fixes? * How are v3 hidden services going? * Should we try to get everyone to a) get a user on hiro's oniongit and b) get everyone to at least use for code review instead of gitlab.com? (ahf) * review-group-18 now exists! Please assign yourself as reviewer for some tickets. Tasks for after the meeting: * nickm: Find somebody to attend to each non-assigned 0.3.1.x ticket * Everybody: review everything in review-group-18 * somebody: update wiki (https://trac.torproject.org/projects/tor/wiki/org/process/TorOnTrac) with updates from http://5jp7xtmox6jyoqd5.onion/p/trac-hygiene teor: Last week: * Deployed PrivCount 1.0.1 on a few relays to check our previous results * Worked on PrivCount HSDir Upload (v2 & v3) Statistics (thanks for the privcount tags on trac, nickm!) * Added chutney hidden service network with different numbers of intro points #22599 * Found out that chutney doesn't support Hidden Service client auth #22646 * Tracked down some of the zstd issues #22502 and children This week: * Finish Implementing & Testing PrivCount HSDir Upload Statistics * Start planning Montreal travel * Start Implementing PrivCount HSDir Download Statistics dgoulet: Last week: * Wilmington Meeting This week: * I'll be at the DRL meeting in Montreal for the next 3 days (19th-21st) so expect communication delays on IRC/Email. * My focus will be prop224 as the 0.3.2 merge window has opened. A series of branch will get into needs review this week for both nickm and asn. Mike: Last week: * Wilmington This week: * Catch up on email, paperwork * Put finishing touches on Prop254 implementation * Maybe start work on torrc options needed for Prop247 prototype ahf: Last week: * Wilmington Meeting. This week: * Analyze log files to extract information on whether our sponsor4 efforts have reduced directory bandwidth usage. * Look into LZMA mprotect() issue. * Look into Teor's Zstandard bugs. * Finish the changes from prop #278 to dir-spec.txt asn: [Just made it back home but jetlagged. Unclear what my state will be during the meeting hours] Last week: - Attended network team hackfest. Thanks to everyone! This week: - Catch up with the backlog that accumulated during meeting - Start reviewing remaining prop224 service-side code - Work on prop247 simulator - Revise prop247 based on meeting discussions - Meeting blog post (might delay to next week) haxxpop: - Took a look at post quantum crypto :D (especially lattice-based) - Review a bit of asn's prop224 client side code (now it's dgoulet's, I think) This week - something of prop224 catalyst: Last week: * Wilmington meeting * Opened some tickets to follow up from testing session in Wilmington: #22635 #22636 * Looked at #22619: we don't seem to be testing SessionGroup at all? This week: * Review komlo's pending changes to CodingStandards.md * Follow up on more testing-related things * Look at the interaction of #12931 with other PT key=value escaping issues * Give more feedback on #7869 now that 0.3.2 merge window is open * #22619 is tricky; the config validation fix should probably go into 0.3.1 but making sure we have test coverage for the actual functionality of SessionGroup= is not a small task * Try out calltool * Try out oniongit * Jot down notes about Wilmington logistics pastly: last week: - Wilmington. Create name --> face dictionary - Learned about what Tor wants before merging KIST - +1 LDAP account - +2 gitweb.tp.o repos - help setup privcount deployement this week: - Do merge-kist-into-tor things, like ... - oh --enable-gcc-warnings is a thing and says I suck - comments comments comments - tor proposal maybe - unit tests tests tests later: - KIST code develivered to Tor in 3w or less (hopefully!) - dgoulet will help review/merge KIST, correct? Where would dgoulet like to do that? gitlab? oniongit? nickm: Last week: * Wilmington! * more ticket triage! * work on big list of ALL the attacks that need research * Try to match developers to sponsored work. This week: * Just opened 0.3.2.x. * Just opened review-group-18. * Work on fixing 0.3.1.x bugs * Work on 0.3.2.x code reviews and merges * Remind people that 0.3.1.x bugs need attention. * More bug triage in Unspecified and 0.3.2.x. * Put the wilmington stuff I did online. * Maybe, sponsor4 followup planning * TBD isabela: Last week: * half wilmington! This week: * work on invoices, reports (organizing NSF ones and sponsor4 may one (late this month). Also will update the launcher brief, havent got a chance to do that yet and I am super late with it :( * Working on new proposals - modularization one (on that I think the driving car for the pitch should be it will help app devs have Tor build with their apps) Sebastian: virtually attended Rust session. Please ask Rust questions if there are any. Otherwise busy atm Yawning: Unsubbed from the network-team list. Because I'm not actually doing anything or contracting with tor at the moment.

1 0

Job Opening - Browser Developer!
by Erin Wyatt 16 Jun '17

16 Jun '17

Hey Everyone! We’re super excited to announce a new job opening for a Browser Developer! The job description is pasted below, is attached in PDF format, and can be found on our website at https://www.torproject.org/about/jobs-browserdeveloper.html.en. Please help us spread the word by posting, forwarding, tweeting, etc. Thank you! :) Cheers, Erin Wyatt HR Manager ewyatt(a)torproject.org GPG Fingerprint: 35E7 2A9F 6655 45F9 2CB6 6624 BA0C 9400 F80F 91CE June 15, 2017 The Tor Project is looking for Browser Developer (C++ and Javascript)! As a browser developer, your job would be to work closely with other members of the Tor Browser development team on C++ patches to our Firefox-based browser, writing new APIs, altering functionality for privacy and security, and making improvements to our collection of Firefox add-ons (JavaScript code). Being a Tor Browser developer includes triaging, diagnosing, and fixing bugs; looking for and resolving web privacy issues; responding on short notice to urgent security issues; and working collaboratively with coworkers and volunteers to implement new features and web behavior changes. We also need help making our code more maintainable, testable, and mergeable by upstream. The person in this position will also review other people's code, designs, and academic research papers to make suggestions for improvement. This is a full-time position. Required Qualifications: · Experience in C++ (and ideally, JavaScript). Five years of C++ experience is probably necessary for the level of expertise we want, though some of these years can be replaced with other Object Oriented Programming and/or C experience. If you meet this level of experience with C++/OOP, JavaScript can be learned on the job. · Possess a solid understanding of issues surrounding secure C++ programming and reference counted memory (at least to the level of avoiding issues). · Be comfortable diving into new, unfamiliar codebases, looking for ways to alter and augment their functionality in specific, goal-oriented ways. · Be familiar with web technologies and how the web works, especially the same-origin model and web tracking. · Willingness and ability to justify and document technical decisions for a public, world-wide technical audience. · Be comfortable working remotely with a geographically distributed team. · Experience interacting with users and other developers online, including experience being confronted with differing ideas and opinions (not always in a nice manner), while maintaining a high level of professionalism. · Comfort with transparency: as a non-profit organization who develops open source software, almost everything we do is public, including your name (or at least your business name) and possibly salary information. Preferred qualifications: · Familiarity and/or experience with writing add-ons and/or patches for Mozilla Firefox or other web browsers. · Familiarity with compiling software for the Android platform. · Familiarity with Firefox's internal architecture, including its use of multiple processes and sandboxing. · Be intensely creative yet also ruthlessly pragmatic in your thinking. · Possess knowledge/familiarity of probability, statistics, and information theory. · Know enough about networking to be able to visualize what HTTP 1.1 looks like on the wire while encapsulated within Tor's network protocol. · Experience working with distributed (remote) teams across different time-zones with people of differing skill levels over multiple mediums, including email, instant messaging, and IRC. · Open-source experience: contributed significant chunks of code to multiple open-source projects in the past. · Familiarity with distributed version control systems, including Git. · Genuinely be excited about Tor and its values! For a more detailed understanding of the full breadth and depth of the work you'd be doing, have a look at The Design and Implementation of the Tor Browser, especially The Design Requirements section at https://www.torproject.org/projects/torbrowser/design/#DesignRequirements. Other notes: Academic degrees are great, but not required if you have the right experience! 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. 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. 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. The Tor Project, Inc., is an equal opportunity, affirmative action employer. The Tor Project, Inc., is an equal opportunity, affirmative action employer. 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, 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!

1 0

Notes from June 15 2017 Vegas team meeting
by Karsten Loesing 16 Jun '17

16 Jun '17

Notes for June 15 2017 meeting: Arturo: 1) Attended the ISC Project Global Workshop in Washington D.C. with Maria (25th & 26th May) where we facilitated the following sessions: - 90-minute OONI demo - Contributing to test lists & using data from OONI Explorer - Measuring internet blackouts 2) Updated the Cuba, Lesotho, Zimbabwe and Azerbaijan test lists 3) Wrote a blog on our findings on recent censorship events in Egypt (we hope to co-publish this with Access Now) 4) Facilitated OONI community meeting on IRC (and Slack) on 23rd May 5) Published Indonesia report 6) Deployed a beta of probe orchestration and preparing for releasing part of probe orchestration as part of the upcoming ooniprobe mobile release due end of month. Georg: 1) Finished our switch to the ESR52 train with the release of Tor Browser 7.0.1/7.5a1; dealing with bug reports 2) Picking up Sponsor4 work not related to ESR52 transition (everyone on the team knows the big items they are supposed to work on in the coming weeks) 3) Working on the browser developer job posting Alison: 1) Just returned from vacation. 2) Pushing out membership policy proposal on Monday. 3) My speaking engagements this week: TA3M, KPFT Houston 4) Otherwise, just playing catch up from my week off! Shari: 1) update on board meeting 2) update on strategic planning 3) I'm in San Francisco for EFF board meeting Karsten: 1) Reminder: notes go to tor-project@ 12+ hours after the meeting, unless there are objections. 2) Working on metrics-lib releases 1.9.0 and 2.0.0 this week and the next for last remaining Sponsor X deliverable, ignoring pretty much everything else. Isabela: 1) Job post for TBB team is about to go out - starting drafting others after that. 2) Organizing NSF work with Roger and network team (today at Wilmington! had other meetings yesterday too) 3) sponsor4 may report / invoices updates to brad / following up on payments for contractors and other small things 4) trying to finish 2017/18 update / finish tor launcher feature brief update based on june 2nd meeting 5) Hiro is pretty much done with the blog (just missing applying a new layout that ux team is creating) - next step will be to figure out the trac and gitlab situation to know how to move forward. I am also working on collecting new tasks for her. 6) Linda is working on the wireframes for tor launcher (manual flow based on her paper suggestions) - she is also working on improvements on blog post design/experience and on website redesign follow ups. 7) randomly helping the new peeps on different small tasks and trying to get the onboarding wiki page done / Erin has been busy too, but we are in touch and keeping notes on what else we have to add to this page based on questions coming from tommy and stephanie

1 0

New blog deployed
by Silvia [Hiro] 16 Jun '17

16 Jun '17

Hi everyone, The new blog has been deployed and is now living on https://blog.torproject.org as before. If you find any bugs or issues please add to the master ticket: https://trac.torproject.org/projects/tor/ticket/22013 Talk soon, -hiro/silvia

9 13

Damian's Status Report - May 2017
by Damian Johnson 15 Jun '17

15 Jun '17

Later than I'd like but oh well. Lot of great stuff! http://blog.atagar.com/may2017/

1 0

OONI Team status report May 2017
by Arturo Filastò 15 Jun '17

15 Jun '17

# OONI Monthly Report: May 2017 The OONI team made steady progress in May 2017. We released the beta version of our probe orchestration and, in collaboration with Sinar Project, we published a new research report on "The State of Internet Censorship in Indonesia". We also updated test lists in collaboration with our partners, and we started organizing OONI's upcoming Partner Gathering. ## Beta release of probe orchestration We made two beta releases of the probe orchestration backend: https://github.com/TheTorProject/proteus/releases/tag/v0.1.0-beta.2. The probe orchestration client code is being integrated inside of v0.7.0 of measurement-kit here: https://github.com/measurement-kit/measurement-kit/pull/1250. This beta version of the backend is currently deployed (https://github.com/TheTorProject/ooni-sysadmin/pull/112) on staging machines and we are in the process of testing it in preparation of including a subset of orchestration inside of the next version of ooniprobe-mobile. The feature-set included in the current beta of the probe orchestration is the following: * Support for clients to register for receiving orchestration messages with a password * Authentication for orchestration clients and administrators * Support for updating metadata of probes via authentication * Support for sending push notifications to iOS (Apple Push Notifications) and Android (Firebase Cloud Messagging) devices * A web interface for administrators that allows them to: - View the currently registered clients - View the currently scheduled jobs - Add new recurrent measurements based on the target probe In the first integration in ooniprobe-mobile we plan to only support probe registration and metadata update. This will allow us to send visibile push notification to send useful information messages to users, but without the full orchestration workflow. ## Research and improvements to reducing fingerprintability of ooniprobe We did a bit of research documenting what we are currently doing to reduce the fingerprintability of ooniprobe and what we could do better. As a result of this research we also added support for randomising the order in which URLs are tested (in ooniprobe desktop) to further reduce the fingerprint an ooniprobe scan has as well as improve the accuracy of measurement: https://github.com/TheTorProject/ooni-probe/pull/758. ## Publication of research report In collaboration with Sinar Project, we published a new research report titled: "The State of Internet Censorship in Indonesia". The full report can be found here: https://ooni.torproject.org/post/indonesia-internet-censorship/ We also published a summary of the report on the Tor blog: https://blog.torproject.org/blog/state-internet-censorship-indonesia ## Updated test lists In May 2017 we added URLs and updated the following test lists in collaboration with partners: * Iran test list: https://github.com/citizenlab/test-lists/pull/161 * Cuba test list: https://github.com/citizenlab/test-lists/pull/170 * Venezuela test list: https://github.com/citizenlab/test-lists/pull/162, https://github.com/citizenlab/test-lists/pull/158 * Egypt test list: https://github.com/citizenlab/test-lists/pull/164 ## Organizing upcoming OONI Partner Gathering We worked on logistics pertaining to the organization of OONI's first Partner Gathering, which will take place on 10th & 11th July 2017 in Toronto. ## Outreach and community engagement ### Events We presented OONI at the following events: CryptoRave (5th & 6th May 2017) We presented OONI and co-facilitated a workshop on test lists ("Listathona") with Coding Rights at CryptoRave. More information can be found here: https://ooni.torproject.org/post/ooni-cryptorave-2017/. Tor Meeting at the Hacker Club Garoa (11th May 2017) Our team member in Brazil also facilitated an OONI session at the Hacker Club Garoa in Sao Paolo (https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Proje…). Open Source Conference Albania/OSCAL (13th & 14th May 2017) We presented OONI through a 1-hour talk titled: "Free & Open Source Software for a Free & Open Internet". More information can be found here: https://eventyay.com/e/ecc2001a/schedule/ ISC Project Global Workshop (25th & 26th May) We facilitated the following sessions at the ISC Project Global Workshop in Washington D.C: * 90-minute OONI demo * Contributing to test lists & using data from OONI Explorer * Measuring internet blackouts ### Community meeting We hosted our monthly community meeting on https://slack.openobservatory.org/ on 23rd May 2017. As part of the meeting, we discussed filtering techniques for OONI Explorer, as well as methods for tracking internet shutdowns on mobile networks. ### Article We wrote and published an article about ooniprobe for Coding Rights' Antivigilancia newsletter: https://antivigilancia.org/es/2017/05/ooni-descubriendo-la-censura-en-inter… ## Press coverage An article about OONI was published on Motherboard: https://motherboard.vice.com/it/article/come-tracciare-la-censura-di-intern… ## Userbase In May 2017 ooniprobe was run 70,218 times from 1,905 different vantage points across 162 countries around the world. This information can also be found through our stats here: https://measurements.ooni.torproject.org/stats ~ The OONI team.

2 1

GSoC 2017 - Crash Reporter for Tor Browser: Report #1
by Nur-Magomed 14 Jun '17

14 Jun '17

Hi everyone! This is my report #1 for the "Crash Reporter for Tor Browser" project. At the beginning I would like to apologize that I being late and delayed e-mail. # First 2 weeks work was focused on following: 1) Build Tor Browser with Crash Reporter I successfully built Tor Browser with Crash Reporter in, tested crashes and it works fine. Browser repository could be found at GitHub [1]. 2) Make crash reports more anonymous Most of my last work was focused on the analysis of data fields that crashreporter collects. I had discussions in IRC #tor-dev with mentor and also I created wiki-page for the analysis [2]. The next stage is creating final blacklist of fields (according to analysis), that we must not send. If someone has ideas about privacy of data fields [2], please don't hesitate and contact with me or add in wiki-page. # What's next The next week work is focused on Crash Reporter client: > UI - make it easy to understand for user "what's going on" when crash happened; > Deleting reports after crash report is sent. Thanks, Nur-Magomed [1] https://github.com/nmago/tor-browser [2] https://trac.torproject.org/projects/tor/wiki/doc/crashreporter

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project