Hello Tor Community,
I'm happy to announce that the Tor Project Community Policies have a new
website! You can visit our Policies website here:
<https://community.torproject.org/policies>. The website hosts the Tor
Project Community governance policies, including our Code of Conduct,
Social Contract, Relay Operators docs, and other important documents.
The website was generated using Onion MkDocs[1] and was part of our
project at Tor Hackweek[2]. We've also updated all links directing to
the old repository (gitweb.tpo) to the new website.
If you find any issue or have suggestions for improvements, please feel
invited to open a ticket in the Community/Policies repository:
<https://gitlab.torproject.org/tpo/community/policies>.
A special thanks to Rhatto and Lavamind for their support and assistance
with the deployment. I'm very happy to have a more accessible and user
friendly page for the Tor Community.
Best regards,
Gus
[1] Onion MkDocs: https://gitlab.torproject.org/tpo/web/onion-mkdocs
[2] Tor Hackweek: https://gitlab.torproject.org/tpo/community/hackweek/-/issues/13
--
The Tor Project
Community Team Lead
Hello Tor world,
*I'm very happy to share that starting today through December 31, your
donation to the Tor Project will be matched 1:1.* That means that every
donation, up to $75,000, will be doubled.
Please spread the word! :)
Blog announcement:
https://blog.torproject.org/friends-of-tor-match-2023/
Twitter post:
https://x.com/torproject/status/1729238115263652330
Mastodon post:
https://mastodon.social/@torproject/111484468818648276
Thank you,
Al
--
Al Smith (they/them)
Fundraising Director
The Tor Project
My working hours may not be your working hours. If I message you outside
of your working hours, know that I do not expect an immediate response
and that I support your right to disconnect.
Hi folks,
A set of Tor people will be at CCC at the end of December this year,
and we are organizing what Tor activities will happen.
With luck, activities will include a maintrack talk from me on Tor and
recent censorship, and a Tor relay operator meetup organized by our
local CCC friends.
Are you part of the broader Tor community and you plan to be there? If
yes, please either note this on the gitlab ticket if it's convenient
( https://gitlab.torproject.org/tpo/community/outreach/-/issues/40051 )
or else mail me off-list if you like. (No need to turn this mailing list
into a big 'me too' thread.)
And if you are planning some other Tor-related activity (you want
some Tor people at your assembly? you plan to talk about Tor in a talk
submission? something else?) please let us know that too if you like.
I'll plan to keep people updated as the plans emerge.
Woo,
--Roger
Hi everyone!
We have our Hackweek retrospective at tomorrow's All Hands meeting
(Wednesday, November 15th). Each project's presenter(s) will have 5
minutes or so to talk about the work done and any next steps.
Action items:
(1) Re: projects that you worked on, presenters, please be prepared to
discuss the work done and next steps, add comments about status of
projects in Gitlab, and also close the issue;
(2) Re: projects that weren't picked up/worked on last week, please go
ahead and close those issues in Gitlab; and lastly
(3) See the link for the Hackweek retrospective pad below. Please take
a few moments to collect your thoughts about: (a) what went well with
Hackweek?; (b) what didn't go so well and the challenges?; and (c) what
could we try to do differently in the future? Got them gathered?
Good! Now add them to the pad below :)
https://pad.riseup.net/p/AWQ8DisjSVnu9leO90Xo-HackweekRetrospective-keep
If we have time after presentations, we'll go through the retrospective
pad comments.
Thanks everyone! See you at the All Hands!
Best,
Tyler
Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-11-09-16.00.html
And our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday, Nov 16 16:00 UTC
Facilitator: meskio
Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC
(channel is logged while meetings are in progress)
This week's Facilitator: onyinyang
== Goal of this meeting ==
Weekly check-in about the status of anti-censorship work at Tor.
Coordinate collaboration between people/teams on anti-censorship at the
Tor Project and Tor community.
== 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?scope=all&utf8=%E2%9C%93&state=opened&assignee_id=None
* Sponsor 96 <-- meskio, shell, onyinyang, cohosh
*https://gitlab.torproject.org/groups/tpo/-/milestones/24
* Sponsor 150 <-- meskio working on it
*https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_name%5B%5D=Sponsor%20150
== Announcements ==
== Discussion ==
* azure will close domain fronting January 8
*
https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/33#note_296…
* Maybe, move to use a private pad?
* we can use the 'read-only' link from the riseup pads as a
public link and share the editing link with the people that participates
on the meetings.
* meskio will set up for next week.
== Actions ==
== Interesting links ==
*
https://forum.torproject.org/t/snowflake-daily-operations-october-2023-upda…
* FOCI & PETS 2023 videos
* Running a high-performance pluggable transports Tor bridge
https://www.youtube.com/watch?v=UkUQsAJB-bg&list=PLWSQygNuIsPc8bOJ2szOblMK4…
* Lox: Protecting the Social Graph in Bridge Distribution
https://www.youtube.com/watch?v=hT2PkFs-61A&list=PLWSQygNuIsPeSo_mDoX9MPrVD…
* others https://github.com/net4people/bbs/issues/307
== Reading group ==
* We will discuss "On Precisely Detecting Censorship Circumvention
in Real-World Networks" on November 9
*
https://www.robgjansen.com/publications/precisedetect-ndss2024.html
* 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.
cecylia (cohosh): 2023-11-09
Last week:
- conjure bridge maintenance
- caught a bug in safelog library
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- caught problem with domain front in conjure
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conj…
This week:
- lox tor browser UX integration
- lox distributor testing
- look into alternative domain fronting providers
Needs help with:
dcf: 2023-11-09
Last week:
- revised encapsulation.ReadData redesign to return an error in
the case of a short buffer
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- security upgrade to tor 0.4.8.8 on snowflake bridges
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- sent emails to make contacts for uTLS-like fingerprint
obfuscation in pion/dtls
Next week:
- open issue to have snowflake-client log whenever KCPInErrors
is nonzero
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- parent:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- open issue to disable /debug endpoint on snowflake broker
Before EOY 2023:
- move snowflake-02 to new VM
Help with:
meskio: 2023-11-09
Last week:
- update the teams wikis
- explore pad backup options (hackweek#16)
- rdsys accept multiple config files, to support separating
secrets (rdsys#92)
- fix onionsproutsbot after server upgrade (onionsproutsbot#55)
- expore why polyanthum disk is filling up (tpa/team#41379)
Next week:
- experiment with testing bridges more frequently by
bridgestrap (bridgestrap#39)
Shelikhoo: 2023-11-09
Last Week:
- Work on snowflake performance improvement (WIP):
https://gitlab.torproject.org/shelikhoo/snowflake/-/tree/dev-speedwithudp?r…
- Hackweek: wiki replacement considerations
https://gitlab.torproject.org/tpo/community/hackweek/-/issues/26#note_29635…
- Hackweek: Collaborative editing
https://gitlab.torproject.org/tpo/community/hackweek/-/issues/16#note_29633…
- Merge request reviews
Next Week/TODO:
- Write Tor Spec for Armored URL (continue)
- Work on snowflake performance improvement (WIP):
https://gitlab.torproject.org/shelikhoo/snowflake/-/tree/dev-speedwithudp?r…
- Merge request reviews
onyinyang: 2023-11-09
Last week(s):
- Continued work on Lox telegram bot
- Hackweek: Docs for Lox
https://gitlab.torproject.org/tpo/community/hackweek/-/issues/20
This week:
- Hackweek: Docs for Lox
https://gitlab.torproject.org/tpo/community/hackweek/-/issues/20
- Publish Lox crates to crates.io
(long term things were discussed at the
meeting!):https://pad.riseup.net/p/tor-ac-community-azaleas-room-keep
- brainstorming grouping strategies for Lox
buckets (of bridges) and gathering context on how types of bridges are
distributed/use in practice
Question: What makes a bridge usable for a
given user, and how can we encode that to best ensure we're getting the
most appropriate resources to people?
1. Are there some obvious grouping
strategies that we can already consider?
e.g., by PT, by bandwidth (lower
bandwidth bridges sacrificed to open-invitation buckets?), by locale (to
be matched with a requesting user's geoip or something?)
2. Does it make sense to group 3
bridges/bucket, so trusted users have access to 3 bridges (and untrusted
users have access to 1)? More? Less?
--
---
onyinyang
GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036