tor-project

tor-project@lists.torproject.org

17 participants
2326 discussions

Network meeting notes, 1st June 2020
by Gaba 01 Jun '20

01 Jun '20

Hi! Network meetings are still happening every Monday at 1700UTC on #tor-meeting in irc.oftc.net We had a meeting on June 1st and here are the logs and notes. log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-01-17.00.log… pad: https://pad.riseup.net/p/tor-netteam-2020.1-keep Content of the meeting pad: == Network meeting pad! == Next meeting is at Monday 1 June 1700 UTC on #tor-meeting on OFTC. June Schedule: * Monday 1 June 17:00 UTC * Monday 8 June 17:00 UTC * Monday 15 June 17:00 UTC Welcome to our meeting! We meet each month at: Mondays at 1700 UTC On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the tor-project mailing list archive for older notes.) 23 March: https://lists.torproject.org/pipermail/tor-project/2020-April/002804.html 1 April - 4 May: we skipped meetings while transitioning TPI == Stuff to do every week == Let's check and update our roadmap: What's done, and what's coming up? Any change? All the trac tickets for the roadmap are in the team's page: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam S27 - Asn & Dgoulet - ends at the end of May S28 & S30 - Continue after October - Ahf S55 - Nickm S69 - Nickm - ends at the end of May Non sponsor stuff DoS defenses = Dgoulet + Asn Library Size reduction = Ahf + Dgoulet sbws = Ahf + Juga Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Go over our 0.4.4 status page at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… . (If maint-0.4.4 were released as stable tomorrow, what would we regret?) == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases. * Check other's people call for help in their entries. Volunteers need help. Please help them when you are around. Maybe we should have times of day when different people are responders, and expectations of who helps. ------------------------------- ---- 1 June 2020 ------------------------------- == Announcements [please date] == == Discussion [please date] == [June 1st] Who is taking the s55 tickets owned by teor? - nick and david https://trac.torproject.org/projects/tor/query?owner=~teor&status=accepted&… - What to do with proposals? - discuss each one in Monday meetings. === Active Proposed Policies === * Pull Request Guidelines (stalled) === Design proposals under discussion === 315: require more fields in directory documents (still waiting [6/1]) 316: flashflow (asn and nickm are reviewing, should schedule discussion with pastly. [5/18]) 317: dns (under discussion on ML [5/18]) 318: limit protovers (waiting for more commment; needs discussion [6/1]) 319: wide everything (nick replied on ml; waiting for more discussion [6/1]) 320: tap out again - Do we have a consensus to replace this with a "deprecate v2 onion services" proposal? If so, who writes it? [6/1] protover rethinking (teor's email to tor-dev) (nick needs to reply [5/18]) 321: happy families (need feedback [6/1]) 322: dirport linkspec (need feedback [6/1]) == Recommended links == == Updates == Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! Nick: Week of 25 May (planned): - Actually taking monday holiday off; brain is fried and a day might help me. - Finish walking onions proposal; last week. - review and merge in general - FINALLY read and reply to prop316? - Try to make a plan for protovers? Week of 25 May (actual): - Finished walking onions proposal - Review and merge a bit. - Respond wrt other proposals - Send out proposals 321 and 322. Week of 1 Jun (planned): - Send out walking onions proposal once copy-edit is done. - Ramp on on S55. - Catch up on all emails - Catch up with all review/merge - Finish triage! - look at jenkins status - can I fix coverity? if not, open a ticket. - opine on gitlab/trac stuff - advance proposal discussions - summarize code-format status, ask for team decision. ahf (afk today due to public holiday): Week of 25/05 planned: - Look into how we can start + connect to the Tor process in Fenix. - Onion-Location docs. - Get merging to tor.git. Week of 25/5 actually: - Fenix and OrbotService integration. - Onion-Location docs with Anto. Week of 1/6 planned: - Gitlab session at all hands. - Continued Fenix work. asn: Week of 25/05 (actual): - Network team work (reviews / merges / ticket work) - Catching up with email backlog. - Some work on token stuff. - Rebooting PoW work. - Spent time taking care of a personal bureaucracy. Done with this phase; will have some more to do in 10 days. Week of 01/06 (planned): - More work on PoW. - More network team work. jnewsome: Week of May 4 (actual): - Some LD_PRELOAD behavior investigation to guide shadow-Phantom design decisions - Added more tests covering next-to-be-implemented shadow-Phantom syscalls - Mentored/reviewed a volunteer PR - Kickoff OnionPerf meeting Week of May 11 (planned): - Start digging into OnionPerf - Start familiarizing myself with Shadow *usage* for Tor simulations - tor-project@ Shadow update email Week of May 11 (actual): - Worked on improving Shadow logging framework - Helped volunteer get their PR to improve tests into mergeable shape and merged - Started poking at OnionPerf Week of May 18 (planned): - tor-project@ shadow update email - finish logging improvement PR - More digging into OnionPerf. #33974: update to tgen 1.0 \o/ pastly: Week of 18 May (planned): - Finish bones of external FlashFlow repo (python?) to control tor clients that perform FF measurements - Finish bones of little-t tor changes s.t. measurement can be performed - Discuss FlashFlow with network team devs as they have questions c: Week of May 25 (planned): - close up work on #33609 - get started on other s55 tickets, potentially knock out 'easy' ones first and take it from there - update https://trac.torproject.org/projects/tor/wiki/doc/gsoc with my information -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Anti-censorship meeting notes, 28 May 2020
by Philipp Winter 28 May '20

