Hi,
Starting today, July 8th, the Tor Project is running a one month
campaign called #MoreOnionsPorfavor to raise awareness about onion
sites, that is, websites available over onion services.
We recently released a feature called Onion-Location in Tor Browser that
announces to users if a website has an onion site available.
Join us to make a more secure web!
To participate, enable Onion-Location, share your onion site using the
hashtag #MoreOnionsPorFavor on your favorite social media, and we'll
select some onion service operators to receive a Tor swag.
Read our blog post for all the details:
https://blog.torproject.org/more-onions-porfavor
cheers,
Gus
--
The Tor Project
Community Team Lead
http://expyuzz4wqqyqhjn.onion/
Hi!
Tor Browser meetings are happening every Monday at 1800UTC on
#tor-meeting in irc.oftc.net
We had a meeting on July 6th and here are the logs and notes.
Log:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-07-06-18.01.log…
Pad:
http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor…
Contents of the pad for today:
== Tor Browser meeting pad! ==
Next meeting is at Monday 13th July 1800 UTC on #tor-meeting on OFTC.
July Schedule:
* Monday 6 July 18:00 UTC
* Monday 13 July 18:00 UTC
* Monday 20 July 18:00 UTC
* Monday 27 July 18:00 UTC
Release meetings: https://pad.riseup.net/p/tor-browser-release-meeting-keep
Tuesday July 7th 18:00 UTC
(This channel is logged while meetings are in progress.) (See
https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht…
for background.)
Upcoming Releases and other important dates
2020.06.30: 9.5.1 and 10.0a2 - ESR68.10, ESR78.0
Latest Releases:
2020.05.22: 9.5a13
https://blog.torproject.org/new-release-tor-browser-95a13
2020.06.02: 9.5 Stable
https://blog.torproject.org/new-release-tor-browser-95
2020.06.02: 10.0a1
https://blog.torproject.org/new-release-tor-browser-100a1
== Previous notes ==
(Search the tor-project mailing list archive for older notes.)
June 15th -
https://lists.torproject.org/pipermail/tor-project/2020-June/002878.html
June 22nd -
https://lists.torproject.org/pipermail/tor-project/2020-June/002891.html
== What project we are working on? ==
SPONSOR 58 - Tor Browser Security, Performance, & Usability Improvements
Milestone: https://gitlab.torproject.org/groups/tpo/-/milestones/11
Parent ticket:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33664
Timeline: https://nc.torproject.net/s/ow2r6cLgL7Cd9BA
== Stuff to do every week ==
Board https://gitlab.torproject.org/groups/tpo/applications/-/boards
- any change?
Check reviews not taken! How reviews from last week worked? Any
blocker?
https://gitlab.torproject.org/groups/tpo/applications/-/issues?scope=all&ut…
Next release: anybody need help with anything?
-------------------------------
---- 6 July 2020 -------------
-------------------------------
== Announcements [please date] ==
Android release in next day
== Discussion [please date] ==
Applications/Tor Browser wiki page structure -
https://gitlab.torproject.org/tpo/applications/team
== Status Updates == Please update the status in the same place every
week under your name
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.
ahf:
Week of 22/6 planned:
- Trying to minimize myself in the Gitlab stuff for now.
- Need to deal with review backlog.
- Back to doing Fenix + Tor integration.
- Get Tor network extension working on device with TGP sponsorship.
Week of 22/6 actually:
- Got help from Benjamin with certificates and all the Apple
"security" stuff with running your own apps on your own devices...
- Failed at completely detaching myself from Gitlab things:
worked on a few minor issues and the label clean-up.
- Tried to push for some sponsorship for CI for our Gitlab instance.
- Read Mike's congestion pads/mails.
- Got back to Fenix+Tor integration.
Week of 29/6 planned:
- Delete unused labels from Gitlab.
- Try to solve Gitlab#41 with Hiro since it makes working with
GL a bit more frustrating with our git.tpo/gitlab.tpo hybrid setup.
- Do merging/backporting of Tor things.
boklm:
Week of 2020-06-15 (actual):
- Made patches to use rootless containers and was able to do
builds of Tor Browser for windows-x86_64 and osx-x86_64
(tor-browser-build#23631 and rbm#40001). For some unknown reason the
builds based on wheezy are not working.
Week of 2020-06-22 (planned):
- Add some documentation for rbm#40001 and set the patch as
Needs Review
- Improve patch for rbm#32272 to handle Ctrl+C
Mike:
Week of 06/29 (planned):
- Performance funding proposal pre-meeting + funder meeting
- gecko-dev proxy audit
Week of 06/29 (actual):
- Research paper peer review for COSE
- Funding proposal work
- Performance funding proposal pre-meeting + funder meeting
- Congestion control proposal published! finally!
- Misc tor bug replies + spec tweaks
Week of 07/06 (planned):
- gecko-dev proxy audit <-- which #issue is this one? #40017? --gaba
mcs and brade:
Week of June 22nd (actual):
- Rebased & landed “update downloading” patch (upstreaming
tor-browser#28885).
- See https://bugzilla.mozilla.org/show_bug.cgi?id=1642404
- Investigated intermittent test failure for other part of
tor-browser#28885.
- See https://bugzilla.mozilla.org/show_bug.cgi?id=1647313
- So far we have not reproduced the failure.
- tor-browser#33534: Finished reviewing Firefox 75-78beta
release/dev notes.
Week of June 29th (planned):
- tor-browser#33534: Review closed bugs for Firefox 75-78.
- More work on the intermittent test failure bug (Bugzilla 1647313).
- tor-browser#33852 (Clean up about:logins (LockWise) to avoid
mentioning sync, etc.)
sysrqb:
Week of 29 June (planned):
#33939
Unblock any other Fenix work
9.5.1/10.0a2 releases
cpu_features patch uplift
Week of 2 June (actual):
#33939
9.5.1/10.0a2 releases
cpu_features patch uplift (small progress)
Week of 6 July (planned):
#33939 <-- any help needed with it? --gaba
Unblock any other Fenix work
Android release preps and release
cpu_features patch uplift
GeKo:
Week of June 29 (planned):
Finish build of application services
help with releases were fit
Reviews (dev.tpo, O3.2 design for S30, #27105, #30832)
Week of June 22 (actual):
Work on build of application services
help with releases were fit
Reviews (dev.tpo, O3.2 design for S30, #27105)
Week of 6 July:
Finish build of application services
Help with Fennec release
Reviews (#27105, #30832, #33954, #33533 fixups, hopefully branch
based on esr78)
Fix up desktop toolchains so we can switch to nightly builds based
on esr78
blocked by #34432 landing
Antonela:
Week of 29 June (planned):
- Review HTTPS-E Names
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40010#n…
- Work on S58 tickets TBA UI
- Waiting for tbb-dev review in S30 <-- who is reviewing this?
--gaba [I reviewed it, GeKo] [yes, thank you! - A]
https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004
Week of 29 June (actual):
- Work on S58 tickets TBA UI
- S30 / TB 10.0 Connecting to Tor
- Some l10n work
https://gitlab.torproject.org/tpo/community/l10n/-/issues/32602
Week of 6 July:
- Working on S58 TBA UI
Main ticket
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33658
WIP https://marvelapp.com/prototype/783fhfb
- Review
HTTPS-E Names:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40010
Onion Location:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40020
acat:
Week of 29th June (planned):
- Finish tor-browser-bundle-testsuite@40002: Add test for "Add
v3 onion services client authentication prompt" TB patch
- Revise & Rebase #33533 to latest beta and test
tor-browser-spec#40001 process
- Revise tor-browser-spec@40001: Add rebasing process document
- Maybe iterate on tor-browser@33791: Evaluate Firefox tests
- I was thinking of finding the subset of FF tests that pass and
put it in some list/script so that we can run/keep track of it. +1 (+1,
yes, please)
Week of 29th June (actual):
- Finish tor-browser-bundle-testsuite@40002: Add test for "Add
v3 onion services client authentication prompt" TB patch
- Revise & Rebase #33533 to esr78
- Revise tor-browser-spec@40001: Add rebasing process document
- Quick patch for #40020: On a v2 onion page, Onion-Location
with a v3 onion should count as "onion available"
Week of 6th July:
- Revise & Rebase #33533 to 79beta and test
tor-browser-spec#40001 process
- 40010: Improve/Simplify Https-Everywhere Onion Name Implementation
- torbutton@40001: Generate tor-browser-brand.ftl from
brand.properties and brand.dtd
- Iterate on tor-browser@33791: Evaluate Firefox tests
- I was thinking of finding the subset of FF tests that pass
and put it in some list/script so that we can run/keep track of it. +1
(+1, yes, please)
Jeremy Rand:
Week of 29 June (planned):
Look more seriously at what's needed to port the Namecoin
support to macOS/Windows.
Keep working on rebasing Namecoin's patches to Electrum 4.0.0.
Continue working on upstreaming Namecoin's Electrum patches.
Continue talking to NLnet about funding things.
Issue a formal statement from Namecoin about the OTF situation
(hopefully it helps).
Hopefully get my GitLab account sorted out.
Week of 29 June (actual):
Look more seriously at what's needed to port the Namecoin
support to macOS/Windows. (WIP)
Upstream Electrum released 4.0.1. (4.0.0 was skipped for
unknown reasons.)
Merge some upstream code from Electrum 4.0.1.
Various NLnet coordination.
Finish writing OTF statement for Namecoin (not published yet).
I can now login to GitLab (though email notifications don't work
yet here...)
Week of 6 July (planned):
File some GitLab issues about Namecoin support in macOS/Windows.
Work on getting Electrum-NMC 4.0.1 ready.
Work on upstreaming Electrum-NMC patches.
More NLnet coordination.
Publish OTF statement on Namecoin.org.
Maybe figure out why email notifications aren't working for me
from GitLab. <-- notifications were disabled before, they do not work
for a specific project for you? --gaba (Hmm, maybe something was fixed
without me noticing, will try again. -Jeremy)
--
she/her are my pronouns
GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19
Hi!
Network meetings are happening every Monday at 1700UTC on
#tor-meeting in irc.oftc.net. Everyone is welcome to participate in them!
We had a short meeting on July 6th and here are the logs and notes.
Log:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-07-06-17.00.log…
Pad:
http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor…
Contents of the pad for today:
== Network meeting pad! ==
Next meeting is at Monday 29th June 1700 UTC on #tor-meeting on OFTC.
June Schedule:
* Monday 6 July 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.)
15 June:
https://lists.torproject.org/pipermail/tor-project/2020-June/002877.html
22 June:
https://lists.torproject.org/pipermail/tor-project/2020-June/002890.html
== Stuff to do every week ==
Let's check and update our roadmap:
What's done, and what's coming up? Any change?
Board: https://gitlab.torproject.org/groups/tpo/core/-/boards
S28 & S30 - Continue after October - Ahf
S55 - Nickm & dgoulet
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:
Merge requests in Core:
https://gitlab.torproject.org/groups/tpo/core/-/merge_requests
Let's check out 0.4.4 release status and open tickets!
Tickets in 0.4.4.x with no owner.
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
nickm:
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
dgoulet:
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
ahf:
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
asn:
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
== 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.
-------------------------------
---- 6 July 2020
-------------------------------
== Announcements [please date] ==
== Discussion [please date] ==
* Request for update on fallback list (6 July)
=== 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 29 June (planned):
- More S55 work
- 044 work
- Investigate problems building/running with Openssl 3 alpha
(tor#34139)
- Maybe move OSS-fuzz off of openssl 3?
- Write a proposal for packing multiple commands into a relay cell.
- More thinking on congestion control
- Work on stable releases
Week of 29 June (actual):
- More s55 work
- Several 044 tickets
- started proposal for packed relay cells
- Backports with ahf
- Wrote a possible migration plan for gitolite (the easy parts)
Week of 6 July (planned):
- Revise my working checklists, and distribute them?
- Stable releases-- aim for end-of-week.
- Review and merge
- S55:
- Export statistics
-
- 044 work:
- All "must", all "should".
- Some "can"?
- Release packed cell proposal (fitting multiple relay commands
in a cell)
ahf:
Week of 29/6 planned:
- Delete unused labels from Gitlab.
- Try to solve Gitlab#41 with Hiro since it makes working with
GL a bit more frustrating with our git.tpo/gitlab.tpo hybrid setup.
- Do merging/backporting of Tor things.
Week of 29/6 (actually):
- Got rid of all the GL labels.
- Did not solve Gitlab#41
- Learned how to do merging thanks to David.
- Worked on backports.
- Tried to figure out the issue in the 3 \r\n Windows issues.
- Back on Android/Browser stuff.
- Got iOS on-device testing to work for the Tor.framework
network extension.
Week of 7/6 (planned):
- Windows \r\n issues (#33781, #26316)
- Get profiles done on iOS for memory consumption.
- Work on Android stuff with the Browser Team.
- Help if I can with Gitlab#41.
asn:
Week of 29/06 (planned):
- More PoW work
- A look at v3 metrics.
- More OBv3 hackathon. Someone is hacking on distinct descriptor support.
- Need to adapt the gitlab process to using MRs as discussed on Thurdsay.
- A bunch more reviews & merges.
Week of 29/06 (actual):
- Lots of network team reviews/merges/bugfixes work.
- Some v3 metrics work.
- More OBv3 reviews.
- Triaging gitlab tickets.
Week of 06/07 (planned);
- Going AFK on Friday so biggest priority is to finish all
reviews/merges/044 tickets by then.
jnewsome:
Week of June 22 (planned):
- More profiling of shadow/phantom and start work on optimizations
Week of June 22 (actual):
- Ported "interposable libc" patch to centos 7 (our benchmarking
platform).
This version of glibc took a bit more work.
- Switched ptrace-based shadow/phantom to use PTRACE_SYSEMU,
substantially improving performance.
Week of June 29 (planned):
- Fix https://github.com/shadow/shadow/issues/853
- Help with shadow/phantom benchmarking and optimization as needed
- Work on shadow test code-coverage measurement strategy
Week of June 29 (actual):
- Fixed https://github.com/shadow/shadow/issues/853
- Got Rust + C code-coverage working and in our CI. Still
cleaning up.
- Proof-of-concept implementation of shadow/phantom optimization
for greatly reducing memory marshalling overhead
Week of July 6 (planned):
- Get code-coverage PR cleaned up and merged
- Implement phantom memory-marshalling optimization "for real"
and merge
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
Week of May 25 (actual):
- #33609 ready for review
- started hunting down and working on other Sponsor55-can and
-must issues
- talking in #tor-project about wiki
Week of June 1 (actual):
- opened and made #34381 ready for review
- IPv4 part of #32888
Week of June 8 (planned):
- #33598
- IPv6 part of #32888 <-- do you have a ticket for it?
Week of June 8 (actual):
- #32888 IPv6 PR: https://github.com/torproject/tor/pull/1932
- requested reproducibility info for
https://bugs.torproject.org/33598 -- maybe I'll start thread on tor-dev@
since trac is read-only
- wrote Outreachy blog post explaining Tor's IPv6 goals
Week of June 15 (planned):
- during meeting, poke someone about
https://github.com/torproject/chutney/pull/66
- chutney work with nickm (#34445 - #34448)
- force myself to remain regularly active on tor-dev@ so we can
get things done more efficiently :)
- in general just check behind myself and others to clean up
open issues in need of commentary or review
Week of June 15 (actual):
- started work on more chutney documention
- opened discussions on gitlab about chutney components
Week of June 22 (planned):
- continue chutney discussion/work
- #32888 / work on Address config to support IPv6
dgoulet:
Week of 29/06 (actual):
- s55: See #33049 for progress. Most of my week was on IPv6 tickets
both
on code or review.
- Merges and reviews.
- Wrote hs-v2 deprecation blog post. Published now.
- We got the HS-v2 deprecation warning #40003 in.
Week of 06/07 (planned);
- Simply continue s55 work...
- If time allows it, really need to address the fallbackdir situation.
--
she/her are my pronouns
GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19
Hi all,
Here are our meeting minutes:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-07-02-15.58.html
And here is our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Next meeting: Thursday July 2nd 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:
* Roadmap: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards
* The anti-censorship team's wiki page: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home
* Past meeting notes can be found at: https://lists.torproject.org/pipermail/tor-project/
* Tickets that need reviews: from sponsors we are working on:
* All needs review tickets: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s…
* https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 <-- it will be moved into gitlab
* https://gitlab.torproject.org/groups/tpo/-/milestones/4
* https://gitlab.torproject.org/groups/tpo/-/milestones/7
* https://gitlab.torproject.org/groups/tpo/-/milestones/5
* https://gitlab.torproject.org/groups/tpo/-/milestones/6
* https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 <-- it will be moved into gitlab
* must-do tickets: https://gitlab.torproject.org/groups/tpo/-/milestones/10
* possible tickets: https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&…
* Anti-censorship related tickets that we want other teams to fix:
* https://pad.riseup.net/p/tor-anti-censorship-tickets-keep <-- it will be moved into gitlab with TPO labels
== Announcements ==
* Use the "First Contribution" label if an issue is well-suited for newcomers.
* Take a look at our June 2020 report and make sure that it has your work:
* https://pad.riseup.net/p/ituvazq54RQemaxu0m4E
== Discussion ==
* Is there a way to accept anonymous bug reports in the anti-censorship team, even if other teams don't?
* https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
* If a random member of the public emails gitlab-admin to get an account, will it work? Or are accounts only for internal people?
* Could we have our own cypherpunks account?
* Could we recommend a public pad, from which we transcribe reports weekly?
== Actions ==
*
== Interesting links ==
*
== Reading group ==
* We will discuss GoodbyeDPI on July 9th
* https://github.com/ValdikSS/GoodbyeDPI
* 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-07-02):
* Gave a talk at OONI's Internet Measurement Village 2020:
* Recording: https://www.youtube.com/watch?v=g6xEfNHkFKY
* Filed tpo/anti-censorship/bridgedb#40001; the craziest BridgeDB bug I've run across so far.
* Lots of debugging for tpo/anti-censorship/bridgedb#31422. Eventually realised that the problem was #40001.
* Some onionperf and exitmap work.
* Merged tpo/anti-censorship/emma!2 for emma.
* Provided more background in tpo/anti-censorship/bridgedb#32117.
* Tested tpo/core/tor!10.
* Worked on June'20 team report.
* Moved forward with tpo/anti-censorship/wolpertinger#34259.
Next week:
* Wrap up tpo/anti-censorship/wolpertinger#34259.
Help with:
*
cecylia (cohosh): last updated 2020-06-25
Last week:
- reviewed #29184
- revised nat discovery feature (#34129)
- trial refactor of bridgedb to get ready for a GetTor integration (#3780)
- sponsor 28 evaluation prep
- snowflake proxy on mobile work, reviews
This week:
- away on vacation
Needs help with:
- another review of #34129
- review/feedback on #3780
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-06-11
Last week:
-
Next week:
- follow ups to #33365
- start on #31201
Help with:
-
dcf: 2020-07-02
Last week:
- tried to grant admin access to the snowflake broker CDN configuration (#30510)
- replied on revisions to NAT behavior (#34129)
- filed a ticket for bridge port scan usability (bridge-port-scan#1)
- helped debug a snowflake failure on Whonix (snowflake#34435)
Next week:
Help with:
Antonela: 2020-06-25
- (S30) planning activities for the user group in HK:
- Run emma
https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%2…
- Discovery issues with Bridges flow - working on the script
https://gitlab.torproject.org/tpo/ux/research/-/issues/4
agix:2020-07-02
Last week:
-Was off because of studies
Next week:
-Start on fixing #34318
-Finish review
Help with:
-
hanneloresx: 2020-06-25
Last week:
- Read existing documentation for BridgeDB. Get acclimated to GitLab.
- Read background information for #32117
Next week:
- Work on #32117
- Translate monthly team report
- Work on #33727
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-07-02
Last week:
- MR for #6 Allow users to add custom Relay, STUN, Broker servers using a settings UI.
-MR for #8 A Readme file for the project.
Next week:
- #6 Showing users stat about how many clients' they served in the past 24 hours
Help with: -
# Roll call: who's there and emergencies
Hiro and anarcat present in the meeting. Quick chat by mumble do to a
check-in and resolve some issues with the installer to setup
fsn-node-07 and check overall priorities.
# Roadmap review
We looked at the [issue board][] which excludes GitLab, because that
board was processed in the gitlab meeting yesterday.
[issue board]: https://gitlab.torproject.org/tpo/tpa/team/-/boards
We went through the tickets and did some triage, moving some tickets
from `Open` to `Backlog` and some tickets into `Next`. anarcat has no
tickets left in `Backlog` because he's going away for a two months
leave. hiro will review her ticket priorities within the week.
## GitLab workflow changes
We tried to get used to the new GitLab workflow.
We decided on using the "Next" label to follow the global @tpo
convention, although we have not adopted the "Icebox" label yet. The
gitlab policy was changed to:
> Issues first land into a "triage" queue (`Open`), then get assigned to
> a specific milestone as the ticket gets planned. We use the `Backlog`,
> `Next`, and `Doing` of the global "TPO" group board labels. With the
> `Open` and `Closed` list, this gives us the following policy:
>
> * `Open`: untriaged ticket, "ice box"
> * `Backlog`: planned work
> * `Next`: work to be done in the next iteration or "sprint"
> (e.g. currently a month)
> * `Doing`: work being done right now (generally during the day or
> week)
> * `Closed`: completed work
>
> That list can be adjusted in the future without formally reviewing
> this policy.
>
> Priority of items in the lists are determined by the *order* of items
> in the stack. Tickets should *not* stay in the `Next` or `Doing` lists
> forever and should instead actively be closed or moved back into the
> `Open` or `Backlog` board.
Note that those policies are still being discussed in the GitLab
project, see [issue 28][] for details.
[issue 28]: https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/28
## Exciting work that happened in June
* [Trac migrated to GitLab][]
* [TPA wiki][] migrated to GitLab
* kvm4 and kvm5 were retired, signaling the end of the "libvirt/KVM"
era of our virtual hosting: all critical services now live in
Ganeti
* lots of buster upgrades happened
[Trac migrated to GitLab]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/gitlab/#migration
[TPA wiki]: https://gitlab.torproject.org/tpo/tpa/team/
# Hand-off
During the mumble check-in, hiro and anarcat established there was not
any urgent issue requiring training or work.
anarcat will continue working on the documentation tickets as much as
he can before leaving ([Puppet][], [LDAP][], [static mirrors][]) but
will otherwise significantly reduce his work schedule.
[Puppet]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40024
[LDAP]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/34426
[static mirrors]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/34436
# Other discussions
No other discussions were held.
# Next meeting
No next meeting is currently planned, but the next one should normally
be held on Wednesday August 5th, according to our normal schedule.
# Metrics of the month
* hosts in Puppet: 72, LDAP: 75, Prometheus exporters: 126
* number of apache servers monitored: 29, hits per second: 176
* number of nginx servers: 2, hits per second: 2, hit ratio: 0.87
* number of self-hosted nameservers: 6, mail servers: 12
* pending upgrades: 1, reboots: 0
* average load: 0.67, memory available: 271.44 GiB/871.88 GiB, running processes: 400
* bytes sent: 211.50 MB/s, received: 113.43 MB/s
* GitLab tickets: 171 issues including...
* open: 125
* backlog: 26
* next: 13
* doing: 7
* (closed: 2075)
* number of Trac tickets migrated to GitLab: 32401
* last Trac ticket ID created: 34451
* planned buster upgrades completion date: 2020-08-11
Only 3 nodes left to upgrade to buster: troodi (trac), gayi (svn) and
rude (RT).
Upgrade prediction graph still lives at
https://help.torproject.org/tsa/howto/upgrades/
Now also available as the main Grafana dashboard. Head to
<https://grafana.torproject.org/>, change the time period to 30 days,
and wait a while for results to render.
--
Antoine Beaupré
torproject.org system administration
Hi!
We discussed the best way to resume the User Experience team meetings to
cultivate our open space for discussions around ethical user research,
user interface design, and user experience. Given our current capacity,
we consider a monthly meeting a good way to keep the group updated.
Meetings will happen every first Tuesdays of the month at 14UTC,
starting next Tuesday 7th in irc.oftc.net #tor-meeting.More details on
our wiki [0].
I hope to see you around to update each other about what we are up to
and share the open calls for research and design.
Peace and love,
A
[0] https://gitlab.torproject.org/tpo/ux/team/-/wikis/home
--
Antonela Debiasi
UX Team Lead
@antonela
E2330A6D1EB5A0C8
https://torproject.org
Hi!
Tor Browser meetings are happening every Monday at 1800UTC on
#tor-meeting in irc.oftc.net
We had a meeting on June 29th and here are the logs and notes.
Log:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-29-18.01.log…
Pad:
http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor…
Contents of the pad for today:
== Tor Browser meeting pad! ==
Next meeting is at Monday 6th July 1800 UTC on #tor-meeting on OFTC.
July Schedule:
* Monday 29 June 18:00 UTC
* Monday 6 July 18:00 UTC
Release meetings: https://pad.riseup.net/p/tor-browser-release-meeting-keep
Tuesday July 7th 18:00 UTC
(This channel is logged while meetings are in progress.) (See
https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht…
for background.)
Upcoming Releases and other important dates
2020.06.30: 9.5.1 and 10.0a2 - ESR68.10, ESR78.0
Latest Releases:
2020.05.22: 9.5a13
https://blog.torproject.org/new-release-tor-browser-95a13
2020.06.02: 9.5 Stable
https://blog.torproject.org/new-release-tor-browser-95
2020.06.02: 10.0a1
https://blog.torproject.org/new-release-tor-browser-100a1
== Previous notes ==
(Search the tor-project mailing list archive for older notes.)
June 15th -
https://lists.torproject.org/pipermail/tor-project/2020-June/002878.html
June 22nd -
https://lists.torproject.org/pipermail/tor-project/2020-June/002891.html
== What project we are working on? ==
SPONSOR 58 - Tor Browser Security, Performance, & Usability Improvements
Milestone: https://gitlab.torproject.org/groups/tpo/-/milestones/11
Parent ticket:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33664
Timeline: https://nc.torproject.net/s/ow2r6cLgL7Cd9BA
== Stuff to do every week ==
Kanban https://gitlab.torproject.org/groups/tpo/applications/-/boards
Check reviews not taken! How reviews from last week worked? Any
blocker?
https://gitlab.torproject.org/groups/tpo/applications/-/issues?scope=all&ut…
Next release: anybody need help with anything?
-------------------------------
---- 29 June 2020 -------------
-------------------------------
== Announcements [please date] ==
== Discussion [please date] ==
[June 29th] Please review
http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/58-…
. Bekeela will be sending it today.
[June 29th] dev.tpo needs Application Team review >
https://gitlab.torproject.org/tpo/web/trac/-/issues/24132
== Status 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.
ahf:
Week of 22/6 planned:
- Trying to minimize myself in the Gitlab stuff for now.
- Need to deal with review backlog.
- Back to doing Fenix + Tor integration.
- Get Tor network extension working on device with TGP sponsorship.
Week of 22/6 actually:
- Got help from Benjamin with certificates and all the Apple
"security" stuff with running your own apps on your own devices...
- Failed at completely detaching myself from Gitlab things:
worked on a few minor issues and the label clean-up.
- Tried to push for some sponsorship for CI for our Gitlab instance.
- Read Mike's congestion pads/mails.
- Got back to Fenix+Tor integration.
Week of 29/6 planned:
- Delete unused labels from Gitlab.
- Try to solve Gitlab#41 with Hiro since it makes working with
GL a bit more frustrating with our git.tpo/gitlab.tpo hybrid setup.
- Do merging/backporting of Tor things.
boklm:
Week of 2020-06-15 (actual):
- Made patches to use rootless containers and was able to do
builds of Tor Browser for windows-x86_64 and osx-x86_64
(tor-browser-build#23631 and rbm#40001). For some unknown reason the
builds based on wheezy are not working.
Week of 2020-06-22 (planned):
- Add some documentation for rbm#40001 and set the patch as
Needs Review
- Improve patch for rbm#32272 to handle Ctrl+C
Mike:
Week of 06/22 (planned):
- Wrap up congestion control proposal draft
- gecko-dev proxy audit
Week of 06/22 (actual):
- Funding proposal work
- Congestion control work for funding proposal notes
- Gitlab label cleanup
Week of 06/29 (planned):
- Performance funding proposal pre-meeting + funder meeting
- gecko-dev proxy audit
mcs and brade:
Week of June 22nd (actual):
- Rebased & landed “update downloading” patch (upstreaming
tor-browser#28885).
- See https://bugzilla.mozilla.org/show_bug.cgi?id=1642404
- Investigated intermittent test failure for other part of
tor-browser#28885.
- See https://bugzilla.mozilla.org/show_bug.cgi?id=1647313
- So far we have not reproduced the failure.
- tor-browser#33534: Finished reviewing Firefox 75-78beta
release/dev notes.
Week of June 29th (planned):
- tor-browser#33534: Review closed bugs for Firefox 75-78.
- More work on the intermittent test failure bug (Bugzilla 1647313).
- tor-browser#33852 (Clean up about:logins (LockWise) to avoid
mentioning sync, etc.)
sysrqb:
Week of 15 June (planned):
Really, really finish #33939
Review testsuite patches and merge them so we have a
working...testsuite
Catch up on current 9.5/10.0a tickets
Finally land vpx patch upstream
Review
https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004
Continue tracking OTF/DRL situation
Audit GitLab labels
Release prep
Week of 15 June (actual):
Really, really finish #33939 (no)
Review testsuite patches and merge them so we have a
working...testsuite (handed off to GeKo)
Catch up on current 9.5/10.0a tickets (no)
Finally land vpx patch upstream (small progress)
Review
https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 (no)
Continue tracking OTF/DRL situation (spent some time)
Audit GitLab labels (complete)
Release prep (complete)
Week of 22 June (planned):
#33939
Unblock any other Fenix work
9.5.1/10.0a2 releases
cpu_features patch uplift
GeKo:
Week of June 22 (planned):
Gitlab work
Finish review of #33533
Finish application-services build
Week of June 22 (actual):
Gitlab work
Finish Review of #33533
Work on application-services build
Week of 29 June:
Finish build of application services
help with releases were fit
Reviews (dev.tpo, O3.2 design for S30, #27105, #30832)
Antonela:
Week of 22 June (planned):
- Review HTTPS-E Names
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40010#n…
- Work on S58 tickets TBA UI
- Waiting for tbb-dev review in S30
https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004
Week of 22 June (actual):
- Nothing of that
Week of 29 June:
- Review HTTPS-E Names
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40010#n…
- Work on S58 tickets TBA UI
- Waiting for tbb-dev review in S30
https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004
acat:
Week of 22nd June (planned):
Possibly address GeKo's feedback on #33533
Add tests in tor-browser-bundle-testsuite:
40001: Add test for "Communicating security expectations TB
patch"
40002: Add test for "Add v3 onion services client
authentication prompt" TB patch
40003: Add test for "Implement Onion-Location" TB patch
40004: Add test for "Implement .onion alias urlbar rewrites"
TB patch
40005: Add test for "Replace security slider with security
level UI" TB patch
Rebase #33533 to latest beta and test tor-browser-spec#40001 process
Week of 22nd June (actual):
- Add tests in tor-browser-bundle-testsuite (will push MR after
meeting):
- 40001: Add test for "Communicating security expectations
TB patch"
- 40003: Add test for "Implement Onion-Location" TB patch
- 40004: Add test for "Implement .onion alias urlbar
rewrites" TB patch
- 40005: Add test for "Replace security slider with security
level UI" TB patch
Week of 29th June:
- Finish tor-browser-bundle-testsuite@40002: Add test for "Add
v3 onion services client authentication prompt" TB patch
- Revise & Rebase #33533 to latest beta and test
tor-browser-spec#40001 process
- Revise tor-browser-spec@40001: Add rebasing process document
- Maybe iterate on tor-browser@33791: Evaluate Firefox tests
- I was thinking of finding the subset of FF tests that pass
and put it in some list/script so that we can run/keep track of it.+1
(+1, yes, please)
Jeremy Rand:
Week of 15 and 22 June (actual):
Ask for feedback on latest Namecoin patches to Tor Browser on
Reddit.
https://old.reddit.com/r/Namecoin/comments/hbf9fq/we_need_more_testers_for_…
Got some decent feedback. At this point it looks like the
primary request from testers is adding macOS and Windows support.
Upstream Electrum released a couple of betas of Electrum 4.0.0.
Started looking at rebasing Namecoin's patches to 4.0.0 (most are
rebased continuously, but a few only get rebased for releases.)
Dealing with various funding-related things e.g. NLnet proposal.
Discussed having Namecoin issue a statement about the OTF situation.
Tried to activate my GitLab account, failed.
Week of 29 June (planned):
Look more seriously at what's needed to port the Namecoin
support to macOS/Windows.
Keep working on rebasing Namecoin's patches to Electrum 4.0.0.
Continue working on upstreaming Namecoin's Electrum patches.
Continue talking to NLnet about funding things.
Issue a formal statement from Namecoin about the OTF situation
(hopefully it helps).
Hopefully get my GitLab account sorted out.
--
she/her are my pronouns
GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19
Hi!
Network meetings are happening every Monday at 1700UTC on
#tor-meeting in irc.oftc.net
We had a meeting on June 29th and here are the logs and notes.
Log:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-29-16.59.log…
Pad:
http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor…
Contents of the pad for today:
== Network meeting pad! ==
Next meeting is at Monday 29th June 1700 UTC on #tor-meeting on OFTC.
June Schedule:
* Monday 29 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.)
1 June:
https://lists.torproject.org/pipermail/tor-project/2020-June/002857.html
8 June:
https://lists.torproject.org/pipermail/tor-project/2020-June/002865.html
15 June:
https://lists.torproject.org/pipermail/tor-project/2020-June/002877.html
22 June:
https://lists.torproject.org/pipermail/tor-project/2020-June/002890.html
== Stuff to do every week ==
Let's check and update our roadmap:
What's done, and what's coming up? Any change?
Board: https://gitlab.torproject.org/groups/tpo/core/-/boards
S28 & S30 - Continue after October - Ahf
S55 - Nickm & dgoulet
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:
[NEEDS NEW GITLAB LINK]
Merge requests in Core:
https://gitlab.torproject.org/groups/tpo/core/-/merge_requests
Let's check out 0.4.4 release status and open tickets!
Tickets in 0.4.4.x with no owner.
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
nickm:
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
dgoulet:
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
ahf:
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
asn:
https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&sta…
== 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.
-------------------------------
---- 29 June 2020
-------------------------------
== Announcements [please date] ==
== Discussion [please date] ==
[June 29th] Please take a look! (antonela) in the next 1 week to
dev.torproject.org work ->
https://gitlab.torproject.org/tpo/web/trac/-/issues/24132#note_2681345
[June 29th] David, Nick: please review s55 board
https://gitlab.torproject.org/groups/tpo/core/-/boards?scope=all&utf8=%E2%9…
=== 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 22 June (planned):
- Go through backlog
- Work on misc 0.4.4.x issues
- Fix S55 bugs
- More gitlab stuff, probably.
- catch up on email backlog?
Week of 22 June (actual):
- Fiddle with gitlab
- Review and merge
- Work on various 044 tickets assigned to me, including:
- Move Codestructure.md into Doxygen
- Remove OPTIONS_DUMP_DEFAULTS
- Work on various S55 tickets, including:
- 34445 (remove authority semantics for assumereachable)
- Other assumereachable handling
- Catch up on email backlog
- Look through Mike's congestion control proposal
Week of 29 June (planned):
- More S55 work
- 044 work
- Investigate problems building/running with Openssl 3 alpha
(tor#34139)
- Maybe move OSS-fuzz off of openssl 3?
- Write a proposal for packing multiple commands into a relay cell.
- More thinking on congestion control
- Work on stable releases
ahf:
Week of 22/6 planned:
- Trying to minimize myself in the Gitlab stuff for now.
- Need to deal with review backlog.
- Back to doing Fenix + Tor integration.
- Get Tor network extension working on device with TGP sponsorship.
Week of 22/6 actually:
- Got help from Benjamin with certificates and all the Apple
"security" stuff with running your own apps on your own devices...
- Failed at completely detaching myself from Gitlab things:
worked on a few minor issues and the label clean-up.
- Tried to push for some sponsorship for CI for our Gitlab instance.
- Read Mike's congestion pads/mails.
- Got back to Fenix+Tor integration.
Week of 29/6 planned:
- Delete unused labels from Gitlab.
- Try to solve Gitlab#41 with Hiro since it makes working with
GL a bit more frustrating with our git.tpo/gitlab.tpo hybrid setup.
- Do merging/backporting of Tor things.
asn:
Week of 22/06 (planned):
- More work on PoW proposal. Fold in David's work on the scheduler and
derive
results from that.
- Hopefully merge #32040.
- More reviews & merges.
Week of 22/06 (actual):
- Another version of the PoW proposal is out:
https://lists.torproject.org/pipermail/tor-dev/2020-June/014381.html
- OBv3 now has a bunch of new features as the result of the gitcoin
hackathon:
- SIGHUP support
- status socket support
- OBv3 is also in Debian sid
- Wrote guidelines for gitlab review process:
-
https://gitlab.torproject.org/tpo/core/tor/-/wikis/NetworkTeam/GitlabReviews
- Did a bunch of reviews & merges
Week of 29/06 (actual):
- More PoW work
- A look at v3 metrics.
- More OBv3 hackathon. Someone is hacking on distinct descriptor support.
- Need to adapt the gitlab process to using MRs as discussed on Thurdsay.
- A bunch more reviews & merges.
jnewsome:
Week of June 15 (planned):
- Work out logging from the shim with the new file IO design
- Help flesh out support for syscalls and libraries needed to
run Tor
- Start looking into code-coverage tools (gcov)
Week of June 15 (actual):
- Fixed logging destination from the shadow/phantom shim
- Patched libc from package sources to allow benchmarking for
"preload" interposition mechanism without having to reimplement
more of libc
- A little bit of initial benchmarking of shadow/phantom.
(So far much slower, but have some ideas for improvement)
- Backported centos 7 fixes for shadow
https://github.com/shadow/shadow/pull/851
Week of June 22 (planned):
- More profiling of shadow/phantom and start work on optimizations
Week of June 22 (actual):
- Ported "interposable libc" patch to centos 7 (our benchmarking
platform).
This version of glibc took a bit more work.
- Switched ptrace-based shadow/phantom to use PTRACE_SYSEMU,
substantially improving performance.
Week of June 29 (planned):
- Fix https://github.com/shadow/shadow/issues/853
- Help with shadow/phantom benchmarking and optimization as needed
- Work on shadow test code-coverage measurement strategy
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
Week of May 25 (actual):
- #33609 ready for review
- started hunting down and working on other Sponsor55-can and
-must issues
- talking in #tor-project about wiki
Week of June 1 (actual):
- opened and made #34381 ready for review
- IPv4 part of #32888
Week of June 8 (planned):
- #33598
- IPv6 part of #32888 <-- do you have a ticket for it?
Week of June 8 (actual):
- #32888 IPv6 PR: https://github.com/torproject/tor/pull/1932
- requested reproducibility info for
https://bugs.torproject.org/33598 -- maybe I'll start thread on tor-dev@
since trac is read-only
- wrote Outreachy blog post explaining Tor's IPv6 goals
Week of June 15 (planned):
- during meeting, poke someone about
https://github.com/torproject/chutney/pull/66
- chutney work with nickm (#34445 - #34448)
- force myself to remain regularly active on tor-dev@ so we can
get things done more efficiently :)
- in general just check behind myself and others to clean up
open issues in need of commentary or review
Week of June 15 (actual):
- started work on more chutney documention
- opened discussions on gitlab about chutney components
Week of June 22 (planned):
- continue chutney discussion/work
- #32888 / work on Address config to support IPv6
dgoulet:
Week of 22/06 (actual):
- Finalized #33233 and it is now merged.
- Patch on small tickets: #40008 and #33618
- Reviewed and merged a series of tickets.
- Patch on #40006 and merged as well.
- Reviewed congestion control proposal from mikeperry.
- Worked with asn on our Gitlab review process
- Discussion with asn on v3 metrics
- s55 sync with nickm.
Week of 29/06 (planned);
- s55 work: Remaining tickets are in #33049
- Write HSv2 deprecation blog post and hopefully publish
--
she/her are my pronouns
GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19