The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2024-02-05T21:22:54Zhttps://gitlab.torproject.org/tpo/web/community/-/issues/295Change for Vultr's stance on Tor for Good Bad ISPs page2024-02-05T21:22:54ZGhost UserChange for Vultr's stance on Tor for Good Bad ISPs page```
Company/ISP: Vultr (https://vultr.com)
ASN: -
Bridges: No
Relay: No
Exit No
Comments: "TOR exit nodes are listed, merely as an example, as part of our Sample list of Prohibited Activities. We do not support any TOR related activity o...```
Company/ISP: Vultr (https://vultr.com)
ASN: -
Bridges: No
Relay: No
Exit No
Comments: "TOR exit nodes are listed, merely as an example, as part of our Sample list of Prohibited Activities. We do not support any TOR related activity on our network, including but not limited to TOR exit relays."
Last update: 20/09/2022 (D/M/Y)
```
After contacting Vultr support, they told me that they do not permit any Tor-related activity on their network. Even if someone manages to run nodes with them without getting in trouble for now, I feel it should still be updated to let others know about their stance and the potential risk of account termination.
![supportimage](/uploads/3ead185df4d77958c05fe54795e244d3/Untitled.jpg)GusGushttps://gitlab.torproject.org/tpo/web/community/-/issues/325Which fingerprint?2024-02-05T20:09:19ZharpiaWhich fingerprint?<!--
* Use this issue template for suggesting new docs or updates to existing docs.
-->
### Problem to solve
<!-- Include the following detail as necessary:
-->
I think this paragraph needs clarification:
> You'll need to replace `<I...<!--
* Use this issue template for suggesting new docs or updates to existing docs.
-->
### Problem to solve
<!-- Include the following detail as necessary:
-->
I think this paragraph needs clarification:
> You'll need to replace `<IP ADDRESS>`, `<PORT>`, and `<FINGERPRINT>` with the actual values, which you can find in the tor log. Make sure to use `<FINGERPRINT>`, not `<HASHED FINGERPRINT>`; and that `<PORT>` is the obfs4 port you chose - and not the OR port.
The Tor logs list 3 different fingerprints.
```
Your Tor server's identity key fingerprint <fingerprint>
Your Tor bridge's hashed identity key fingerprint <fingerprint>
Your Tor server's identity key ed25519 fingerprint <fingerprint>
```
### Further details
- Link to the page: https://gitlab.torproject.org/tpo/web/community/-/blob/main/content/relay/setup/bridge/post-install/contents.lr
### Proposal
<!-- Further specifics for how can we solve the problem. -->
Correct me if I'm wrong - I think the correct fingerprint is the first one, "your Tor server identity key". This is how I would rewrite it:
> Make sure to use your Tor server's identity key fingerprint, not the hashed bridge key or the ed25519 key;GusGushttps://gitlab.torproject.org/tpo/web/community/-/issues/340(relay) Broken link on technical considerations page2024-02-05T19:32:52ZGus(relay) Broken link on technical considerations pageReported on the Tor Forum: https://forum.torproject.org/t/broken-link-on-technical-considerations-page/11180
New link: https://asrank.caida.org/Reported on the Tor Forum: https://forum.torproject.org/t/broken-link-on-technical-considerations-page/11180
New link: https://asrank.caida.org/GusGushttps://gitlab.torproject.org/tpo/web/community/-/issues/335(Snowflake guide) Add Snowflake debian package2024-02-05T19:12:52ZGus(Snowflake guide) Add Snowflake debian packageSnowflake-proxy is available as a package in Debian bookworm. We should mention at https://community.torproject.org/relay/setup/snowflake/standalone/Snowflake-proxy is available as a package in Debian bookworm. We should mention at https://community.torproject.org/relay/setup/snowflake/standalone/Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & TibetGusGushttps://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/34Minor documentation fixes2024-02-05T16:40:54ZSilvio RhattoMinor documentation fixes# Tasks
* [x] Do some minor documentation fixes.
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)# Tasks
* [x] Do some minor documentation fixes.
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31https://gitlab.torproject.org/tpo/core/arti/-/issues/1222Add central documentation for our filesystem layout2024-02-01T15:43:34ZNick MathewsonAdd central documentation for our filesystem layoutSomewhere in doc/dev, we should document all the files that we create or look at.
This will include:
* `tor-keymgr` stuff, possibly by reference
* All state files
* All onion-service-related files
* All cache files
* All locks...Somewhere in doc/dev, we should document all the files that we create or look at.
This will include:
* `tor-keymgr` stuff, possibly by reference
* All state files
* All onion-service-related files
* All cache files
* All locks
* All configuration files
This should replace `crates/tor-hsservice/src/state_dir.md` (cc @diziet)https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/39Update mining documentation2024-01-31T18:27:20ZSilvio RhattoUpdate mining documentation# Tasks
* [x] Cleanup the [Tips when mining Onion Addresses][] page.
* [x] Update the [Tips when mining Onion Addresses][] page, including references to
* [x] [Onionmine](https://gitlab.torproject.org/tpo/onion-services/onionmine/).
...# Tasks
* [x] Cleanup the [Tips when mining Onion Addresses][] page.
* [x] Update the [Tips when mining Onion Addresses][] page, including references to
* [x] [Onionmine](https://gitlab.torproject.org/tpo/onion-services/onionmine/).
* [x] The [Vanity Addresses page](https://community.torproject.org/onion-services/advanced/vanity-addresses/).
[Tips when mining Onion Addresses]: https://tpo.pages.torproject.net/onion-services/onionspray/guides/mining/
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31https://gitlab.torproject.org/tpo/web/manual/-/issues/99Update known issues page - Tor Browser desktop and mobile2024-01-30T13:40:21ZGusUpdate known issues page - Tor Browser desktop and mobileAccording to the [blog post](https://blog.torproject.org/new-release-tor-browser-105), here's a list of known issues that we need to update the Tor Browser Manual:
### Desktop
- tpo/applications/tor-browser#40497
- tpo/applications/tor...According to the [blog post](https://blog.torproject.org/new-release-tor-browser-105), here's a list of known issues that we need to update the Tor Browser Manual:
### Desktop
- tpo/applications/tor-browser#40497
- tpo/applications/tor-browser#40242
- tpo/applications/tor-browser#40506
- tpo/applications/tor-browser#40510
https://tb-manual.torproject.org/known-issues/
### Mobile
- tpo/applications/fenix#40176
- tpo/applications/fenix#40110
- tpo/applications/fenix#40172
- tpo/applications/fenix#40174
- tpo/applications/fenix#40103
- tpo/applications/fenix#40115
- tpo/applications/fenix#40324
https://tb-manual.torproject.org/mobile-tor/ebanamebanam@torproject.orgebanamebanam@torproject.orghttps://gitlab.torproject.org/tpo/onion-services/onionbalance/-/issues/25Onionbalance Security Analysis2024-01-30T12:28:21ZSilvio RhattoOnionbalance Security AnalysisWrite a quick threat model / security analysis for Onionbalance, stating what it brings (or does not bring) in terms of security.
One good aspect to highlight is that it can offer a practical solution to reduce the attack surface in the...Write a quick threat model / security analysis for Onionbalance, stating what it brings (or does not bring) in terms of security.
One good aspect to highlight is that it can offer a practical solution to reduce the attack surface in the long-term .onion identity key, since only the frontend/publish nodes need to have access to it. So Onionbalance is not just about load balancing, but also separation of concerns/isolation. And until offline keys is supported, that's the best and easier approach to reduce the attack surface on these keys.
The [Vanguards' security analysis][] may be a good source of inspiration for such document, in terms of structure and content.
[Vanguards' security analysis]: https://github.com/mikeperry-tor/vanguards/blob/master/README_SECURITY.mdOnionbalance 0.2.3https://gitlab.torproject.org/tpo/web/manual/-/issues/130Manual on Bridges speaks of "addresses" but means whole bridge lines2024-01-29T19:32:45ZIan Jacksoniwj@torproject.orgManual on Bridges speaks of "addresses" but means whole bridge linesThe page https://tb-manual.torproject.org/bridges/ speaks of "Bridge addresses" but it means the whole bridge line, including not just the address and port but also PT name, identity key, and PT parameters. I think this is unnecessarily...The page https://tb-manual.torproject.org/bridges/ speaks of "Bridge addresses" but it means the whole bridge line, including not just the address and port but also PT name, identity key, and PT parameters. I think this is unnecessarily confusing.
It might even be leading to users fishing the thing out of the bridge line that looks like an address...
Since internally (and presumably in the community) we speak of "bridge lines", maybe that should be the official terminology? Or we could invent a new term ("bridge spec") maybe, but changing existing usage is slow of course.
We should be clear internally about precisely what the terms mean, and use them consistently (for example, the "bridge line" does not seem to include the `Bridge` that appears as the keyword in torrc).https://gitlab.torproject.org/tpo/ux/team/-/issues/89Project idea: Write a user research handbook2024-01-29T19:09:34ZdonutsProject idea: Write a user research handbookOnboarding partners who have little to no experience conducting user research simply isn't possible in a single session, and the existing material we have on the [community portal](https://community.torproject.org/user-research/guideline...Onboarding partners who have little to no experience conducting user research simply isn't possible in a single session, and the existing material we have on the [community portal](https://community.torproject.org/user-research/guidelines/) isn't sufficient either. Instead, I'd like to create a longer version of this content called the user research handbook, with graphic support provided by our designers, including topics like:
- Our methodology (i.e. the processes we follow)
- Research methods (i.e. the types of research we employ)
- Best practices (previously dubbed the privacy playbook)
- Assessing risk (i.e. our risk assessment procedure)
- Recruitment
- Reporting
This content may then be hosted on the future design-dot website (see [UX / milestone#17](https://gitlab.torproject.org/groups/tpo/ux/-/milestones/17)).Sponsor 9 - Phase 7 - Usability and Community Intervention on Support for Democracy and Human Rightshttps://gitlab.torproject.org/tpo/ux/design/-/issues/67Design page templates for design-dot2024-01-29T19:09:25ZdonutsDesign page templates for design-dotWorking file here: [Figma / Marble / Design-dot](https://www.figma.com/file/nIpahk0b9VMaeEnubiO33g/Marble?type=design&node-id=291%3A6468&mode=design&t=5VNXs9nes3se88ax-1)Working file here: [Figma / Marble / Design-dot](https://www.figma.com/file/nIpahk0b9VMaeEnubiO33g/Marble?type=design&node-id=291%3A6468&mode=design&t=5VNXs9nes3se88ax-1)design-dot MVPdonutsdonutshttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40126Improve Access Keys documentation: explain difference to shortcuts2024-01-24T21:11:50ZemmapeelImprove Access Keys documentation: explain difference to shortcutsWe already have some documentation about Access Keys: https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-translators#access-keys
But it needs to be improved.
We need to differentiate Access Keys, that are a way t...We already have some documentation about Access Keys: https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-translators#access-keys
But it needs to be improved.
We need to differentiate Access Keys, that are a way to navigate menus, from keyboard shortcuts.
One difference: Shortcuts are the same for all locales, Access Keys depend on the locale.
ref: https://hosted.weblate.org/translate/tor/tor-browser/tb-newidentityproperties/ru/?checksum=73b4988ed95a84d9#commentshttps://gitlab.torproject.org/tpo/community/onion-tex-slim/-/issues/2Document localization options2024-01-24T21:11:37ZSilvio RhattoDocument localization optionsSimilar to tpo/web/onion-mkdocs#5.Similar to tpo/web/onion-mkdocs#5.https://gitlab.torproject.org/tpo/community/l10n-for-markdown/-/issues/1Document how to integrate with the translation repository2024-01-24T21:11:33ZSilvio RhattoDocument how to integrate with the translation repositoryDocument how this project can be used in an integrated workflow with the [translations repository](https://gitlab.torproject.org/tpo/translation), in accordance with the [Localization for developers](https://gitlab.torproject.org/tpo/com...Document how this project can be used in an integrated workflow with the [translations repository](https://gitlab.torproject.org/tpo/translation), in accordance with the [Localization for developers](https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-developers) document.https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/19Fine tune the documentation2024-01-23T18:16:17ZSilvio RhattoFine tune the documentation# Tasks
* [x] Re-structure docs according to [Diatáxis](https://diataxis.fr/), or at least split some content between How-To Guides and Tutorials.
* [x] Do a more fine-grained edit in the docs, including:
* [x] [Survival Guide](https:...# Tasks
* [x] Re-structure docs according to [Diatáxis](https://diataxis.fr/), or at least split some content between How-To Guides and Tutorials.
* [x] Do a more fine-grained edit in the docs, including:
* [x] [Survival Guide](https://gitlab.torproject.org/tpo/onion-services/onion-support/-/wikis/Documentation/Survival-Guide) (EOTK portion).
* [x] Migration guide for those coming from EOTK, replacing the migration sketched in the ChangeLog (basically copying all `.conf`, `.tconf`, `secrets`; building and configuring; copying the certificates).
* [x] Improved introduction:
* [x] [Project description](https://gitlab.torproject.org/tpo/onion-services/eotk/-/issues/13#note_2986581).
* [x] What it does: adds Onion Service support for existing sites.
* [x] Overview how it works (rewriting proxy through .onion) (with a diagram). The proxy is mainly intended to replace regular domain names with their .onion counterparts, offering a seamless experience to users.
* [x] How it's usually installed: no need to changing existing setups, just provision the Onion Services infra in parallel of existing setups; can run anywhere, in a laptop, a single board computer, in servers; as standalone program, or as a container.
* [x] Use-cases.
* [x] On EOTK compatibility: the `eotk` script is kept as an alias to `onionspray`.
* [x] Replace `eotk` with `onionspray` in the CLI usage.
* [x] Installation:
* [x] Required knowledge (Onion Services and command line familiarity etc).
* [~] Using Tor and OpenResty upstream packages for your distro (when available) (moved to tpo/onion-services/onionspray#21).
* [x] Contact and reporting:
* [x] Contact info (tor-dev channel and mailing list?).
* [x] How to report bugs.
* [~] ChangeLog:
* [~] Update with everything (or just referring to) done in the [initial milestone](https://gitlab.torproject.org/tpo/onion-services/onionspray/-/milestones/1) (moved to tpo/onion-services/onionspray#28).
* [x] Setup the [Renovate Bot](https://gitlab.torproject.org/tpo/tpa/renovate-cron) to watch for changes in vendorized Git submodules.
* [x] Review the documentation.
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31https://gitlab.torproject.org/tpo/tpa/team/-/issues/41433Provide git commit notifications for dirauth-conf changes to #tor-internal2024-01-19T20:40:07ZGeorg KoppenProvide git commit notifications for dirauth-conf changes to #tor-internalAs our dirauth-conf repo is moving away from git.torproject.org to Gitlab we'd like to retain the option to send notifications for git commits pushed to our #tor-internal channel.As our dirauth-conf repo is moving away from git.torproject.org to Gitlab we'd like to retain the option to send notifications for git commits pushed to our #tor-internal channel.https://gitlab.torproject.org/tpo/core/arti/-/issues/1249Arti documentation next phase2024-01-18T18:02:26ZGabagaba@torproject.orgArti documentation next phaseDocumentWrite is almost done with the Arti documentation. We need to make a decision on
- how deployment will happen for arti.torproject.org. Are we move the documentation from DocumentWrite into this arti repository and deploy it to a...DocumentWrite is almost done with the Arti documentation. We need to make a decision on
- how deployment will happen for arti.torproject.org. Are we move the documentation from DocumentWrite into this arti repository and deploy it to arti.torproject.org through gitlab pages?
- deprecation of old documentation. Is there any check we can do to be sure that everything from the old documentation is in the new one?
On parallel we need "training" from DocumentWrite to understand their work and be sure that we can keep maintaining this documentation in the easiest way possible.
Thoughts?https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41064Update tools/signing/README and add a tools/signing/machines-setup/README2024-01-18T15:05:06ZboklmUpdate tools/signing/README and add a tools/signing/machines-setup/READMEWe should update `tools/signing/README` for latest changes, and also
point to the issue templates for usage information.
We should also create `tools/signing/machines-setup/README` to document
how the setup of the signing machines is done.We should update `tools/signing/README` for latest changes, and also
point to the issue templates for usage information.
We should also create `tools/signing/machines-setup/README` to document
how the setup of the signing machines is done.boklmboklmhttps://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/17Improve and cleanup the documentation2024-01-17T21:30:01ZSilvio RhattoImprove and cleanup the documentation# Tasks
* [x] Improve and cleanup the documentation.
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)# Tasks
* [x] Improve and cleanup the documentation.
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.6.0Silvio RhattoSilvio Rhatto2024-01-31