28 May '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-28-16.00.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday May 28th 16:00 UTC Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == * Our anti-censorship roadmap: * Our roadmap consists of a subset of trac tickets on keyword #anti-censorship-roadmap-2020 * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proj… * Tickets that need reviews: from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep == Announcements == * == Discussion == * S30 UX work - https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * O3.1 (Research different scenarios of how human rights defenders experience censorship) * A1 - Develop Tor user personas as a tool to understand users’ contexts and mental models. - ticket #32811- in progress, Duncan is back and we are collaborating on this. I'm planning to involve Maria from OONI for reviewing it as well. * A2 - Define which censorship scenarios we are going to address.- first approach in the link * A3 - Use Tor user personas to define user flows that will empower human rights defenders to effectively circumvent censorship based on the scenarios identified above.- TBD * O3.2 (Design the flow of how our users can bypass the scenarios of O3.1) * A1 / A2 * User flow part 1: User learns they are under censorship. Create mockups with different solutions on how to notify Tor Browser users about detected censorship. * User flow part 2: Once censorship is acknowledged by the user, we then guide them on how to bypass the detected censorship. Create mockups with different solutions on how to better guide our users to bypass censorship. * I'm not sure what is the best ticket to drop this. I've been working on this, and I want to share it with you so we can start thinking about what we want to do in Tor Browser for this sponsor and with this scope. You can make comments! I can move this to any other place if it is useful/better! <--- Can you create a ticket for it? I was waiting for you to start looking at this to create a ticket. It should be a children of #31283. * https://www.notion.so/antonela/S30-UX-0dd8ffd7a46a44f4ae4660d89f95eb51 * Improvements to snowflake quality of life (by prioritizing less restrictive proxies) also opens us up to DoS attacks. Are we okay with this? Ideas on how to mitigate it? (https://bugs.torproject.org/34129 for context) == Actions == * == Interesting links == == Reading group == * We will discuss "Conjure: Summoning Proxies from Unused Address Space" on May 28 * https://censorbib.nymity.ch/#Frolov2019b * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. phw: This week (2020-05-28): * Good progress on #34259; mostly done with fetching OONI data. * Also thought about how one could generalise wolpertinger (after all, it's basically BridgeDB for for censorship measurement clients rather than users). * OONI's backend now has support for wolpertinger's API. * Updated onionperf patch set for #30586 with new requirements. * Filed #34298 for onionperf and wrote a fix. * Reviewed #33434 for onionperf. * Reviewed #34286 for GetTor. * Merged #34154 and #33945 for BridgeDB; released version 0.10.1. * Wrote blog post about new BridgeDB release (may come out today). * Reviewed OTF applications. * Finally got access to our Azure account. * Filed #34318 for BridgeDB. * Helped bridge op figure out why bridge didn't have Running flag -- apparently because IPv6 port was unreachable. * Helped agix get a blog account. * Wrote exitmap module to find exits that resolve non-existing domains. Next week: * Make wolpertinger fetch OONI's test results from S3 bucket. Help with: * cecylia (cohosh): last updated 2020-05-28 Last week: - reviews - worked with Hashik on snowflake proxy for android - did more learning about debain packaging and catching up on #33736 - Wrote some code to demonstrate NAT behaviour discovery (#34129) - started integrating NAT behaviour discovery into snowflake - file an upstream pion/stun PR for support for RFC 5780 - wrote a fix for gettor mailer-daemon loop (#34286) - wrote up a summary for the conjure reading group meeting This week: - finish implementations of NAT behaviour discovery (#34129) - Design a way to use NAT behaviour discovery at the broker - implement NAT behaviour discovery in client and proxies - look at viatsk's work on NAT test suite (#25595) - look at BridgeDB's email responder code and see if there's an uninvasive way to integrate GetTor (#3780) - investigate #33669 - Follow up on discussions of debian obfs4proxy package - translations? - testing snowflake client on android (#30318) Needs help with: - review of #34286 - feedback on #34129 juggy : This week: - Dig into the algorithm for how BridgeDB distributes bridges Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB to write architectural overview Help with: arlolra: 2020-05-07 Last week: - webext repo versioning / publishing #34140, #34126, #34132, #34127 Next week: - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-05-28 Last week: Next week: - check with Kyle about snowflake fingerprinting results - share access to the snowflake broker CDN configuration (#30510) Help with: agix:2020-05-28 Last week: - Worked on patch for #27984 - Read this weeks paper - Get familiar with blog policies Next week: - Further test #27984 & submit patch Help with: - thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with: HashikD: 2020-04-28 Last week: - Established the WebRTC connection. (in Test project) - Fixed the issue with connectoin termination. (in Test project) - Sending some temporary data to test the connection. (in Test project) - Finished #34308 (closed) creating new project - Finished and commented on #34264, #34307 (merge_ready) Next week: - Getting my merge requests accepted and acting up on feedback of code. Help with:

