The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-04-01T03:02:39Zhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40564TPA-RFC-41: Consider replacing or fixing Schleuder2023-04-01T03:02:39ZAlexander Færøyahf@torproject.orgTPA-RFC-41: Consider replacing or fixing SchleuderHello,
The title is a bit of a joke, but the gist of the issue here is that Schleuder seems to make everybody sad and miserable.
Over the past few weeks we had to do:
- Transition the Community Council list to new members. That caused...Hello,
The title is a bit of a joke, but the gist of the issue here is that Schleuder seems to make everybody sad and miserable.
Over the past few weeks we had to do:
- Transition the Community Council list to new members. That caused troubles where we needed help from TPA.
- @nickm wrote a very important email to the Network Team Security list which nobody received. @dgoulet got the log out which gave the error message, but @nickm has not been notified about this automatically from the system.
- Issues with handling key updates when the keys isn't on the currently-functional-whatever-that-may-mean OpenPGP keyserver.
- It seems like we have /some/ overlap between tor-security@ and network-team-security@, but maybe we should just consolidate these two into a single end-point for such reports? Since I'm not on the former: does the browser team gets as many security issues that way as the network team does?
We don't use Schleuder much in the organization right now. Only for "sensitive" topics such as the Community Council, and the different methods to report security issues to us.
Since https://gitlab.com/gitlab-org/gitlab/-/issues/222908 is still open, Gitlab doesn't seem to be the sole solution to this issue unfortunately and wouldn't work in the CC case at all :-/
Can we try to come up with an alternative?
CC'ing @cohosh here too as CC contact.
CC'ing @arma and @sysrqb as they are on tor-security@ too.
update: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-41-schleuder-retirement drafted
next steps:
- [ ] retire network-team-security@
- [ ] decide what to do with tor-security-encrypted@
- [ ] decide what to do with tor-security@
- [ ] make a ticket to setup a new VM for schleuder and setup the web interface (see also tpo/tpa/team#40981)old service retirement 2023anarcatanarcat2022-12-01https://gitlab.torproject.org/tpo/community/hackweek/-/issues/29Document how to verify reproducibility of build of a mullvad/tor browser release2023-11-30T16:16:39ZboklmDocument how to verify reproducibility of build of a mullvad/tor browser release# About the project
* Contact: @boklm
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: no
# Participants
- @boklm
# Summary
I think many users don't know that our builds are reproducible, or how they can rebuild to verify...# About the project
* Contact: @boklm
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: no
# Participants
- @boklm
# Summary
I think many users don't know that our builds are reproducible, or how they can rebuild to verify that they get a matching build.
We could generate a `reproducible-build.txt` file in the release directory containing the following informations:
* which git repository to clone
* which commit to checkout
* which command to use to start the build
* which sha256sums to expect after the build finished
* how to remove embedded signatures from exe and mar files we publish to check that they match the unsigned build
# Skills
Need to know how to build Tor Browser.
# Links
* tpo/applications/tor-browser-build#40997Hackweek 2023boklmboklmhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/22Arti key manager documentation2023-11-30T16:16:39Zgabi-250Arti key manager documentation# About the project
* Contact: @gabi-250
* Chat: #tor-dev on `irc.oftc.net`
* Video room: TBD
# Participants
- @gabi-250
- etc
# Summary
The Arti team has been implementing a key management backend for handling the
various keys a...# About the project
* Contact: @gabi-250
* Chat: #tor-dev on `irc.oftc.net`
* Video room: TBD
# Participants
- @gabi-250
- etc
# Summary
The Arti team has been implementing a key management backend for handling the
various keys and certificates required by Arti to operate (see
https://gitlab.torproject.org/tpo/core/arti/-/issues/728 for a brief
overview).
The projects I'm proposing here aim to improve the various bits of documentation related to key
management in Arti.
## Project A: Set up a protocol name registry
The main (and currently only) Arti key store is an on-disk store that stores
keys in OpenSSH key format.
Some of the key types we need to support don't have a
predefined SSH public key [algorithm name], so we've had to
define several custom SSH algorithm names (for example, we have a custom
algorithm name for x25519 keys, which don't have a predefined algorithm name).
See
https://gitlab.torproject.org/tpo/core/arti/-/issues/936 and
https://gitlab.torproject.org/tpo/core/arti/-/issues/1049 for more details.
As per [RFC4251 § 6], our custom ssh algorithm names use the
`<something@subdomain.torproject.org>` format.
**In order to manage the local
namespacing of our (Tor Project's) custom SSH algorithm names, we will need a
protocol name registry**. This protocol name registry will live in
[torspec](https://gitlab.torproject.org/tpo/core/torspec) repo.
This [comment] lists the algorithm strings that will need to be documented, and
can be used as a starting point for this project.
## Project B: Improve documentation in the tor-keymgr crate
I think the documentation of the `tor-keymgr` crate could use some improvements:
* the `ArtiNativeKeystore` docs are very sparse (i.e. we should at least
document the key format it's using)
* it would be nice to have some docs explaining how to implement a custom key
store
* it would be nice to have some docs explaining how to mock a `Keystore`
* etc
## Project C: Document Arti's future key management CLI
We will eventually want to have a CLI for managing keys in Arti.
We should document various use-cases for it, and the corresponding command
invocation (i.e. its arguments).
(This may or may not be within the scope of Hackweek).
# Skills
* Git/GitLab.
* Markdown.
* Writing documentation.
Project A requires some knowledge (or willingness to learn) about
the OpenSSH key format used for keys stored in the Arti key store.
Project B requires some knowledge (or willingness to learn) about
the internals of Arti's key manager/key store implementations.
# Links
* a sketch of the [key manager/keystore
APIs](https://gitlab.torproject.org/tpo/core/arti/-/blob/8598f8902ed76d3302701934b86bb54b74a4326f/doc/dev/notes/key-management.md)
we have in Arti
* the currently supported key types are listed
[here](https://gitlab.torproject.org/tpo/core/arti/-/blob/8598f8902ed76d3302701934b86bb54b74a4326f/doc/dev/notes/key-management-paths.md)
* a more comprehensive (but somewhat out of date) list of keys that we want to
support can be found
[here](https://gitlab.torproject.org/tpo/core/arti/-/blob/8598f8902ed76d3302701934b86bb54b74a4326f/doc/dev/notes/key-management-keygen.md)
[algorithm name]: https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-19
[RFC4251 § 6]: https://www.rfc-editor.org/rfc/rfc4251.html#section-6
[comment]: https://gitlab.torproject.org/tpo/core/arti/-/blob/8598f8902ed76d3302701934b86bb54b74a4326f/crates/tor-keymgr/src/key_type/ssh.rs#L22-91Hackweek 2023gabi-250gabi-250https://gitlab.torproject.org/tpo/community/hackweek/-/issues/20Improve Lox Documentation2023-11-30T16:16:40ZonyinyangImprove Lox Documentation# About the project
* Contact: @onyinyang
* Chat: #tor-anticensorship on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @onyinyang
- anyone else that wants to join
# Summary
This is about enhancing the documentation...# About the project
* Contact: @onyinyang
* Chat: #tor-anticensorship on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @onyinyang
- anyone else that wants to join
# Summary
This is about enhancing the documentation for [Lox](https://gitlab.torproject.org/tpo/anti-censorship/lox). Lox will be deployed in alpha early next year. We currently have a Wiki as well as a Lox workspace with some incomplete documentation. Now that development towards the alpha is nearing completion, it would be a good time to make sure that documentation is more comprehensive and up to date.
## Project A - Update workspace repository descriptions, build instructions, etc.
* [x] Ensure that each repository in the Lox workspace has an up to date README with comprehensive build/deployment instructions and other information that a user/developer might need
* [x] Ensure that each Lox crate is prepared for publication on `crates.io`
## Project B - Update Lox wiki to provide a better overview of Lox as well as each of the interacting systems and how they work together
* [ ] Ensure that the Lox wiki has a comprehensive overview of Lox as well as the related systems it interacts with
* [ ] Include documentation for users based on [browser UI](https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42036#note_2960089)
# Skills
What are the skills needed for the project:
* Knowledge of Lox
# LinksHackweek 2023onyinyangonyinyanghttps://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/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/network-health/metrics/tagtor/-/issues/24Allow grouping untagged relays2024-03-13T07:38:24ZGeorg KoppenAllow grouping untagged relaysIn #17 we added search functionality to find tagged relays (with arbitrary tags), We should have an option as well to list relays not tagged by anybody.In #17 we added search functionality to find tagged relays (with arbitrary tags), We should have an option as well to list relays not tagged by anybody.TagTor is completed for its scope in Sponsor 112HiroHirohttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/15Onion Reveal coding and documenting2023-12-11T09:46:02ZSilvio RhattoOnion Reveal coding and documenting# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
- @gus
- etc
# Summary
This is a proposal to write a [reveal.js](https://revealjs.com/) compiler similar...# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
- @gus
- etc
# Summary
This is a proposal to write a [reveal.js](https://revealjs.com/) compiler similar to [Onion TeX Slim][].
[Onion TeX Slim]: https://gitlab.torproject.org/rhatto/onion-tex-slim
## Project A - Writing
The first project in this proposal would be to actually write Onion Reveal. This software could work like this:
* [x] Use a Makefile/script target that traverses a folder looking for `.md` files.
* [x] Then it would build the HTML slides using a pandoc reveal template.
* [x] With CI/CD for automation, in a way that's easy to integrate into existing projects.
* [x] Localization support.
* [ ] With support for QR code generation, so it's easy to embed QR codes into slides.
Examples:
* [Files · main · The Tor Project / Web / community · GitLab](https://gitlab.torproject.org/tpo/web/community/-/tree/main)
* [templates/slideshow.html · main · The Tor Project / Web / community](https://gitlab.torproject.org/tpo/web/community/-/blob/main/templates/slideshow.html)
* [models/slideshow.ini · main · The Tor Project / Web / community](https://gitlab.torproject.org/tpo/web/community/-/blob/main/models/slideshow.ini)
* [assets/static/revealjs/dist/theme/tor.css · community](https://gitlab.torproject.org/tpo/web/community/-/blob/main/assets/static/revealjs/dist/theme/tor.css)
* [Helping Survivors of Domestic Violence](https://community.torproject.org/training/resources/helping-survivors/)
## Project B - Trying
* [x] Use this project to build some presentations:
* [x] Tor Training materials: tpo/community/training#122.
Related issues:
* [Make Tor training slides compatible with Reveal JS format (#268) · community](https://gitlab.torproject.org/tpo/web/community/-/issues/268)
Examples:
* [Tor Project | Helping survivors of domestic violence](https://community.torproject.org/training/resources/helping-survivors/)
* [content/training/resources/helping-survivors/contents.lr · community](https://gitlab.torproject.org/tpo/web/community/-/blob/main/content/training/resources/helping-survivors/contents.lr)
# Skills
Some knowledge in the following technologies may be needed in order to participate:
* Git/GitLab.
* Markdown.
* Writing documentation.
* Basic scripting (Python, shell).
# LinksHackweek 2023Silvio RhattoSilvio Rhatto2023-11-09https://gitlab.torproject.org/tpo/community/hackweek/-/issues/14Onion TeX Slim enhancements2023-11-30T16:16:39ZSilvio RhattoOnion TeX Slim enhancements# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
# Summary
This proposal is about making some enhancements to [Onion TeX Slim][].
[Onion TeX Slim]: http...# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
# Summary
This proposal is about making some enhancements to [Onion TeX Slim][].
[Onion TeX Slim]: https://gitlab.torproject.org/rhatto/onion-tex-slim
## Project A - Improving
* [~] Dockerfile for local builds. Moved to tpo/community/onion-tex-slim#5.
* [~] Test and improve the LaTeX templates. Moved to tpo/community/onion-tex-slim#6.
* [~] Add more functionality (graphics etc). Moved to tpo/community/onion-tex-slim#7.
* [~] Localization support, at least for the Markdown/Pandoc version. Moved to tpo/community/onion-tex-slim#2.
* [~] Make easier to add [Onion TeX Slim][] support in a `slides/` or `docs/slides` folder. Moved to tpo/community/onion-tex-slim#8.
## Project B - Trying
* [x] Use this project to build some presentations:
* [x] In the [Tor Community Training repository](https://gitlab.torproject.org/tpo/community/training/).
# Skills
Some knowledge in the following technologies may be needed in order to participate:
* Git/GitLab.
* Markdown.
* LaTeX.
* Basic scripting (Python, shell).
# LinksHackweek 2023Silvio RhattoSilvio Rhatto2023-11-09https://gitlab.torproject.org/tpo/community/hackweek/-/issues/13Onion MkDocs tryout2023-11-30T16:16:40ZSilvio RhattoOnion MkDocs tryout# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
- @gus
- etc
# Summary
This is a proposal to try [Onion MkDocs][] for documenting things at Tor.
[Onion...# About the project
* Contact: @rhatto
* Chat: #tor-dev on `irc.oftc.net`
* Video room: to be defined.
# Participants
- @rhatto
- @gus
- etc
# Summary
This is a proposal to try [Onion MkDocs][] for documenting things at Tor.
[Onion MkDocs]: https://rhatto.pages.torproject.net/onion-mkdocs/
## Project A - Support
* [x] Provide support for people/teams that want to convert their wikis
to or have docs for their projects using [Onion MkDocs][].
* [x] Improve [Onion MkDocs][] stylesheet, plugins etc.
* [x] Improve [Onion MkDocs][] documentation.
## Project B - Convert
* [x] Convert some GitLab wikis to GitLab pages using Onion MkDocs:
* [x] Overview:
https://gitlab.torproject.org/tpo/tpa/team/-/issues/41119#note_2898441
* [x] Candidates for merge requests:
* [x] The Hackweek project itself:
https://gitlab.torproject.org/tpo/community/hackweek, with site now available
at https://tpo.pages.torproject.net/community/hackweek/
* [~] Onion Support Wiki:
https://gitlab.torproject.org/tpo/onion-services/onion-support/. To be done on Project C below.
* [x] Tor Policies repository:
https://gitlab.torproject.org/tpo/community/policies/-/issues/3
## Project C - Investigate
* [x] Investigate how Onion MkDocs could be a [TPA-RFC-38 wiki replacement (#40909) · TPA / TPA team](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40909) ([tpa rfc 38 new wiki service](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service)):
* [x] One approach would be to create a script that import content from some existing GitLab wikis into a single Onion MkDocs instance, to see how it would like to have a convergent "documentation integration" place. How it could be structured? Could it be easily searchable? What would be the best practices for this?
# Skills
Some knowledge in the following technologies may be needed in order to participate:
* Git/GitLab.
* Markdown.
* Basic scripting (Python, shell).
# LinksHackweek 2023Silvio RhattoSilvio Rhatto2023-11-09https://gitlab.torproject.org/tpo/network-health/metrics/tagtor/-/issues/20Tagging a relay in a family should get the tag for all relays of the same family2023-09-28T15:50:23ZGeorg KoppenTagging a relay in a family should get the tag for all relays of the same familyIf one tags a relay, say with `gk-knows`, then what that means is not that I know the relay but that I know the *operator*: we use the relays as means to say something about the operator as that helps us understand e.g. what fraction of ...If one tags a relay, say with `gk-knows`, then what that means is not that I know the relay but that I know the *operator*: we use the relays as means to say something about the operator as that helps us understand e.g. what fraction of Tor traffic is visible for a certain entity. Thus, if we tag a relay with tag X we should make sure all the family members get the tag X as well.TagTor is completed for its scope in Sponsor 112HiroHirohttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/10Issue template for Hackweek proposals2023-11-30T16:17:39ZSilvio RhattoIssue template for Hackweek proposalsCreate an issue template for Hackweek proposals, ref. [ORGANIZE-PRE-HACKWEEK](https://gitlab.torproject.org/tpo/community/hackweek/-/blob/main/ORGANIZE-PRE-HACKWEEK.md).Create an issue template for Hackweek proposals, ref. [ORGANIZE-PRE-HACKWEEK](https://gitlab.torproject.org/tpo/community/hackweek/-/blob/main/ORGANIZE-PRE-HACKWEEK.md).Hackweek 2023Gabagaba@torproject.orgGabagaba@torproject.orghttps://gitlab.torproject.org/tpo/community/outreach/-/issues/40033Video creation + production for bridges how to2023-09-27T22:41:22ZnicobVideo creation + production for bridges how toFor the objective 2 (Connect target audiences with resources to use Tor in their language) of sponsor 134, we need to create a demonstration video on how to use bridges in English to be translated to Arabic, Chinese, & Swahili.
Video sc...For the objective 2 (Connect target audiences with resources to use Tor in their language) of sponsor 134, we need to create a demonstration video on how to use bridges in English to be translated to Arabic, Chinese, & Swahili.
Video script: [Google doc](https://docs.google.com/document/d/1L9VC9RDkraJfmg0Ofn4yZIpsuohJTti6h5KYUujXlsk/edit)
- [x] Script complete and broke down screen by screen (c/o Raya)
- [x] Storyboarding
- [x] Voiceover (c/o Raya)
- [x] Organizing graphic assets including product shots, screen recordings
- [x] Custom intro/outro/transitions
- [x] Editing all components together into single videoSponsor 134: Localizing Tor tools and documentation into Arabic, Chinese, and Swahilinicobnicob2023-07-14https://gitlab.torproject.org/tpo/web/manual/-/issues/144Add Kiswahili translation2023-05-22T06:54:00ZemmapeelAdd Kiswahili translationWe are almost ready to release the Kiswahili translation.
We only need to fix some strings, and the review.We are almost ready to release the Kiswahili translation.
We only need to fix some strings, and the review.Sponsor 134: Localizing Tor tools and documentation into Arabic, Chinese, and Swahiliemmapeelemmapeel2023-05-22https://gitlab.torproject.org/tpo/community/outreach/-/issues/40027Give a live training abou Tor's tools and project for IRI event2023-10-12T15:15:31ZGabagaba@torproject.orgGive a live training abou Tor's tools and project for IRI eventAs part of Sponsor 134, "Objective 3: Educate IRI and allies on new Tor resources", we are working on the following activity:
Activity 3.1 Demonstration of tools at IRI event
We will give a live training to explain Tor, demonstrate too...As part of Sponsor 134, "Objective 3: Educate IRI and allies on new Tor resources", we are working on the following activity:
Activity 3.1 Demonstration of tools at IRI event
We will give a live training to explain Tor, demonstrate tools and highlight work completed in this project and demonstrate newly available resources for the IRI audience. The live training will be recorded.
Training will happen in September or October. We will coordinate with IRI the date.Sponsor 134: Localizing Tor tools and documentation into Arabic, Chinese, and Swahilirayaraya2023-10-11https://gitlab.torproject.org/tpo/community/l10n/-/issues/40094Localize materials into Arabic, Chinese, Farsi & Swahili2023-09-06T15:45:21ZGabagaba@torproject.orgLocalize materials into Arabic, Chinese, Farsi & SwahiliIn the context of [sponsor 134](https://gitlab.torproject.org/groups/tpo/-/milestones/45#tab-issues) localize the following materials:
- [ ] [the Tor Project’s main website](https://hosted.weblate.org/projects/tor/tpo-web/) (torproject...In the context of [sponsor 134](https://gitlab.torproject.org/groups/tpo/-/milestones/45#tab-issues) localize the following materials:
- [ ] [the Tor Project’s main website](https://hosted.weblate.org/projects/tor/tpo-web/) (torproject.org)
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/tpo-web/svg-badge.svg" alt="Translation status" />
- [x] Chinese: <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/tpo-web/svg-badge.svg" alt="Translation status" />
- [ ] Persian: <img src="https://hosted.weblate.org/widgets/tor/fa/tpo-web/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/tpo-web/svg-badge.svg" alt="Translation status" />
- [x] censorship circumvention portals (gettor and bridges.torproject.org) - bridges is not available for translation yet
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Chinese: <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Persian: <img src="https://hosted.weblate.org/widgets/tor/fa/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] the [Tor Browser manual](https://hosted.weblate.org/projects/tor/tor-browser-user-manual/)
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/tor-browser-user-manual/svg-badge.svg" alt="Translation status" />
- [x] Chinese: <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/tor-browser-user-manual/svg-badge.svg" alt="Translation status" />
- [x] Persian: <img src="https://hosted.weblate.org/widgets/tor/fa/tor-browser-user-manual/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/tor-browser-user-manual/svg-badge.svg" alt="Translation status" />
- [x] our [support portal](https://hosted.weblate.org/projects/tor/support-portal/)
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/support-portal/svg-badge.svg" alt="Translation status" />
- [x] Chinese: <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/support-portal/svg-badge.svg" alt="Translation status" />
- [x] Persian: <img src="https://hosted.weblate.org/widgets/tor/fa/support-portal/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/support-portal/svg-badge.svg" alt="Translation status" />
_Farsi translations will be done by Localization Lab, paid by Tor._
_Chinese, Arabic and Swahili will be done by Localization Lab, paid by IRI._Sponsor 134: Localizing Tor tools and documentation into Arabic, Chinese, and Swahiliemmapeelemmapeel2023-08-11https://gitlab.torproject.org/tpo/community/l10n/-/issues/40093Localize tools into Arabic, Chinese (China), Farsi & Swahili2023-09-06T15:45:16ZGabagaba@torproject.orgLocalize tools into Arabic, Chinese (China), Farsi & SwahiliIn the context of [sponsor 134](https://gitlab.torproject.org/groups/tpo/-/milestones/45#tab-issues) we need to localize the following tools:
- [x] [GetTor](https://hosted.weblate.org/projects/tor/gettor-website/) (used to deliver Tor ...In the context of [sponsor 134](https://gitlab.torproject.org/groups/tpo/-/milestones/45#tab-issues) we need to localize the following tools:
- [x] [GetTor](https://hosted.weblate.org/projects/tor/gettor-website/) (used to deliver Tor Browser when torproject.org is censored):
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Chinese (China): <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Farsi: <img src="https://hosted.weblate.org/widgets/tor/fa/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/gettor-website/svg-badge.svg" alt="Translation status" />
- [x] [OnionShare](https://hosted.weblate.org/projects/onionshare/) (Tor-based file-sharing tool):
- [x] Arabic: Android: <img src="https://hosted.weblate.org/widgets/onionshare/ar/onionshare-android/svg-badge.svg" alt="Translation status" />- Desktop: <img src="https://hosted.weblate.org/widgets/onionshare/ar/translations/svg-badge.svg" alt="Translation status" /> - iOS: <img src="https://hosted.weblate.org/widgets/onionshare/ar/onionshare-ios/svg-badge.svg" alt="Translation status" /> - iOS permissions: <img src="https://hosted.weblate.org/widgets/onionshare/ar/onionshare-ios-permissions/svg-badge.svg" alt="Translation status" /> - iOS plurals: <img src="https://hosted.weblate.org/widgets/onionshare/ar/onionshare-ios-plurals/svg-badge.svg" alt="Translation status" />
- [x] Chinese (China): Android: <img src="https://hosted.weblate.org/widgets/onionshare/zh_Hans/onionshare-android/svg-badge.svg" alt="Translation status" />Desktop: <img src="https://hosted.weblate.org/widgets/onionshare/zh_Hans/onionshare-ios-plurals/svg-badge.svg" alt="Translation status" /> - iOS: <img src="https://hosted.weblate.org/widgets/onionshare/zh_Hans/onionshare-ios/svg-badge.svg" alt="Translation status" /> -iOS permissions: <img src="https://hosted.weblate.org/widgets/onionshare/zh_Hans/onionshare-ios-permissions/svg-badge.svg" alt="Translation status" /> - iOS plurals: <img src="https://hosted.weblate.org/widgets/onionshare/zh_Hans/onionshare-ios-plurals/svg-badge.svg" alt="Translation status" />
- [ ] Farsi: Android: <img src="https://hosted.weblate.org/widgets/onionshare/fa/onionshare-android/svg-badge.svg" alt="Translation status" />- Desktop: <img src="https://hosted.weblate.org/widgets/onionshare/fa/translations/svg-badge.svg" alt="Translation status" /> - iOS: <img src="https://hosted.weblate.org/widgets/onionshare/fa/onionshare-ios/svg-badge.svg" alt="Translation status" /> - iOS permissions: <img src="https://hosted.weblate.org/widgets/onionshare/fa/onionshare-ios-permissions/svg-badge.svg" alt="Translation status" /> - iOS plurals: <img src="https://hosted.weblate.org/widgets/onionshare/fa/onionshare-ios-plurals/svg-badge.svg" alt="Translation status" />
- [ ] Swahili: Android: <img src="https://hosted.weblate.org/widgets/onionshare/sw/onionshare-android/svg-badge.svg" alt="Translation status" />- Desktop: <img src="https://hosted.weblate.org/widgets/onionshare/sw/translations/svg-badge.svg" alt="Translation status" /> - iOS: <img src="https://hosted.weblate.org/widgets/onionshare/sw/onionshare-ios/svg-badge.svg" alt="Translation status" /> - iOS permissions: <img src="https://hosted.weblate.org/widgets/onionshare/sw/onionshare-ios-permissions/svg-badge.svg" alt="Translation status" /> - iOS plurals: <img src="https://hosted.weblate.org/widgets/onionshare/sw/onionshare-ios-plurals/svg-badge.svg" alt="Translation status" />
- [x] [OnionSproutBot](https://hosted.weblate.org/projects/tor/onionsprouts-bot/) (Telegram bot tool that helps users circumvent censorship):
- [x] Arabic: <img src="https://hosted.weblate.org/widgets/tor/ar/onionsprouts-bot/svg-badge.svg" alt="Translation status" />
- [x] Chinese (China): <img src="https://hosted.weblate.org/widgets/tor/zh_Hans/onionsprouts-bot/svg-badge.svg" alt="Translation status" />
- [x] Farsi: <img src="https://hosted.weblate.org/widgets/tor/fa/onionsprouts-bot/svg-badge.svg" alt="Translation status" />
- [x] Swahili: <img src="https://hosted.weblate.org/widgets/tor/sw/onionsprouts-bot/svg-badge.svg" alt="Translation status" />
- [x] Tor Browser: at the end because we are still migrating to weblate from transifex.
_Farsi translations will be done by Localization Lab, paid by Tor._
_Chinese, Arabic and Swahili will be done by Localization Lab, paid by IRI._Sponsor 134: Localizing Tor tools and documentation into Arabic, Chinese, and Swahiliemmapeelemmapeelhttps://gitlab.torproject.org/tpo/core/onionmasq/-/issues/54Bridges: PT support2023-10-20T14:25:58ZetaBridges: PT supportWe should be able to support bridges launched through pluggable transports (related to #21). This will require figuring out a way to embed some of the pluggable transports inside the onionmasq library, since I don't think we'll be able t...We should be able to support bridges launched through pluggable transports (related to #21). This will require figuring out a way to embed some of the pluggable transports inside the onionmasq library, since I don't think we'll be able to exec() them on the Android platform.VPN pre-alpha 03etaetahttps://gitlab.torproject.org/tpo/core/tor/-/issues/40841conflux_validate_legs(): Bug: Number of legs is above maximum of 2 allowed: 3...2023-08-30T18:21:26ZMike Perryconflux_validate_legs(): Bug: Number of legs is above maximum of 2 allowed: 3#012 (on Tor 0.4.8.3-rc-dev )A cypherpunks user reported some logspam due to this BUG check as a random comment in https://gitlab.torproject.org/tpo/core/tor/-/issues/40834#note_2935264. Initially, this looks like a rogue Tor client hitting this check. This has neve...A cypherpunks user reported some logspam due to this BUG check as a random comment in https://gitlab.torproject.org/tpo/core/tor/-/issues/40834#note_2935264. Initially, this looks like a rogue Tor client hitting this check. This has never happened in a Shadow run.
This is harmless, but noisy. It is also at warn and not protocol warn.
We could remove the BUG() and demote to ProtocolWarn, but should have a look through the client codepaths for cases that could somehow spawn 3 legs instead of 2, just in case.Tor: 0.4.8.x-stableMike PerryMike Perryhttps://gitlab.torproject.org/tpo/core/tor/-/issues/40811conflux_launch_leg infinite loop2023-07-05T21:32:13ZRoger Dingledineconflux_launch_leg infinite loopI finally got a proper core from the seg fault that my tor has been hitting periodically.
The seg fault seems to happen because my stack has thousands of entries on it, presumably because we are calling functions that call themselves in...I finally got a proper core from the seg fault that my tor has been hitting periodically.
The seg fault seems to happen because my stack has thousands of entries on it, presumably because we are calling functions that call themselves in a circle and it keeps stacking deeper.
It happens in practice when my Tor is minding its own business (not actively being used) but then my wifi goes away.
Here is a sample of the 'where' output from gdb
```
#69 0x000055a2356ef88a in circuit_establish_circuit_conflux (
conflux_nonce=conflux_nonce@entry=0x7ffc342cc320 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,M\320\323\325<\242U",
purpose=purpose@entry=25 '\031', exit_ei=exit_ei@entry=0x55a236878cd0,
flags=flags@entry=70) at src/core/or/circuitbuild.c:547
#70 0x000055a23571aae7 in conflux_launch_leg (
nonce=nonce@entry=0x7ffc342cc320 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,M\320\323\325<\242U")
at src/core/or/conflux_pool.c:1110
#71 0x000055a23571bcb7 in unlinked_circuit_closed (circ=0x55a23cd5d3d0)
at src/core/or/conflux_pool.c:1426
#72 conflux_circuit_has_closed (circ=circ@entry=0x55a23cd5d3d0)
at src/core/or/conflux_pool.c:1632
#73 0x000055a2356f6875 in circuit_mark_for_close_ (circ=0x55a23cd5d3d0,
reason=0, line=line@entry=547,
file=file@entry=0x55a23582f102 "src/core/or/circuitbuild.c")
at src/core/or/circuitlist.c:2262
#74 0x000055a2356ef88a in circuit_establish_circuit_conflux (
conflux_nonce=conflux_nonce@entry=0x7ffc342cc450 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,MP\305\325<\242U",
purpose=purpose@entry=25 '\031', exit_ei=exit_ei@entry=0x55a236878cd0,
flags=flags@entry=70) at src/core/or/circuitbuild.c:547
#75 0x000055a23571aae7 in conflux_launch_leg (
nonce=nonce@entry=0x7ffc342cc450 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,MP\305\325<\242U")
at src/core/or/conflux_pool.c:1110
#76 0x000055a23571bcb7 in unlinked_circuit_closed (circ=0x55a23cd5c550)
at src/core/or/conflux_pool.c:1426
#77 conflux_circuit_has_closed (circ=circ@entry=0x55a23cd5c550)
at src/core/or/conflux_pool.c:1632
#78 0x000055a2356f6875 in circuit_mark_for_close_ (circ=0x55a23cd5c550,
reason=0, line=line@entry=547,
file=file@entry=0x55a23582f102 "src/core/or/circuitbuild.c")
at src/core/or/circuitlist.c:2262
#79 0x000055a2356ef88a in circuit_establish_circuit_conflux (
conflux_nonce=conflux_nonce@entry=0x7ffc342cc580 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,Mж\325<\242U",
purpose=purpose@entry=25 '\031', exit_ei=exit_ei@entry=0x55a236878cd0,
flags=flags@entry=70) at src/core/or/circuitbuild.c:547
#80 0x000055a23571aae7 in conflux_launch_leg (
nonce=nonce@entry=0x7ffc342cc580 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,Mж\325<\242U")
at src/core/or/conflux_pool.c:1110
#81 0x000055a23571bcb7 in unlinked_circuit_closed (circ=0x55a23cd5b6d0)
at src/core/or/conflux_pool.c:1426
#82 conflux_circuit_has_closed (circ=circ@entry=0x55a23cd5b6d0)
at src/core/or/conflux_pool.c:1632
#83 0x000055a2356f6875 in circuit_mark_for_close_ (circ=0x55a23cd5b6d0,
reason=0, line=line@entry=547,
file=file@entry=0x55a23582f102 "src/core/or/circuitbuild.c")
at src/core/or/circuitlist.c:2262
#84 0x000055a2356ef88a in circuit_establish_circuit_conflux (
conflux_nonce=conflux_nonce@entry=0x7ffc342cc6b0 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,MP\250\325<\242U",
purpose=purpose@entry=25 '\031', exit_ei=exit_ei@entry=0x55a236878cd0,
flags=flags@entry=70) at src/core/or/circuitbuild.c:547
```
I still have the core, but my internet for the next days is pretty crappy so I will try to respond as I can. :)
This is Tor running from git commit d5306e107f. I can't easily trigger it, or I would try a git bisect. It's been happening since before the Tor 0.4.8.1-alpha release. I am just a client.Tor: 0.4.8.x-stableMike PerryMike Perry