Hey everyone!
Here are the meeting logs:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-11-05-16.00.html
and our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Next meeting: Thursday November 5th 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…
Sponsor 30
https://gitlab.torproject.org/groups/tpo/-/milestones/4https://gitlab.torproject.org/groups/tpo/-/milestones/7https://gitlab.torproject.org/groups/tpo/-/milestones/5https://gitlab.torproject.org/groups/tpo/-/milestones/6
Sponsor 28
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 <-- do we still need this? The
label is 'for anticensorship team'
Public bug-reporting pad:
https://pad.riseup.net/p/tor-anti-censorship-bugs-keep
== Announcements ==
We're adding a new default bridge.
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40212
== Discussion ==
== Actions ==
== Interesting links ==
"Towards a Scalable Censorship-Resistant Overlay Network based on
WebRTC Covert Channels"
https://www.gsd.inesc-id.pt/~nsantos/papers/barradas_dicg20.pdf
== Reading group ==
We will discuss "The use of TLS in Censorship Circumvention" on
2020-11-12
https://tlsfingerprint.io/static/frolov2019.pdf
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-10-29):
Reviewed Snowflake patches, rdsys patch, grant budget, and S30 report.
Lots of rdsys and Salmon refactoring.
Made good progress on cohosh's idea of making Salmon more privacy
preserving by not storing a social graph on the server side.
Experimented with statsd/graphite for metrics.
Seems very promising.
Took a look at the recent censorship in Tanzania.
Next week:
Finish refactoring Salmon and start working on cohosh's "social
graph reduction" idea.
Help with:
https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues/3
cecylia (cohosh): last updated 2020-11-05
Last week:
- submitted merge request for snowflake#40012
- worked on a patch for guardian project efforts to make a snowflake
library (snowflake#40018)
- made slides for sponsor 28 PI meeting
- attended sponsor 28 PI meeting
- switched from a docker-based to network namespace solution for
probetest service (snowflake#40013)
This week:
- finish debugging snowflake#40013
- continue work on snowflake#40018
- follow up on progress towards a telegram bot for gettor
- pick up snowflake multiplexing work again (snowflake#25723)
- sponsor 28 PI meeting
- write probetest survival guide
Needs help with:
- review of snowflake!16
juggy :
This week:
- Got very basic "suggested readings" list up and running here :
https://jugheadjones10.github.io/anti-censorship-reading/
Next week:
- Keep studying BridgeDB to write architectural overview
Help with:
- Open issues here
(https://github.com/jugheadjones10/anti-censorship-reading ) for
papers/resources/readings that you think might be useful for newcomers
arlolra: 2020-10-29
Last week:
-
Next week:
- getting back up to speed
- follow ups to #33365
- start on #31201
Help with:
-
dcf: 2020-11-05
Last week:
- reviewed broker firewall changes for Snowflake probetest
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
Next week:
- review broker metrics cache
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
Help with:
Antonela: 2020-08-27
This week:
- Wrapping Babatunde's research on the use of circumvention tools
during internet censorship in Africa. Wrapping Personas for s30 with it.
For september:
- We are planning interviews with users in China to run our bridges
discovery issues script in real time. We discussed to include TBA +
snowflake as a task for users to run over a week or two and report back.
https://gitlab.torproject.org/tpo/ux/research/-/issues/4
- I still have bridges.tpo to lektor issue open
- More work on UX/UI for TB 10.0/10.5
- Review Salmon related tickets (im late with it!)
agix:2020-11-05
Last week:
-Made some good progress on understanding rdsys code (a lot of
debugging)
-Gather ideas for Pluggable Transports/HTTPT/Issues/#4
Next week:
-Continue work on rdsys ticket
Help with:
-
hanneloresx: 2020-10-22
Last week:
- Took break to focus on work
Next week:
- #32117: Look at CAPTCHA success rate for users from the US across
different types of bridges
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-10-16
This week:
- Finished work on #19
Next week:
- Network checks
Help with: -
Hi,
During November 6th, November 7th and November 9th, the Tor Project and
Localization Lab will host the first edition of Tor Project's
localization hackathon, the Tor L10n Hackathon.
https://blog.torproject.org/tor-l10n-hackathon
A hackathon is an event where a community hangs out and works together
to update, fix, and collaborate on a project. The L10n Hackathon is a
remote and online event.
In this localization hackathon, we're going to work exclusively on the
localization of our latest resource, the Tor Community portal.
https://community.torproject.org/
The Community portal is organized into sections: Training, Outreach,
Onion Services, Localization, User Research, and Relay Operations. Each
section helps users understand how they can get involved in each
activity to build and strengthen the community supporting the Tor Project.
At this time, we will ask technical folks to be available and open for
any technical questions that might arise from translators when
localizing our available material. You can join us in #tor-l10n to
answer these questions.
You can find the event's schedule here:
https://wiki.localizationlab.org/index.php/TorL10nHackathon
Given our global mission, it is critical to offer these resources in
local languages.
Thanks in advance for your collaboration!
Gus, Erin and Antonela
--
Antonela Debiasi
UX Team Lead
@antonela
E2330A6D1EB5A0C8
https://torproject.org
Hello everyone,
The next Tor Browser release meeting will be held on 03 November at 1900
UTC in #tor-meeting. Please add discussion items on the pad:
https://pad.riseup.net/p/tor-browser-release-meeting-keep
If we do not have any discussion items for the meeting by 1700 UTC on
3rd Nov, then the meeting will be cancelled.
Thanks,
Matt
Hi!
The November's User Experience team meeting will be on November 10th in
#tor-meeting*.
During this meeting, we will discuss the 2021 Roadmap for the user
experience team and its impact across different teams. We will also review
the 2020 State of the Onion presentation.
Also, we will have some space for an open floor so feel free to list
yourself in the pad.
https://pad.riseup.net/p/1D8sK8Zy74b_0qclC97I-ux-team-monthly-2020-keep
Remember, the User Experience team meetings are willing to cultivate an
open space for discussions around ethical user research, user interface
design, and user experience, meanwhile building privacy-enhancing products.
I hope to see you around!
Peace and love,
A
[*] https://gitlab.torproject.org/tpo/ux/team/-/wikis/home
--
Antonela Debiasi
UX Team Lead
torproject.org
@antonela
E2330A6D1EB5A0C8
Hey everyone!
Here are the meeting logs:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-10-29-15.58.html
and our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Next meeting: Thursday October 29th 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…
Sponsor 30
https://gitlab.torproject.org/groups/tpo/-/milestones/4https://gitlab.torproject.org/groups/tpo/-/milestones/7https://gitlab.torproject.org/groups/tpo/-/milestones/5https://gitlab.torproject.org/groups/tpo/-/milestones/6
Sponsor 28
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 <-- do we still need this? The
label is 'for anticensorship team'
Public bug-reporting pad:
https://pad.riseup.net/p/tor-anti-censorship-bugs-keep
== Announcements ==
Please add your October highlights to our monthly report pad:
https://pad.riseup.net/p/-mFSnGRKoOGCIq0pByRz
Found a student who's interested in working on:
https://gitlab.torproject.org/tpo/anti-censorship/emma/-/issues/4
== Discussion ==
== Actions ==
== Interesting links ==
"Towards a Scalable Censorship-Resistant Overlay Network based on
WebRTC Covert Channels"
https://www.gsd.inesc-id.pt/~nsantos/papers/barradas_dicg20.pdf
== Reading group ==
We will discuss "" on
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-10-29):
Reviewed Snowflake patches, rdsys patch, grant budget, and S30 report.
Lots of rdsys and Salmon refactoring.
Made good progress on cohosh's idea of making Salmon more privacy
preserving by not storing a social graph on the server side.
Experimented with statsd/graphite for metrics.
Seems very promising.
Took a look at the recent censorship in Tanzania.
Next week:
Finish refactoring Salmon and start working on cohosh's "social
graph reduction" idea.
Help with:
cecylia (cohosh): last updated 2020-10-29
Last week:
- talked to guardian project about their efforts to integrate snowflake
- sponsor 28 evaluations (x_x)
- more revisions to and deployed snowflake#40013
- published snowflake-webext!7 on addon stores and website
- helped out with snowflake mobile bug (snowflake#40018)
- implemented cached broker stats (snowflake#40012)
- modified a script to plot default bridge connections from Tanzania
(https://gitlab.torproject.org/-/snippets/67)
This week:
- follow up on progress towards a telegram bot for gettor
- pick up snowflake multiplexing work again (snowflake#25723)
- roll out and monitor snowflake web deployment
- sponsor 28 PI meeting
- clean up and write tests for snowflake#40012
Needs help with:
- firewall feedback for snowflake#40013 (dcf)
juggy :
This week:
- Got very basic "suggested readings" list up and running here :
https://jugheadjones10.github.io/anti-censorship-reading/
Next week:
- Keep studying BridgeDB to write architectural overview
Help with:
- Open issues here
(https://github.com/jugheadjones10/anti-censorship-reading ) for
papers/resources/readings that you think might be useful for newcomers
arlolra: 2020-10-29
Last week:
-
Next week:
- getting back up to speed
- follow ups to #33365
- start on #31201
Help with:
-
dcf: 2020-10-29
Last week:
- Azure CDN bookkeeping
- made a patch to remove an unnecessary error log from Snowflake
proxy
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
Next week:
- review broker firewall changes
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
Help with:
Antonela: 2020-08-27
This week:
- Wrapping Babatunde's research on the use of circumvention tools
during internet censorship in Africa. Wrapping Personas for s30 with it.
For september:
- We are planning interviews with users in China to run our bridges
discovery issues script in real time. We discussed to include TBA +
snowflake as a task for users to run over a week or two and report back.
https://gitlab.torproject.org/tpo/ux/research/-/issues/4
- I still have bridges.tpo to lektor issue open
- More work on UX/UI for TB 10.0/10.5
- Review Salmon related tickets (im late with it!)
agix:2020-10-29
Last week:
-Implemented feedback on #5 (rdsys)
-Got more familiar with rdsys
Next week:
-Get feedback from my univesity professor regarding tackeling
Pluggable Transports/HTTPT/Issues/#4 in my master thesis
-More familiarization with rdsys
Help with:
-
hanneloresx: 2020-10-22
Last week:
- Took break to focus on work
Next week:
- #32117: Look at CAPTCHA success rate for users from the US across
different types of bridges
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-10-16
This week:
- Finished work on #19
Next week:
- Network checks
Help with: -
Hi,
About 2 years ago I setup a server to run sbws.
It seems the sbws instance instance running in sbws.lavafeld.org is not being
actively used.
In case you would like to continue seeing this service up and running, please do
let me know.
Cheers,
~Vasilis
Hi all, hope everyone's getting through this pandemic reasonably well.
Just my usual not-so-monthly status report.
https://blog.atagar.com/october2020/
Cheers! -Damian
Hi,
tl,dr: The ministry of finance of the German state of Thuringia advises
against the blocking of the Tor network.
Longer version: In march I tried to reach <URL:https://tmasgff.de/>, the
website of the ministry of social affairs of Thuringia. However their
provider, Alfahosting, was blocking Tor traffic. So I reached out to the
ministry and asked why this is so. They answered that there is a huge
amount of hacking traffic coming from the Tor network. That's Why all
traffic coming from Tor is blocked.
So I made an FOIA-like request (Thuringia has a transparency law) and
asked how many attacks they saw from the Tor network and from the
non-Tor network:
<URL:http://fdstaat23zv6kdmntgkvdzkr7hipl5oqswwi3xawzkj2w2gwsbxmrwyd.onion/a/181821>
After some back and forth they told me, that their provider won't answer
the request for "security reasons". The ministry requested a statement
from the CI(S)O of the state which resides inside the ministry of
finance. He answered that providing information to users from the Tor
network is no special risk and the ministry won't recommend blocking the
Tor network. Since the the site <URL:https://tmasgff.de/> is available.
Best,
--
Jens Kubieziel https://kubieziel.de/blog/https://datenkanal.org/https://insecurity.radio.fm/