1 0

Metrics meeting notes, 28th May 2020
by Gaba 28 May '20

28 May '20

Hi! Metrics Meetings are happening every Thursday at 15UTC in #tor-meeting in irc.oftc.net Here are the minutes for the meeting of May 28th: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-28-14.58.html And here is the pad notes: ----------------------------------------------------- Agenda Thursday, May 28th, 15 UTC ----------------------------------------------------- OnionPerf project: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor59 Find out why onion service measurements have gotten slower (#34303) How do we catch future '#34303's? Define lower/upper bounds for TTFB/TTLB/circuit build times/etc. in whichever monitoring tool we're going to use. Automatically run OnionPerf instances with newly changed OnionPerf/Tor code. Analyze unusual distribution of time to extend to first hop in circuit (#34257) karsten updates the HK instance to run a #34303-patched tor version to see if #34303 also affects circuit build times. karsten adds measurements to the ticket by Friday evening for dennis_jackson to look over the weekend. Harmonize TTFB/TTLB definitions with Tor Metrics plots (#34215) We agree that it's a good change. karsten merges after the meeting. Split visualizations into public server vs. v2 onion server vs. v3 onion server measurements (#34216) acute reviews this patch. Update metrics-web to only plot "official" data (#33397) We should have guidelines for archiving experimental measurements; like keeping a tarball of the onionperf-data/ directory, a description of the experiment, versions used, etc. In the future we might want to have long-running measurements that shouldn't be plotted on the Metrics website; like different Tor versions or configurations. Having these in CollecTor would be convenient. We should reconsider this when we have these use cases and see what we need. Fix message logging and filtering (#29369) phw picks this ticket. Any review pending to be assigned? Anybody need any help with anything? Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-28-14.58.log… -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Privacy-Friendly web- GSoC 2020
by Aya Hany 26 May '20

