The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-11-30T16:16:39Zhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/19Cleanups and improvements on Tor specifications2023-11-30T16:16:39ZNick MathewsonCleanups and improvements on Tor specifications# About the project
* Contact: Nick Mathewson
* Chat: #tor-dev on `irc.oftc.net`
* Video room: <https://tor.meet.coop/nic-u9t-t6q-hmy>
# Participants
- Nick Mathewson
- etc
# Summary
We [recently][prop345] migrated our [protocol ...# About the project
* Contact: Nick Mathewson
* Chat: #tor-dev on `irc.oftc.net`
* Video room: <https://tor.meet.coop/nic-u9t-t6q-hmy>
# Participants
- Nick Mathewson
- etc
# Summary
We [recently][prop345] migrated our [protocol specifications] to [mdbook], in
preparation for a larger round of revisions and improvements.
This week, we'll be working on the follow-ups from that transition,
and other general improvements on the specifications.
## Project A: Simple mdbook-related followups
Our conversion process was largely a mechanical one, and there
is substantial opportunity for improving its results.
This might take the form of:
- Looking for instances of \`\`\` blocks that can instead be
formatted better as tables, indented text, or some other
kind of information.
- Looking for occurrences of "See section X.Y.Z above" or similar
text that can be turned into links.
- Looking over our existing links, and making sure that they are well
considred.
- Looking for misformatted text in the output, and correcting the
markdown that generated it.
- Making the resulting documentation better fit our themes and style guidelines.
This will not be a purely mechanical process. You will need to make
sure that you understand what you are reading well enough to be sure
that you aren't changing its meaning, that your links really are going
to the intended text, and so on.
## Project B: Revisions for clarity and consistency
This year marks the twentieth anniversary of our [first attempt] at a
protocol specification. Over the years, as our protocol grew,and as
our terminology evolved, we have revised and extended the specs bit
by bit, but seldom had a chance to consider their readability as a whole.
With this project, we will be looking for was to improve our
specifications as a whole, by fixing issues like:
- Inconsistent or outdated terminology
- Missing explanations
- Material without sensible motivation
- Lack of distinction between specification and analysis
- Illogical ordering and division of chapters
- Obscure writing
- Lack of overall introductions
- Historical notations of limited relevance
- Outdated notes about years-unsupported versions of Tor, or
plans from the distant past.
Again, this cannot be a mechanical process: you don't need to be an
_expert_ in the Tor protocols to work on this, but also you can't just
search and replace old terms for new ones, or rewrite text without
taking time to understand what it means.
# Skills
Before you begin, you should make sure that you can use git, edit
markdown, and make merge requests on <https://gitlab.torproject.org/>.
It would also be a good idea to make sure that you can build the
HTML-rendered spec website locally. There is a [script to do
that][build_html] in the specification repository; you will need
to make sure that you have Python and mdbook installed.
Finally, you should be comfortable reading and writing specification
documents of this type, and you should have some idea of how Tor
works.
# Links
[prop345]: https://spec.torproject.org/proposals/345-specs-in-mdbook.html
[protocol specifications]: https://spec.torproject.org/
[mdbook]: https://rust-lang.github.io/mdBook/
[build_html]: https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/bin/build_html.sh?ref_type=heads
[first attempt]: https://gitlab.torproject.org/tpo/core/tor/-/commit/858c611573167adb328e2359ad0c4a866070964eHackweek 2023Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/team/-/issues/225Review priorities for next year for each team2023-12-07T19:20:01ZGabagaba@torproject.orgReview priorities for next year for each team@micah @meskio @richard @donuts @gk @ahf @anarcat I'm sending you all invites to meet the first week of December to discuss priorities.@micah @meskio @richard @donuts @gk @ahf @anarcat I'm sending you all invites to meet the first week of December to discuss priorities.Gabagaba@torproject.orgGabagaba@torproject.org2023-12-08https://gitlab.torproject.org/tpo/tpa/team/-/issues/41358Please remove the PM job posting from the website2023-10-12T19:12:53ZErin WyattPlease remove the PM job posting from the websiteWe've received over 400 applicants, we are closing the position. Thank you!We've received over 400 applicants, we are closing the position. Thank you!anarcatanarcathttps://gitlab.torproject.org/tpo/team/-/issues/224Go over all projects for 20242023-12-07T19:20:05ZGabagaba@torproject.orgGo over all projects for 2024Gabagaba@torproject.orgGabagaba@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41356GitHub mirror for Onionbalance2023-10-18T16:55:55ZSilvio RhattoGitHub mirror for OnionbalanceThe [Onionbalance](https://onionbalance.readthedocs.io) codebase was recently [moved around](tpo/onion-services/onionbalance#10):
* From https://github.com/asn-d6/onionbalance to https://github.com/torproject/onionbalance.
* From https:...The [Onionbalance](https://onionbalance.readthedocs.io) codebase was recently [moved around](tpo/onion-services/onionbalance#10):
* From https://github.com/asn-d6/onionbalance to https://github.com/torproject/onionbalance.
* From https://gitlab.torproject.org/tpo/core/onionbalance to https://gitlab.torproject.org/tpo/onion-services/onionbalance.
Now I'd like to configure automatic pushes from Tor's GitLab to GitHub.
I'm aware of the [recommended procedure](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/gitlab#how-to-mirror-a-git-repository-from-gitlab-to-github) and have done it before, but I don't have admin access in the [GitHub repo](https://github.com/torproject/onionbalance) to proceed (my user on GitHub is [rhatto](https://github.com/rhatto/)).
Not sure if this is the right place to ask, but did so after finding a related issue (tpo/tpa/team#41246).Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/18Working on the content for the developer portal2023-11-30T16:16:39ZGabagaba@torproject.orgWorking on the content for the developer portal# About the project
* Contact: @gaba
* Chat: #tor-dev on `irc.oftc.net`
* Video room: https://tor.meet.coop/gab-tph-u9q-eo0
* Meet Monday, Tuesday, Wednesday, Thursday from 12UTC to 20UTC
# Participants
- @gaba
- you?
# Summary
...# About the project
* Contact: @gaba
* Chat: #tor-dev on `irc.oftc.net`
* Video room: https://tor.meet.coop/gab-tph-u9q-eo0
* Meet Monday, Tuesday, Wednesday, Thursday from 12UTC to 20UTC
# Participants
- @gaba
- you?
# Summary
The [developer portal](https://gitlab.torproject.org/tpo/web/dev/) has been on the back waiting for some time to get completed. At the beginning of this year Ura.Design worked on a [site/design](https://gitlab.torproject.org/tpo/web/dev/-/issues/6) for it. This is a project to get the content into the site and reviewing the information architecture.
## Project A : Get content into the portal
The content that we are planning to have in this portal is all over the place in repositories and wikis. With this project I will move the content to the dev portal, review the information architecture and organize the work that needs to happen next.
# Skills
- Gitlab
- Writing documentation
- MarkdownHackweek 2023Gabagaba@torproject.orgGabagaba@torproject.org2023-11-09https://gitlab.torproject.org/tpo/team/-/issues/221Sponsor 9 Report2023-11-30T18:35:57ZGabagaba@torproject.orgSponsor 9 ReportWrite report for sponsor 9 for previous phase (July 2022 to June 2023).Write report for sponsor 9 for previous phase (July 2022 to June 2023).Gabagaba@torproject.orgGabagaba@torproject.org2023-11-16https://gitlab.torproject.org/tpo/team/-/issues/219Budget for Translations into Turkmen2024-01-16T13:08:32ZGabagaba@torproject.orgBudget for Translations into TurkmenWe need to write the budget and scope to request Localization Lab for the translation for turkmen.
cc @emmapeelWe need to write the budget and scope to request Localization Lab for the translation for turkmen.
cc @emmapeelGabagaba@torproject.orgGabagaba@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41348Help needed with torspec migration (see proposal 345) hosting.2024-01-11T21:34:29ZNick MathewsonHelp needed with torspec migration (see proposal 345) hosting.Hi! As part of [proposal 345](https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/proposals/345-specs-in-mdbook.md), I want to migrate the rendered format of torspec.git to the web. We'll have a nice easy gitlab CI hook that get...Hi! As part of [proposal 345](https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/proposals/345-specs-in-mdbook.md), I want to migrate the rendered format of torspec.git to the web. We'll have a nice easy gitlab CI hook that gets run whenever the specs change, but after that point the whole process becomes a bit murky in my head.
To be concrete, here is what I'd like (if it's not too hard):
1. I'd like to know the right way to cause the CI hook to result in a pile of rendered HTML getting put on spec.tpo. This can replace the existing content of spec.tpo, which won't need to be on puppet any longer; I'll be sure to keep the links working.
2. If possible, I'd like a temporary subdomain (specs2.torproject.org? specs-demo.torproject.org?) for the script to target while to target while this is under development. This subdomain doesn't need to get CDN support, and it can get deleted completely after the migration is done and the CI hooks target the regular spec.tpo.
As an alternative to 2, we could just temporarily blow away spec.tpo, but that would put more time pressure on me to get it fixed fast, which might not be so great.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41347Move tor-pristine-upstream.git to GitLab2023-11-29T22:24:59ZJérôme Charaouilavamind@torproject.orgMove tor-pristine-upstream.git to GitLabDuring a work session with @weasel today about releasing new tor versions to our Debian repository we agreed we should move over `tor-pristine-upstream.git` to GitLab, as it currently lives only on git-rw.tpo.During a work session with @weasel today about releasing new tor versions to our Debian repository we agreed we should move over `tor-pristine-upstream.git` to GitLab, as it currently lives only on git-rw.tpo.legacy Git infrastructure retirement (TPA-RFC-36)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41346Migrate pauli to gnt-dal2023-10-11T12:35:03ZJérôme Charaouilavamind@torproject.orgMigrate pauli to gnt-dalWhile working on tpo/tpa/team#41341 we figured out that the latency between gnt-dal and gnt-fsn is likely the cause of additional delays when running a Puppet agent run, when `pauli` is configured to use the `puppetdb-01` PuppetDB backen...While working on tpo/tpa/team#41341 we figured out that the latency between gnt-dal and gnt-fsn is likely the cause of additional delays when running a Puppet agent run, when `pauli` is configured to use the `puppetdb-01` PuppetDB backend.
We decide to attempt to migrate `pauli` from gnt-fsn to gnt-dal in the hope that this will remove the extraneous delays.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2023-10-12https://gitlab.torproject.org/tpo/tpa/team/-/issues/41343Onionoo backends out of disk space2023-11-20T21:57:17ZHiroOnionoo backends out of disk spaceSeems the onionoo backends have run out of disk space on /srv. Can we increase space? I think if we could add 10 More GB to each host at least (ideally 20) it would be ok.Seems the onionoo backends have run out of disk space on /srv. Can we increase space? I think if we could add 10 More GB to each host at least (ideally 20) it would be ok.anarcatanarcathttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/17Clean up and improve the user support FAQ text2023-11-30T16:16:39ZRoger DingledineClean up and improve the user support FAQ text# About the project
* Contact: Roger Dingledine
* Chat: #tor-www on `irc.oftc.net` / [#tor-www](https://matrix.to/#/#tor-www:matrix.org) on matrix
* Video room: https://tor.meet.coop/pav-g4m-iys-h7n (kick off meeting on Monday, 06 No...# About the project
* Contact: Roger Dingledine
* Chat: #tor-www on `irc.oftc.net` / [#tor-www](https://matrix.to/#/#tor-www:matrix.org) on matrix
* Video room: https://tor.meet.coop/pav-g4m-iys-h7n (kick off meeting on Monday, 06 November at 14 UTC)
* Pad: https://pad.riseup.net/p/improve-support-faqs-hackweek-qwjebqwjqedwqebdj
# Participants
- Roger Dingledine
- ebanam
- @gus
- you?
# Summary
Tor has a huge variety of FAQ entries on support.torproject.org, copied over from the original FAQ, the abuse FAQ, etc. When we made support.tpo, we only took some of the entries. Then we updated those over the years, but actually we have mostly left them alone -- I imagine it's hard for most individuals to decide to change one of these support entries, because they don't know who needs to buy in, or they worry that somebody else thinks it's perfect the way it is.
Let's look again at the big picture of which entries are useful, which ones are right, and whether there are any missing. The outcome will be a better support site.
# Skills
We will need people who know how to technical write, people who know what problems/questions/concerns Tor users encounter, people who know how Tor and Tor Browser work, people who have an interest in Tor comms and framing, and people who know basic html/markup. These don't all have to be the same people! :)
# LinksHackweek 2023Roger DingledineRoger Dingledinehttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41341Deploy new PuppetDB server2023-10-04T21:47:02ZJérôme Charaouilavamind@torproject.orgDeploy new PuppetDB serverAs part of tpo/tpa/team#40696 we decided to deploy a new PuppetDB server alongside the old puppet master.
The hope is we can make progress on the Puppet upgrade plan by replacing the current PuppetDB running on `pauli` with this new one.As part of tpo/tpa/team#40696 we decided to deploy a new PuppetDB server alongside the old puppet master.
The hope is we can make progress on the Puppet upgrade plan by replacing the current PuppetDB running on `pauli` with this new one.Debian 12 bookworm upgradeJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/team/-/issues/217Q3 Reports for DRL sponsored projects2023-10-30T13:45:49ZGabagaba@torproject.orgQ3 Reports for DRL sponsored projects61
- [x] Write the last report for the project
- [x] Gather indicators https://nc.torproject.net/f/462462
- [x] Send final docs to team for review
- [x] Send final docs to Bekeela and Isabela for review
96
- [x] Send mail [requesting i...61
- [x] Write the last report for the project
- [x] Gather indicators https://nc.torproject.net/f/462462
- [x] Send final docs to team for review
- [x] Send final docs to Bekeela and Isabela for review
96
- [x] Send mail [requesting info](http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/sponsor96-next-report)
- [x] Get narrative into the report
- [x] Gather indicators
- [x] Send final docs to team for review
- [x] Send final docs to Bekeela and Isabela for review
101
- [x] Send mail [requesting info](https://pad.riseup.net/p/sponsor101-next-report)
- [x] Get narrative into the report
- [x] Gather indicators
- [x] Send final docs to team for review
- [x] Send final docs to Bekeela and Isabela for review
112
- [x] Send mail [requesting info](https://pad.riseup.net/p/sponsor112-next-report)
- [x] Get narrative into the report
- [x] Gather indicators
- [x] Send final docs to team for review
- [x] Send final docs to Bekeela and Isabela for reviewGabagaba@torproject.orgGabagaba@torproject.org2023-10-25https://gitlab.torproject.org/tpo/tpa/team/-/issues/41336mandos not working for dal-rescue-022023-10-02T19:48:53ZJérôme Charaouilavamind@torproject.orgmandos not working for dal-rescue-02When rebooting `dal-rescue-02`, it gets stuck in the initramfs, at the luks prompt.
Normally, mandos takes care of supplying the password to allow the boot process to complete, but it's not working.
I checked the configuration on the m...When rebooting `dal-rescue-02`, it gets stuck in the initramfs, at the luks prompt.
Normally, mandos takes care of supplying the password to allow the boot process to complete, but it's not working.
I checked the configuration on the mandos server and at a glance it checks out. The problem is probably that the luks password in mandos is not present as a luks key slot on `dal-rescue-02`.anarcatanarcathttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/16Collaborative editing2023-11-30T16:16:40ZSilvio RhattoCollaborative editing# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @meskio
- @rhatto (I'm looking for someone to be the new maintainer/coordinator/asignee for this proposal, as I ma...# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @meskio
- @rhatto (I'm looking for someone to be the new maintainer/coordinator/asignee for this proposal, as I may participate only marginally on it)
- @micah
- @shelikhoo (Partially)
# Summary
This is about enhancing ways we deal with [Etherpads](https://etherpad.org/).
## Project A - Nextcloud collaborative editor
* [x] Try the Nextcloud collaborative editor as an attempt at reducing the number of external tools we have to deal with.
## Project B - Etherpad
* [x] Etherpad archival utility/GitLab bot (as ticket comments, merge requests etc). Use case: add pad links into the ticket description, and the bot will act regularly, submitting changes somewhere. Maybe this already exists? We may also try to expand this use case for other document sources/platforms.
* [ ] Investigate the possibility to run our own etherpad, and not use the pad cleanup that Riseup does, and then the pads can be integrated with Nextcloud.
## Project C - CryptPad
* [x] Etherpad may be winding down development, and we should re-consider [CryptPad](https://cryptpad.fr/), which has a number of document management utilities bundled with it.
## Project D - HedgeDoc
* [ ] Try [HedgeDoc](https://hedgedoc.org/), "an open-source, web-based, self-hosted, collaborative markdown editor".
# Skills
What are the skills needed for the project:
* Not sure yet! Maybe no specific skills needed.
* Etherpad autosaving may depend on the knowledge needed to create GitLab bots and other scripts.
# LinksHackweek 2023micahmicah@torproject.orgmicahmicah@torproject.org2023-11-09https://gitlab.torproject.org/tpo/tpa/team/-/issues/41334Endpoint for containers.torproject.org is confused2023-09-25T16:22:02Zmicahmicah@torproject.orgEndpoint for containers.torproject.org is confusedIf I attempt to pull an image from the container registry like this:
```
$ podman pull containers.torproject.org/tpo/tpa/container-images:bookworm
```
I get this error:
```
Error: initializing source docker://containers.torproject.org...If I attempt to pull an image from the container registry like this:
```
$ podman pull containers.torproject.org/tpo/tpa/container-images:bookworm
```
I get this error:
```
Error: initializing source docker://containers.torproject.org/tpo/tpa/container-images:bookworm: pinging container registry containers.torproject.org: Get "https://containers.torproject.org/v2/": x509: certificate is valid for gitlab-02.torproject.org, not containers.torproject.org
```Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41333Update torbrowser@torproject.org key in wkd2023-09-25T20:46:47ZboklmUpdate torbrowser@torproject.org key in wkdIt is possible to get the torbrowser gpg key with:
```
gpg --auto-key-locate nodefault,wkd --locate-keys torbrowser@torproject.org
```
The key that is returned by this needs to be updated for a new expiration date on the subkey. The upd...It is possible to get the torbrowser gpg key with:
```
gpg --auto-key-locate nodefault,wkd --locate-keys torbrowser@torproject.org
```
The key that is returned by this needs to be updated for a new expiration date on the subkey. The updated key is:
https://people.torproject.org/~boklm/tmp/_torbrowser_extended_2023.ascanarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41330Create a `lox` user on rdsys-frontend-012023-10-23T18:30:48ZCecylia BocovichCreate a `lox` user on rdsys-frontend-01On the rdsys-frontend-01 machine, we're going with the plan to create a user per service and setup systemd for that user (see https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/167#note_2943424)). We're planning to deploy t...On the rdsys-frontend-01 machine, we're going with the plan to create a user per service and setup systemd for that user (see https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/167#note_2943424)). We're planning to deploy the lox distributor and would like a user for that service.
cc @meskio @onyinyanganarcatanarcat