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/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/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/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-31https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/14Documentation cleanup2024-01-17T16:35:28ZSilvio RhattoDocumentation cleanup# Tasks
* [~] Cleanup the codebase, removing old/unused code (moved to tpo/onion-services/eotk#16).
* [x] Cleanup the documentation, removing deprecated items etc.
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: lo...# Tasks
* [~] Cleanup the codebase, removing old/unused code (moved to tpo/onion-services/eotk#16).
* [x] Cleanup the documentation, removing deprecated items etc.
# 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/onion-services/onionspray/-/issues/15Setup Onion MkDocs2024-01-17T16:35:02ZSilvio RhattoSetup Onion MkDocs# Tasks
* [x] Setup web documentation through [Onion MkDocs](https://gitlab.torproject.org/tpo/web/onion-mkdocs/).
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/...# Tasks
* [x] Setup web documentation through [Onion MkDocs](https://gitlab.torproject.org/tpo/web/onion-mkdocs/).
# 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/network-health/metrics/exit-scanner/-/issues/40001broken links in docs2024-01-16T15:47:58Zanarcatbroken links in docsit's great to have documentation on the exit scanner and check here:
https://gitlab.torproject.org/tpo/network-health/team/-/wikis/Exit-Scanner-Ops
... but there are a bunch of broken links in the page, for example:
https://gitlab.tor...it's great to have documentation on the exit scanner and check here:
https://gitlab.torproject.org/tpo/network-health/team/-/wikis/Exit-Scanner-Ops
... but there are a bunch of broken links in the page, for example:
https://gitlab.torproject.org/tpo/metrics/exit-scanner/-/wikis/check-ops/
https://gitlab.torproject.org/tpo/metrics/exit-scanner/-/wikis/tordnsel
it seems like only a part of the ikiwiki docs were imported here...
also, it would seem important to crossref those docs with https://gitlab.torproject.org/tpo/metrics/team/-/wikis/home
arguably, maybe *all* the metrics docs should be centralised there instead of having multiple wikis like this...https://gitlab.torproject.org/tpo/community/hackweek/-/issues/24Public documentation about project design and grant writing process2024-01-11T17:32:09Zal smithPublic documentation about project design and grant writing process# About the project
* Contact: @smith
* Chat: #tor-internal on `irc.oftc.net`
* Video room: tbd
# Participants
- @smith
- etc
# Summary
- Write a guide on the process of project design and grant proposal writing
- Publish that ...# About the project
* Contact: @smith
* Chat: #tor-internal on `irc.oftc.net`
* Video room: tbd
# Participants
- @smith
- etc
# Summary
- Write a guide on the process of project design and grant proposal writing
- Publish that guide
- Create a template spreadsheet with guidelines on how to do estimations (@gaba, any interest in helping?)
We created an [overview of the grants process in Costa Rica and presented it in an in-person session](https://gitlab.torproject.org/tpo/team/-/wikis/Meetings/2023/2023-Tor-Meeting-Costa-Rica-Wiki/overview-of-how-projects-get-funded). We can use this to create something that's easier to read, more well-resourced, and easier to find.
# Skills
- Familiarity with the project design and grant writing process, either from a team participant side (e.g., someone from the network team who has been involved grant writing before) or from the design and writing side (e.g., someone form the money machine team).
# LinksHackweek 2023al smithal smithhttps://gitlab.torproject.org/tpo/web/team/-/issues/44Archive and redirect gettor.torproject.org landing page to support portal2024-01-11T13:54:11ZGusArchive and redirect gettor.torproject.org landing page to support portalAlthough GetTor service is very important and useful for users where torproject.org website is blocked, I don't get what's the point of having GetTor landing page since all the instructions are available on Support portal and on Tor Brow...Although GetTor service is very important and useful for users where torproject.org website is blocked, I don't get what's the point of having GetTor landing page since all the instructions are available on Support portal and on Tor Browser Manual, which is bundled in TB.
So, here is my proposal to archive and redirect gettor.torproject.org:
- Improve gettor entry on https://support.torproject.org/censorship
- Archive the repository: https://gitlab.torproject.org/tpo/web/gettor-web
- Redirect gettor.torproject.org to support.torproject.org/censorship
- Remove gettor-web from weblateSponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibetemmapeelemmapeelhttps://gitlab.torproject.org/tpo/web/support/-/issues/212Add a short FAQ to snowflake.tp.o2024-01-10T23:43:36ZArlo BreaultAdd a short FAQ to snowflake.tp.oThis should include explanations for the missing feature error messages. See comment:13:ticket:31391This should include explanations for the missing feature error messages. See comment:13:ticket:31391https://gitlab.torproject.org/tpo/web/community/-/issues/208Do onion services connect through two or three hops to an introduction service?2024-01-09T15:23:33ZHackerNCoderhackerncoder@encryptionin.spaceDo onion services connect through two or three hops to an introduction service?https://community.torproject.org/onion-services/overview/ - Act 1 cannot agree with itself on whether an onion service connects through a two or three-hop Tor circuit to an introduction point. Text says "through a two-hop Tor circuit", b...https://community.torproject.org/onion-services/overview/ - Act 1 cannot agree with itself on whether an onion service connects through a two or three-hop Tor circuit to an introduction point. Text says "through a two-hop Tor circuit", but image says "through a three-hop Tor circuit". We should clarify which one it is.Silvio RhattoSilvio Rhattohttps://gitlab.torproject.org/tpo/ux/team/-/issues/93Project idea: Design and build a replacement for styleguide-dot2023-12-13T05:10:58ZdonutsProject idea: Design and build a replacement for styleguide-dotAt the Tor Project hackweek in November 2023, the UX Team explored a replacement for our existing style guide ([styleguide.torproject.org](https://styleguide.torproject.org/)), with the stated goal:
> The UX Team have been discussing re...At the Tor Project hackweek in November 2023, the UX Team explored a replacement for our existing style guide ([styleguide.torproject.org](https://styleguide.torproject.org/)), with the stated goal:
> The UX Team have been discussing replacing the [existing styleguide](http://styleguide.torproject.org) with a new resource that's wider in scope – e.g. "design.torproject.org". In addition to updating our brand and web guidelines given their evolution over the past few years, we're also considering adding new sections to document our human-centered design principals, user research program, and overall methodology. The revised portal should serve as a central point of reference for external resources too, including for example our Figma libraries for the browser, web and VPN, and any open source design resources we use.
During the hackweek, we made good progress planning the structure of the future site and designed some initial templates. However it also became clear that the scope we were aiming for was simply too large, and that it would be better to focus on deploying a basic MVP that covers the same subjects as the current style guide—those being:
- Home page
- Styles
- Color: featuring the new 10 point color system, core brand colors, and semantic uses.
- Typography: including updates to our brand fonts at display and body sizes.
- Assets
- Brand: featuring the new logo, if approved (see https://gitlab.torproject.org/tpo/ux/team/-/issues/92), the new Tor Browser application icons, and guidelines for use.
- Iconography: including custom icons for Tor Browser and our new brand icons (see https://gitlab.torproject.org/tpo/ux/design/-/issues/62).
- Illustration: featuring the new illustrations being developed by Nico (see https://gitlab.torproject.org/tpo/ux/design/-/issues/61).https://gitlab.torproject.org/tpo/network-health/team/-/issues/201Create bandwidth authority specification2023-12-11T09:56:45ZGeorg KoppenCreate bandwidth authority specificationWe have:
* https://research.torproject.org/techreports/torflow-2009-08-07.pdf
* https://gitlab.torproject.org/tpo/network-health/torflow/-/blob/main/NetworkScanners/BwAuthority/README.spec.txt
* https://gitlab.torproject.org/tpo/network...We have:
* https://research.torproject.org/techreports/torflow-2009-08-07.pdf
* https://gitlab.torproject.org/tpo/network-health/torflow/-/blob/main/NetworkScanners/BwAuthority/README.spec.txt
* https://gitlab.torproject.org/tpo/network-health/torflow/-/blob/main/NetworkScanners/BwAuthority/README.BwAuthorities
* https://gitlab.torproject.org/tpo/network-health/torflow/-/blob/main/README
* https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/bandwidth-file-spec.txt
We should create a single "bandwidth authority spec" including data from those documents and the current implementations.jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/134Add documentation on how to build documentation, run tests and add example co...2023-12-11T09:55:56ZjugaAdd documentation on how to build documentation, run tests and add example configurationsjugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/107Move all or part of the documentation about Tor and the bandwidth scanner2023-12-11T09:51:28ZjugaMove all or part of the documentation about Tor and the bandwidth scannerI've writing documentation in https://onbasca.readthedocs.io/ that i didn't know where else could go.
Some of it might be useful only for me but some might be useful for other people and should be in Tor project domain.I've writing documentation in https://onbasca.readthedocs.io/ that i didn't know where else could go.
Some of it might be useful only for me but some might be useful for other people and should be in Tor project domain.jugajuga