26 May '20

Hi there :) I'm Aya, I'm studying Computer science at Mansoura University. I will be working on the "Privacy-Friendly web" project as a part of the GSoC with my mentors Hiro and Antonela. The goal of the project is to make websites work better with tor browser, providing a CSS template based on bootstrap.

2 1

Stem Type Hints
by Damian Johnson 21 May '20

21 May '20

Hi all, I'm delighted to announce that Stem now incorporates type information! For a brief description please see... https://blog.atagar.com/may2020/ Cheers! -Damian

1 0

Outreachy Intern Introduction
by Nicolei Ocaña 21 May '20

21 May '20

Hi Tor Project Team, I'm Nicolei Ocana (IRC: nicoleiocana__), one of the 2020 Outreachy Interns. I will be contributing in Project 1: Help Tor Project support our users along with my mentor Gus (ggus) & the Community Team. I am thrilled to be participating with everybody in helping millions of users protect their privacy, safety, and freedom of expression on the the Internet. Thank you Pili Guerra (pili); I am beyond appreciative for the opportunity to aid in circumventing censorship with you guys!

1 0

Anti-censorship meeting notes, 21 May 2020
by Philipp Winter 21 May '20

21 May '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-21-15.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday May 21st 16:00 UTC Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == * Our anti-censorship roadmap: https://gitlab.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1 * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proj… * Tickets that need reviews: from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep == Announcements == * == Discussion == * Shall we post our monthly report on the blog instead of (or in addition to) the mailing list? == Actions == * == Interesting links == == Reading group == * We will discuss "Conjure: Summoning Proxies from Unused Address Space" on May 28 * https://censorbib.nymity.ch/#Frolov2019b * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. phw: This week (2020-05-21): * Reviewed #27330. * Reviewed and merged #31528. BridgeDB isn't silly anymore. * Wrote a patch for #30586 (onionperf). * Lots of work on wolpertinger. * OONI started using our public endpoint. * Made some API improvements. * Created API endpoint to POST measurements. * Improved authentication thanks to OONI's feedback. * Started working on shim that relays between wolpertinger and bridgestrap. * Filed #34253 and several S30-related tickets. * Set up GetTor email autoresponder test on our monit instance. * Wrote a fix for #34154. * Made some progress on #34260. * Updated BridgeDB translations (not deployed yet though). * Checked in on #33945; looks like BridgeDB's email autoresponder is healthy again. Next week: * Make wolpertinger fetch OONI's test results from S3 bucket. Help with: * #34154 (extend bridgedb's blockedbridges table) * #33945 (fix bridgedb's failed assertion) cecylia (cohosh): last updated 2020-05-21 Last week: - off Monday (public holiday) - worked with HashikD on GSoC tasks - more work on sponsor 28 evaluation - ran a check for STUN servers that support RFC 5780 - started implementing RFC 5780 support for pion/stun (#34129) - some grant writing tasks This week: - Continue work on STUN servers (#34129 and #25591) - More work on reviving the twitter responder in GetTor (#33036, #27330) - look at old GetTor mirrors (#33893) - investigate #33669 - Follow up on discussions of debian obfs4proxy package - translations? Needs help with: - creation of snowflake repo (#34222) from git-admin juggy : This week: - Dig into the algorithm for how BridgeDB distributes bridges Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB to write architectural overview Help with: arlolra: 2020-05-07 Last week: - webext repo versioning / publishing #34140, #34126, #34132, #34127 Next week: - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-05-21 Last week: - helped debug Moat in Tails https://lists.torproject.org/pipermail/tbb-dev/2020-May/001093.html - tried NAT discovery STUN server (#34129) Next week: - check with Kyle about snowflake fingerprinting results - share access to the snowflake broker CDN configuration (#30510) Help with: agix:2020-05-21 Last week: - was held up with university stuff Next week: - Continue work on #27984 & submit/test first patch Help with: - thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with: HashikD: 2020-04-18 Last week: - Learning how to compile the WebRTC library from Google source. - Learning the broker API. - Implementing to test the WebRTC API into a test project. - Getting ICE candidates and forming the SDP on the client-side. (Answer) Next week: -Learning how to format the SDP (Serialize) to send it to the broker and Deserialize the SDP offer from the broker to assign it to the local descriptor of peer connection. - Setting up the project. Help with: - SDP serialization .

