Hi,
Here are a few highlights about what we did in May, among many other
things:
*
We implemented many improvements to the Tor Connection assistant. This
makes is much easier for people in Asia to circumvent censorship. For
details, see the Tails 5.1 release notes [1].
*
We wrote a new homepage for the _Unsafe Browser_ when you are not
connected to the Tor network yet. This new version makes it easier to
understand how to sign in to the network using a captive portal.
*
We started organized training and usability tests sessions for August in
Brazil.
*
Tails 5.0 was released on May 3 [2]. It was the first version of Tails
based on Debian 11 (Bullseye) and brought new versions of a lot of the
software included in Tails and new OpenPGP tools.
*
We started evaluating Mirrorbits to manage our download mirror pool. On
top of decreasing the required maintenance work, this should make
downloads of Tails faster and more reliable.
*
Tails has been started more than 769 997 times this month. This makes
24 838 boots a day on average.
Cheers!
Links:
------
[1] https://tails.boum.org/news/version_5.1/index.en.html
[2] https://tails.boum.org/news/version_5.0/index.en.html
Hi!
The Tor Project and Tor community is going to be gathering online from
June 27th to July 1st this year for a 5 days hackweek.
This is a call for projects for whoever wants to participate, put
together a team and hack through that last week of June with us. In the
context of this hackweek, a project is anything related to Tor that you
can work with other people in 5 days. It could be a coding project or
something to analyze data but it could also be a cartoon or anything
that do not necessary requires coding skills. You will work on this
project during 5 days with other people in your team. At the end we are
going to have a demo in a Big Blue Button's room where your team will
present the work you did through the week.
This will be the timeline for the hackweek this year:
June 9th: Send hackweek project proposals to this portal:
https://hackweek.onionize.space/hackweek/. Before hackweek begins, start
looking for other people to join your team.
Monday, June 27th: Hackweek begins. The liasions for each project
will present their projects in a BBB room published that day. By this
time, you should have a few members of your team already identified.
Hack hack hack hack... in whatever way you organize yourself. We
will have the room #tor in irc.oftc.net to discuss general hackweek things.
Friday, July 1st: Hackweek ends. Each team presents the work they
did in a BBB room.
We will be updating the list of projects in
https://hackweek.onionize.space/hackweek/schedule/ . Each project will
have one pad (you can use https://pad.riseup.net) with all information
that people need to add themselves to that project.
cheers,
gaba
Hi Everyone,
We will be moving the weekly Tor Browser dev meetings to 1000 UTC (still on Mondays in #tor-meeting
on OFTC) going forward.
best,
-Richard
Here are minutes from Monday.
# Roll call: who's there and emergencies
Anarcat, Kez, and Lavamind present.
No emergencies.
# Roadmap / OKR review
Only one month left to the quarter! Where are we? As a reminder, we
generally hope to accomplish 60-70% of OKRs, by design, so they're not
supposed to be all done.
[TPA OKRs][]: roughly 17% done
* [mail services][] work has not started, the RFC proposal took longer
than expected and we're waiting on a decision before starting any work
* [Retirements][] might progress with a gitolite/gitweb retirement RFC
spearheaded by anarcat
* [codebase cleanup][] work has progressed only a little, often gets
pushed to the side by emergencies
* [Bullseye upgrade][] has only 6 machines left in the second batch. We
need to close 3 more tickets to get at 60% on *that* OKR, and that's
actually likely: the [second batch][] is likely to finish by the end
of the month, the [primary ganeti cluster upgrade][] is planned, and
the [PostgreSQL warnings][] will be done today
* [High-performance cluster][]: "New Relic" is giving away money, we
need to write a grant proposal in 3 days though, possibly not going to
happen
[TPA OKRs]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/roadmap/2022
[mail services]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/4
[retirements]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/1
[codebase cleanup]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/3
[bullseye upgrades]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/5
[second batch]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40692
[primary ganeti cluster upgrade]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40689
[PostgreSQL warnings]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40776
[High-performance cluster]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/2
[Web OKRs][]: 42% done overall!
* The donate OKR is about 25% complete
* translation OKR seems complete, no one has any TODO items on that
anyways, so considered done (100%!)
* docs OKR:
* dev.tpo work hasn't started yet, might be possible to start
depending on kez availability?
* documentation improvement might be good for hack week
[web OKRs]: https://gitlab.torproject.org/tpo/web/team/-/wikis/roadmap/2022
# Holidays
Update on holiday dates, everyone agrees with the plan. Details are
private, see tor-internal emails, and the Nextcloud calendars for the
authoritative dates.
# This week's All-Hands
* lavamind will talk about the blog
* if there is still time after, we can open for comments or questions
about the mail proposal
# Dashboard review
We looked at the global dashboards:
* https://gitlab.torproject.org/tpo/tpa/team/-/boards/117
* https://gitlab.torproject.org/groups/tpo/web/-/boards
* https://gitlab.torproject.org/groups/tpo/tpa/-/boards
... and per-user dashboards, not much to reshuffle.
# Icinga vs Prometheus again
Validate requirements, discuss the alternatives. Requirements weren't
ready, postponed.
# Other discussions
No other discussion came up.
# Next meeting
Next meeting is on a tuesday because of the holiday, we should talk
about OKRs again, and the Icinga vs Prometheus question.
# Metrics of the month
* hosts in Puppet: 96, LDAP: 96, Prometheus exporters: 160
* number of Apache servers monitored: 29, hits per second: 299
* number of self-hosted nameservers: 6, mail servers: 8
* pending upgrades: 0, reboots: 0
* average load: 2.65, memory available: 4.32 TiB/5.91 TiB, running
processes: 933
* disk free/total: 37.10 TiB/92.61 TiB
* bytes sent: 411.24 MB/s, received: 289.26 MB/s
* planned bullseye upgrades completion date: 2022-10-14
* [GitLab tickets][]: 183 tickets including...
* open: 0
* icebox: 151
* backlog: 14
* next: 9
* doing: 5
* needs review: 1
* needs information: 3
* (closed: 2755)
[Gitlab tickets]: https://gitlab.torproject.org/tpo/tpa/team/-/boards
Upgrade prediction graph lives at https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/bullseye/
We have managed to still speed up our upgrades progression from last
time, moving from December to October as a predicted completion
date. That's not as fast as last estimate (2 years acceleration!) but
it's still quite satisfying.
--
Antoine Beaupré
torproject.org system administration
Hi all :)
This is my monthly status report for May 2022.
Main activities during the period:
0. Onionprobe (an onion sites monitoring tool):
* Released version 1.0.0! With:
* Revised metrics.
* Sample Grafana dashboard!
* Prometheus configuration with alerting rules!
* Customizable Alertmanager configuration!
* Details at https://gitlab.torproject.org/tpo/onion-services/onionprobe/
* Deployed an instance for Sponsor 123:
* Using an Ansible role to be hopefully enhanced and released soon.
2. Onionmine (a wrapper for vanity address generation):
* Implemented batch operation.
* Added script to test keys.
* Included a wrapper for HARICA's "onion-csr" tool.
* Some other enhancements.
* Details at https://gitlab.torproject.org/tpo/onion-services/onionmine/
3. Other activities related to Sponsor 123 such as meetings,
devlelopment and support.
--
Silvio Rhatto
pronouns he/him
Hello everyone!
This is my monthly report for the month of May. With six Tor Browser
releases in last month a major part of my work was focussed on
collaborating on bug reports, gaining meaningful feedback and overall
user support work concerning the browser. With the upcoming Tor Browser
11.5 release we are seeing some major changes, so this month I have been
involved in testing the alpha and nightly builds and updating the
documentation [1]. We received a few bug reports for Tor Browser Android
in the last month, with repeated reports of the browser crashing at
launch [2] (the issue has been fixed in the latest stable release
11.0.13. woo!), the Tor process failing to bootstrap when links are
launched directly into the app [3] and extensions/add-ons unable to
install and/or not enabled in the browser [4]
We are about to move our cdr.link/zammad instance (Telegram user support
channel) [5] and I have been testing the test instance before we make
the migration to a new one.
That is all for the highlights from the last
month, following are the stats from our user support platforms:
## Frontdesk
Timeline : 01 May - 31 May 2022
Tickets:
new: 26
open: 5
resolved: 344
Breakdown of number of RT tickets received with respect to operating
system:
(Note: This includes tickets where the user mentioned the operating
system or it was evident from the issue they were running into and/or
enclosed screenshots.)
Windows - 10
macOS - 5
GNU/Linux - 3
Android - 14
Breakdown of most frequent tickets (at least 3 RT tickets):
1. 140 RT Tickets - How to use Tor Bridges in Russia. [6]
2. 52 RT Tickets - Private Bridge requests. This is not related to the
.ru censorship but requests from Tor users in China, Iran, etc. [7]
3. 4 RT Tickets - Tor Browser Android crashes on launch (the bug is
resolved now!) [1]
4. 4 RT Tickets - "Proxy Server refused connection" (Tor fails to
bootstrap) if link from other app are opened in TBA [2]
5. 3 RT Tickets - Can't install extensions on TBA [3]
6. 3 RT Tickets - Tor metrics showing geolocations of some relays
incorrectly [8]
## Tor Forum
Most popular topics in the Support category (in terms of no. of views):
1. Censorship circumvention: "如何在中国大陆绕过 GFW 防火长城连接到
Tor?" ("How to circumvent the Great Firewall and connect to Tor from
China?") [9]
2. Relay operator: "Unexpected path length 4 for exit circuit X, purpose
5" [10]
3. Relay operator: "(Issue with) Running a bridge in Russia" [11]
4. Relay operator: "Periodically disposing of current public IP on
bridge node, a good thing?" [12]
5. Censorship circumvention: "How can I use Tor in China where network
was blocked" [13]
Thanks,
-- Joydeep
[1]: https://gitlab.torproject.org/tpo/web/manual/-/issues/119
[2]: https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40212
[3]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40536
[4]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40606
[5]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40592
[6]: https://forum.torproject.net/t/tor-blocked-in-russia-how-to-circumvent-cens…
[7]: https://support.torproject.org/censorship/connecting-from-china/
[8]: https://gitlab.torproject.org/tpo/core/tor/-/issues/40336
[9]: https://forum.torproject.net/t/gfw-tor/3447
[10]: https://forum.torproject.net/t/unexpected-path-length-4-for-exit-circuit-x-…
[11]: https://forum.torproject.net/t/running-a-bridge-in-russia/3184
[12]: https://forum.torproject.net/t/periodically-disposing-of-current-public-ip-…
[13]: https://forum.torproject.net/t/how-can-i-use-tor-in-china-where-network-was…
Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-05-26-16.00.html
And our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Next meeting: Thursday June 9nd 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 check-in 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 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&…
* Sponsor 96
* https://gitlab.torproject.org/groups/tpo/-/milestones/24
== Announcements ==
* anti-censorship irc channel: #tor-anticensorship @ irc.oftc.net
== Discussion ==
Endless loop on the latest snowflake:
Tor NOTICE: Managed proxy "TorBrowser\Tor\PluggableTransports\snowflake-client.exe": broker failure timed out waiting for answer!
Tor NOTICE: Managed proxy "TorBrowser\Tor\PluggableTransports\snowflake-client.exe": connection failed timeout waiting for DataChannel.OnOpen
* Implement metrics to measure snowflake churn (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) is now under review. Comments are welcome (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…)
* count disctinct proxy ips, to see how fast they change
* enforce 2FA in gitlab
* all accounts with group commit access have 2FA in gitlab already :)
== Actions ==
*
== Interesting links ==
== Reading group ==
* We will discuss "Even Censors Have a Backup: Examining China's Double HTTPS Censorship Middleboxes" on June 23
* https://dl.acm.org/doi/10.1145/3473604.3474559
* 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): last updated 2022-06-02
Last week:
- updated gitlab CI to include go v1.18 (snowflake#40144)
- Remove redundant NAT check at standalone proxy startup (snowflake#40146)
- resolved snowflake#40145
- reviews
This week:
- continued work on conjure PT
- continue snowflake maintenance tasks
Needs help with:
dcf: 2022-06-02
Last week:
- set up access to snowflake-02 bridge site for shelikhoo https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- posted about other DTLS fingerprints that are being filtered in Russia https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss…
Next week:
- look at STATUS VERSION proposal https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/63
Help with:
meskio: 2022-06-02
Last week:
- use systemd to run bridgedb (team#72)
- update debian package for snowflake (snowflake#40143)
- don't use entropy in snowflake tests (snowflake!96)
- contact cymru about their builtin bridges, as they have an old version of obfs4proxy
Next week:
- start working on gettor (rdsys#105)
Shelikhoo: 2022-05-26
Last Week:
- [Merge Request] Add Distributed Snowflake Server Support (snowflake!87)
- [Merge Request] Distributed Snowflake Bridges (Javascript ver.) (snowflake-webext!29)
- [Merge Request] Implement metrics to measure snowflake churn (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) (snowflake!95)
- [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64)
- [Discussion & Deployment] Migrating Controlling git repo to Tor Gitlab Instance (shelikhoo/LogCollectorAncillary#5) <- awaiting/blocked
Next Week:
- [Coding] Distributed Snowflake Bridges (continue)
- [Coding & Deployment] Proposal: Centralized Probe Result Collector (anti-censorship/team#54)
- [Research & Coding] WebSocket + CDN Based Probe Control Connection Forwarder (shelikhoo/LogCollectorAncillary#3)
- [Merge Request] Implement metrics to measure snowflake churn (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…)
- [Research & Discussion] HTTPT & V2Ray related
Itchy Onion: 2022-06-02
Last week:
- work on s28 issue 81 (race conditions in broker)
This week:
- continue working on snowflake !93 (add tests)
- ongoing debugging with s28 (there are other issues, not sure if related to issue 81 yet)
- working on issue 40117 (display NAT log type to stderr in nonverbose mode)
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.