1 0

Metrics meeting notes, 21st May 2020
by Gaba 21 May '20

21 May '20

Hi! Metrics Meetings are happening every Thursday at 15UTC in #tor-meeting in irc.oftc.net Here are the minutes for the meeting of May 21st: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-21-15.01.html And here is the pad notes: ----------------------------------------------------- Agenda Thursday, May 21st, 15 UTC ----------------------------------------------------- OnionPerf project: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor59 Update OnionPerf to TGen 1.0.0 (#33974) karsten emails jnewsome about getting access to a testing VM. requirements are not included in setup.py (#30586) acute writes an update on the ticket. Analyze unusual distribution of time to extend to first hop in circuit (#34257) dennis started looking at the analysis and will look more. karsten tries to get two new hosts in Florida and Amsterdam for comparison. Reduce the number of 50 KiB downloads (#34023) karsten comments on the ticket to say that there were no major concerns at the weekly meeting and that we're doing it. Reduce timeout and stallout values (#34024) karsten updates the ticket to say that we agree that this is an improvement, and we're going to do it. Allow users to select Onion Service version to measure (#33434) asn replied on the ticket. Update metrics-web to only plot "official" data (#33397) Remove existing Tor control log visualizations (#34214) Harmonize TTFB/TTLB definitions with Tor Metrics plots (#34215) Fix message logging and filtering (#29369) leaving this here as something to pick up for writing code. Combine multiple analysis files into single data set (#34191) leaving this here as something to pick up for writing code. Python style anarcat suggested pyflakes3 and black acute suggested pylint and yapf phw and jnewsome suggested flake8 as being used in bridgedb and shadow karsten tries out these tools, and we'll discuss them again next week. Reviews (tag with metrics-team if needs review) karsten adds metrics-team to auto-cc for (new) Metrics/OnionPerf tickets. there are 4 tickets that needs reviewer: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

NYC HOPE to nine days
by George 19 May '20

19 May '20

FYI: > > > Greetings, > > While we all want things to go back to normal, the science just doesn't > make that possible. July and August may still seem far away, but there > simply is no way the COVID-19 crisis will be over by then, even in the > best-case scenario. We had planned on waiting until June to make a final > decision, but it's become clear that planning an in-person conference > simply wouldn't be the responsible thing to do. Nothing matters more than > the health and safety of our attendees. Yes, this will be a financial > kick in the teeth for us. But it's one we'll willingly take as the mere > possibility of putting any of you at risk is unconscionable. > > We want to be clear on one important point. Apart from the obvious > disappointment of not being able to host this historic event at a new > venue we were so looking forward to, we want everyone to come out of this > not feeling dissatisfaction beyond that. More on that later. > > This is what we're now looking at: > > We are NOT canceling HOPE. Instead, we are changing what this year's HOPE > will be. > > HOPE 2020 will now be a NINE DAY EVENT, beginning on Saturday, July 25th > and running until Sunday, August 2nd, 2020. Why did we add an entire week? > Because we want some good to come out of this and we believe our community > is in a position to do just that. We all know what we WON'T have without a > physical conference, but let's now focus on what we CAN have with some > imagination and collaboration. That's what the hacker community is all about. > > We intend to have around the same number of talks as we normally do, but > spread out over a much longer period and available for viewing on a high > capacity stream. Those of you who bought tickets will have exclusive access > to the presenters so you can ask questions, participate in workshops, and > interact with other conference attendees. In addition, you will also > receive a conference t-shirt and badge that won't ever be made available to > anyone else. > > We plan on having NINE keynote speakers, again with exclusive Q&A access > for our attendees. > > Participation in HOPE will no longer be bound by visas and worries of arrest > by certain controversial types. So expect a dynamic and varied cast of > characters. It wouldn't be HOPE without that, but now we can REALLY remove > some barriers. > > In addition to ongoing talks and panels, we'll also have workshops for the > duration of the nine day event. Expect everything from lockpicking to > soldering instruction to our infamous ham radio exams. > > For the overnight hours, we're planning on having concerts, DJs, and other > fun stuff. HOPE will remain a 24 hour event, but for nine days! > > All of this has been - and will continue to be - a daunting task. The > COVID-19 pandemic has affected all of us in varying ways. The continued > survival of 2600 was quickly put into doubt as our distributors stopped > paying us, bookstores with our issues in them shut down, and new issues > were left in loading zones. We've lost more than half a year's income at > last count and have had to stop getting paid in order to continue to > survive. Making this year's HOPE a success is really the only way we can > come through this. > > As mentioned above, we don't want anyone to feel extra unhappy because of > this. If you want a refund, we will give you one. But with all of the > losses we've already suffered, we won't be able to continue existing if we > have to issue very many of those. That's why we're hoping we can put > together the best event possible and make this the highlight of our summer > despite all that's happened. > > We are in the process of accepting talk and workshop proposals that have > already been submitted. We will be providing technical support so that > presenters will be able to participate smoothly in a virtual environment. > We are now opening up the submission process to include many more > participants from all around the globe, something we never really had the > ability to do before. We hope to have talks, workshops, and musical > presentations from a truly international community, no longer bound by a > physical presence. > > While we have a dedicated team of volunteers already working on making this > happen, we can definitely use many more, especially as the event draws > closer and becomes bigger. Email volunteers(a)hope.net and let us know how > you think you can help. We're looking for people with experience setting up > and producing live online broadcasts. We are also looking for emcees, > moderators for online forums, and people to fulfill other behind-the-scenes > roles. > > If we get through all of this, we fully intend to hold a physical HOPE in > 2021 (the first odd-year HOPE since 1997). This will also enable us to > continue publishing once bookstores start opening again. All of this depends > on our hacker spirit getting us through the toughest times we ever could > have imagined. And if you share our enthusiasm over what this new incarnation > of HOPE will mean, this summer will indeed be one to look forward to. > > Stay safe. > > The HOPE Staff > _______________________________________________ > hope-announce mailing list -- hope-announce(a)lists.2600.com > To unsubscribe send an email to hope-announce-leave(a)lists.2600.com >

1 0

May 18th Meeting Notes for SPONSOR 58 - Tor Browser Security, Performance, & Usability Improvements
by Gaba 18 May '20

18 May '20

Hi! We are meeting every Monday at 18UTC via voice in a BBB room to coordinate the work related to Sponsor 58, where we are completing the migration of Tor Browser for Android from Fennec to Fenix. You can read more about it at Parent ticket: https://trac.torproject.org/projects/tor/ticket/33664 Wiki page: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor58 If you want to participate in this meetings please send us a message about how to join. The pad we are using is: https://pad.riseup.net/p/_kbebKhZvNcUuqxQL5NV And here are the pad's notes: NEXT MEETING: MAY 25TH AT 18UTC IN BBB Reminder: please own a ticket when you start working on it. Agenda Reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… (any block from last week review, reviews not assigned yet) -> #27105 and #30832 not ready yet but geko will start reviewing it. -> #33932 and #34013 will be taken by ahf. Look at what people need help with. Status updates: GeKo: Last week: - finished all of the toolchain migration for projects already in tor-browser-build and addressed first review comments) (#34187, #33626, #33973, #33564, #33561, #33563, #33558, #33559) - made progress on review of acat's rebase work (#33533) - looked a bit over dependencies we want to keep/rip out (#33939) This week: - wire up geckoview into fenix - update android-components build patch and wire custom one into fenix as well - finish review of acat's rebase work (#33533) Blocked on decision for #33939 acat: Last week: - #30832: Fix tor-browser tbb-tests - Tested fix for https://github.com/EFForg/https-everywhere/issues/19102 - Revised and landed dns leak uplift followup https://bugzilla.mozilla.org/show_bug.cgi?id=1636411 - #34196: Update site info URL with the onion name - Reviews: Bug 34206: Tor Launcher button labels are missing (Firefox 76) Bug 34209: about:tor and about:tbupdate fail to load in debug build of Tor Browser Bug 34164: Tor Launcher hangs with 33533+5 branch Not blocked This week: - Fix intermittent test failure for https://bugzilla.mozilla.org/show_bug.cgi?id=1636411. - Try to run some tor-browser tests in try. - #30832 followup (tbb-testsuite). Alex: Week of 11/05 actually: - DNS proposal and changes being discussed on tor-dev(a)lists.torproject.org. - Sent revised patches for TROVE-2020-001 with Taylor's suggestions included. - Got OnionBrowser to build and reproduced the iOS Tor 0.4.2+ issue. - Done with emails from April. - Review of various patches for tor.git. - Managed to reproducibly compile GeKo's geckoview patches on two devices. - Code review of GeKo's geckoview patches to Tor Browser (#33626, #33973, #33113). Not blocked on anything. Week of 18/05 planned: - Write documentation for `Onion-Location:` for nginx. - Continue to work with the browser folks. - Hopefully nail down the iOS bug. - Thursday and/or Friday is a public holiday here in DK that I might make use of. Mike: Last week - 5/11: - Got TBB building in Ubuntu 'multipass' vms (https://multipass.run/). Is pretty straight-forward - Congestion control, FlashFlow proposal, TorFlow #33871 help, org discussion email - Got diffs of gecko-dev for proxy audit Blocking: - This week - 5/18: - gecko-dev proxy audit sysrqb: Last week - 11 May: Mostly reviewed patches and preparation for 9.5a13 Began #33939 This week: Finish #33939 Release prep for 9.5a13 and reviewing #31918 MAY 11TH Reminder: - please own a ticket when you start working on it. Agenda - Tickets for AHF - 33973 and 33626 - O2.2 with geko - Review ux-team tickets and set timelines -> #33658 is the first issue to solve in June https://trac.torproject.org/projects/tor/query?cc=~&keywords=~ux-team&spons… - Reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&sponsor=… only #30832 needs a review - #33534 is still owned by pospeselr Status Updates: Name: What did you do last week? Anything anybody is block on? What is the plan for this week? Alex: Last week: - Got Fenix compiled on desktop and laptop with Android dev environment. - Moved the build to remote build host. - Started looking at the TB tickets we apply on top of Firefox. - Not blocked on anything, but I am interested in which tickets we should allocate to me. This week: - Look into the build-system patches from GeKo. Test and review. sysrqb: Last week: Tor Browser releases (Some) S58 ticket triage Make progress on setting up replacement Nightly build machine Blocked: No. This week: #33939 - Decide which components of Fenix to rip out, disable, or use Catch up on status of tickets GeKo: Last week: - worked on lots of toolchain tickets and put a bunch of them into review (#33557, #33561, #33626, #33760, #33833, #33973, #34011, #34012, #34013, #34014, testing currently #33801 and figuring out issues in #33563) - I started to look at writing the script for toolchain changes (#34108) - I started to look into #33939 to unblock me but I can't make a decision here alone - I looked into glueing mozilla-beta into fenix/android-components - I looked into fallout from rebasing to mozilla-beta (#34145) and worked around it - review of acat's rebased patches (#33533) Blocked: - Still on a decision for #33939 This week: - finishing #33801 and #33563 - trying to finish review of acat's rebased patches (#33533) - glueing the different components together - setting up missing projects in tor-browser-build (likely android-components) at least acat: Last week: #31918: Rebase and squash mobile and desktop patches #33533: Rebase Tor Browser patches to 77 beta #34125: Fix torbutton proxy api due to change in Firefox 77. #33962: Uplift patch for 5741 (dns leak protection) Started working on #27105: Fix Tor Browser testsuite Blocked: Not blocked, but not sure whether working on #27105 (Fix Tor Browser testsuite) is the right priority, or I should switch to something else. Next week: #27105: Fix Tor Browser testsuite -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project