The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-11-06T12:55:36Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/29215Document target, modular tor architecture2021-11-06T12:55:36ZNick MathewsonDocument target, modular tor architectureWe'll be working during sponsor31 to make sure that we are moving towards a nice modular architecture. We should document what we're actually trying to achieve, and what our target architecture is, so that we can tell people "do it like ...We'll be working during sponsor31 to make sure that we are moving towards a nice modular architecture. We should document what we're actually trying to achieve, and what our target architecture is, so that we can tell people "do it like X, not necessarily like Tor does it now."
The official deliverable here is "Architectural documentation for how Tor modules work with one another, covering both the actuality and the refactored architecture". The "actuality" is under legacy/trac#29214.Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/web/support/-/issues/250Add to Support portal the new forum link and other references2021-10-27T16:10:43ZGabagaba@torproject.orgAdd to Support portal the new forum link and other referencesUpdate portals with links to the new forum.Update portals with links to the new forum.Launch support's Forum and Blog migrationGusGus2021-10-30https://gitlab.torproject.org/tpo/web/community/-/issues/213Come up with a better terminology for bridges2021-10-27T13:31:53ZPhilipp Winterphw@torproject.orgCome up with a better terminology for bridgesOur terminology for bridges is confusing:
* *Private* bridges are bridges that BridgeDB doesn't know about. Users may mistakenly conclude that if a bridge isn't private, it must be public, which is incorrect. Suggestions for other terms:...Our terminology for bridges is confusing:
* *Private* bridges are bridges that BridgeDB doesn't know about. Users may mistakenly conclude that if a bridge isn't private, it must be public, which is incorrect. Suggestions for other terms: unshared, exclusive, unlisted, unknown.
* *Default* bridges are part of Tor Browser. Conceptually, default bridges are more like obfs4-enabled guard relays. Suggestions for other terms: built-in (we may have been using that term occasionally), standard, public.
* We don't have a consistent term for bridges that are distributed by BridgeDB/rdsys. Perhaps we don't need a term because that's the default?
How can we improve the situation?
Copying @cohosh, @antonela, @arma, and @gus.
# Update
proposal is to change this terminology **everywhere**
- default bridges -> built-in bridges
- will not do private/public bridges anymore
- private bridges -> secret bridges
- public bridges -> distributed bridges
Everywhere means:
- [ ] documentation - needs tickets in each portal
- [ ] [Browser's UI](tpo/applications/tor-browser#40623)
- [ ] Code - needs ticketSponsor 30 - Objective 2.2GusGushttps://gitlab.torproject.org/tpo/core/arti/-/issues/130Naming issue on `tor-client` crate2021-10-21T18:23:16ZNick MathewsonNaming issue on `tor-client` crateThere is already a crate called `tor_client`, which apparently conflicts with `tor-client`. Whoops! For 0.0.0, I've renamed `tor-client` to `arti-tor-client`.
Before 0.0.1, we should either update the documentation to always refer to ...There is already a crate called `tor_client`, which apparently conflicts with `tor-client`. Whoops! For 0.0.0, I've renamed `tor-client` to `arti-tor-client`.
Before 0.0.1, we should either update the documentation to always refer to arti-tor-client, or we should rename the crate to something else.Arti 0.0.1 release: basic anonymityNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/56Packages wiki page getting discontinued2021-10-21T15:17:20ZGabagaba@torproject.orgPackages wiki page getting discontinuedAtagar is not going to keep maintaining https://trac.torproject.org/projects/tor/wiki/doc/packages
I'm opening this ticket to make a decision if it needs to be moved into gitlab and continue to exist.
https://gitweb.torproject.org/doct...Atagar is not going to keep maintaining https://trac.torproject.org/projects/tor/wiki/doc/packages
I'm opening this ticket to make a decision if it needs to be moved into gitlab and continue to exist.
https://gitweb.torproject.org/doctor.git/tree/package_versions.py would have to get adapted to gitlab.https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/21publish the migration source code2021-10-21T15:14:10Zanarcatpublish the migration source codeit would be great to have the migration source code public, if that is safe at all.
it would serve a few purposes:
1. it would allow us to diagnose problems better if they come up
2. it would give good examples on how to talk to the ...it would be great to have the migration source code public, if that is safe at all.
it would serve a few purposes:
1. it would allow us to diagnose problems better if they come up
2. it would give good examples on how to talk to the API
3. it would show others how we did it
Of course the code would need to be sanitized for secrets, but it doesn't have to be clean.Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/73Add missing link to firewalled-clients FAQ in behind-nat question2021-10-21T13:27:32ZemmapeelAdd missing link to firewalled-clients FAQ in behind-nat questionin https://support.torproject.org/operators/behind-nat/ we suggest to read the 'firewalled-clients FAQ' but we don't provide any way to find that FAQ.
We should find out where it is, and link it on the text:
> If your relay is running ...in https://support.torproject.org/operators/behind-nat/ we suggest to read the 'firewalled-clients FAQ' but we don't provide any way to find that FAQ.
We should find out where it is, and link it on the text:
> If your relay is running on a internal net you need to setup port forwarding. Forwarding TCP connections is system dependent but the firewalled-clients FAQ entry offers some examples on how to do this.https://gitlab.torproject.org/tpo/web/community/-/issues/233[Onion Services] Update NYT onion service2021-10-20T13:23:15Zchampionquizzerchampionquizzer@torproject.org[Onion Services] Update NYT onion serviceNew York Times have updated their onion service to v3: https://www.nytimesn7cgmftshazwhfgzm37qxb44r64ytbb2dj3x62d2lljsciiyd.onion/
.. and we must update it on the 'featured onions' section: https://community.torproject.org/onion-servic...New York Times have updated their onion service to v3: https://www.nytimesn7cgmftshazwhfgzm37qxb44r64ytbb2dj3x62d2lljsciiyd.onion/
.. and we must update it on the 'featured onions' section: https://community.torproject.org/onion-services/#featured-onions
Proof: TLS/SSL certificate and onion-location header on https://www.nytimes.com/HackerNCoderhackerncoder@encryptionin.spaceHackerNCoderhackerncoder@encryptionin.spacehttps://gitlab.torproject.org/tpo/web/tpo/-/issues/239[Press] 'Ask us on #tor' should redirect to irc instructions on Support portal2021-10-20T13:22:24Zchampionquizzerchampionquizzer@torproject.org[Press] 'Ask us on #tor' should redirect to irc instructions on Support portal(Thanks to @emmapeel for pointing this out!)
On https://www.torproject.org/press/, 'Ask us on #tor' should ideally redirect to https://support.torproject.org/get-in-touch/irc-help/. Pointing directly to the [OFTC Webchat](https://webch...(Thanks to @emmapeel for pointing this out!)
On https://www.torproject.org/press/, 'Ask us on #tor' should ideally redirect to https://support.torproject.org/get-in-touch/irc-help/. Pointing directly to the [OFTC Webchat](https://webchat.oftc.net/) isn't a good idea I believe since it blocks Tor traffic by default.GusGushttps://gitlab.torproject.org/tpo/web/lego/-/issues/31Code style does not show on certain paragraphs2021-10-15T08:12:43ZemmapeelCode style does not show on certain paragraphsOn the Support portal, the code snippets done with \`\`\` do not show as nice as the bits embedded in text with only one \`.
See for example in https://support.torproject.org/apt/apt-over-tor/
![code-styling-not-working](/uploads/3dd6c...On the Support portal, the code snippets done with \`\`\` do not show as nice as the bits embedded in text with only one \`.
See for example in https://support.torproject.org/apt/apt-over-tor/
![code-styling-not-working](/uploads/3dd6c436c32f810bd65689e06b3e56d8/code-styling-not-working.png)
We could change the parts that do not work, but it would be better if we can make it work in both cases.https://gitlab.torproject.org/tpo/web/team/-/issues/11update documentation for local lektor build2021-10-14T13:48:02Zemmapeelupdate documentation for local lektor buildWe need to make some changes our documentation for lektor, as explained by
Derek Cameron in https://lists.torproject.org/pipermail/tor-community-team/2021-August/000414.htmlWe need to make some changes our documentation for lektor, as explained by
Derek Cameron in https://lists.torproject.org/pipermail/tor-community-team/2021-August/000414.htmlemmapeelemmapeelhttps://gitlab.torproject.org/tpo/web/research/-/issues/40004Update research-web docs to point to gitlab not git2021-10-13T19:00:29ZRoger DingledineUpdate research-web docs to point to gitlab not gitWe're migrating away from jenkins, and using that chance to migrate the research-web git repo from git.tpo to gitlab.tpo as well.
When the dust settles, we should go through whatever meager documentation there is (I see a README file fo...We're migrating away from jenkins, and using that chance to migrate the research-web git repo from git.tpo to gitlab.tpo as well.
When the dust settles, we should go through whatever meager documentation there is (I see a README file for example) and make sure it points to the right git repos, and also make sure it accurately describes the auto build process for the website.
Anybody who is reading this ticket who wants to do these steps, please do. :)https://gitlab.torproject.org/tpo/web/tpo/-/issues/242Update "How do I volunteer with Tor Project?"2021-10-12T20:15:09ZGusUpdate "How do I volunteer with Tor Project?"Let's update this entry URL to `/misc/volunteer-with-tor`
And add this content:
```
A few things everyone can do now:
1. Please consider [running a relay](https://community.torproject.org/relay/) to help the Tor network grow.
1. Tell ...Let's update this entry URL to `/misc/volunteer-with-tor`
And add this content:
```
A few things everyone can do now:
1. Please consider [running a relay](https://community.torproject.org/relay/) to help the Tor network grow.
1. Tell your friends! Get them to run relays. Get them to run [onion services](https://community.torproject.org/onion-services/). Get them to tell their friends.
1. If you like Tor's goals, please take a moment to [donate](https://donate.torproject.org) to support further Tor development. We're also looking for more sponsors - if you know any companies, NGOs, agencies, or other organizations that want anonymity / privacy / communications security, let them know about us.
1. We're looking for more [good examples of Tor users](https://community.torproject.org/user-research/persona/) and Tor use cases. If you use Tor for a scenario or purpose not yet described on that page, and you're comfortable sharing it with us, we'd love to hear from you.
### Documentation
1. Help [localize](https://community.torproject.org/localization/) the documentation into other languages. See [becoming a Tor translator](https://community.torproject.org/localization/becoming-tor-translator/) if you want to help out. We especially need Arabic or Farsi translations, for the many Tor users in censored areas.
### Advocacy
1. The tor community uses [public mailing lists](https://lists.torproject.org/cgi-bin/mailman/listinfo) and IRC channels ([join via Tor](https://www.oftc.net/Tor/)), like [tor-talk](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk) ([#tor on irc.oftc.net](irc://irc.oftc.net/tor)), [tor-relays](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays) ([#tor-relays](irc://irc.oftc.net/tor-relays)), [tor-dev](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev) ([#tor-dev](irc://irc.oftc.net/tor-dev)), or [tbb-dev](https://lists.torproject.org/cgi-bin/mailman/listinfo/tbb-dev), and summarize noteworthy changes into articles for our blog and [newsletter](https://newsletter.torproject.org/).
1. Create a presentation that can be used for various user [group meetings](https://community.torproject.org/outreach/) around the world.
1. Create a video about the positive uses of Tor, what Tor is, or how to use it. Some have already started on [Tor's Media server](https://media.torproject.org/video/), [Howcast](http://www.howcast.com/videos/90601-How-To-Circumvent-an-Internet-Proxy/), and [YouTube](https://www.youtube.com/user/TheTorProject).
1. Create a poster around a theme, such as "Tor for Freedom!"
1. Create a t-shirt design that incorporates ["Congratulations! You are using Tor!"](https://check.torproject.org/) in any language.
1. Spread the word about Tor at a symposium or conference and use these [Tor brochures](https://community.torproject.org/outreach/kit/) as conversation starter.
```
https://support.torproject.org/misc/misc-14/https://gitlab.torproject.org/tpo/web/support/-/issues/266Changing options order Snowflake > Private obfs4 bridges > meek-azure2021-10-12T19:14:39ZGusChanging options order Snowflake > Private obfs4 bridges > meek-azure13:20 < meskio> ggus: I was looking at https://support.torproject.org/censorship/connecting-from-china/
13:20 < meskio> planning to remove meek, shouldn't snowflake be the first option?
13:21 < meskio> or are we worried is new and we tru...13:20 < meskio> ggus: I was looking at https://support.torproject.org/censorship/connecting-from-china/
13:20 < meskio> planning to remove meek, shouldn't snowflake be the first option?
13:21 < meskio> or are we worried is new and we trust more meekGusGushttps://gitlab.torproject.org/tpo/community/support/-/issues/40001Review and suggest improvements on communitydocs.accessnow.org2021-10-07T22:30:14ZGusReview and suggest improvements on communitydocs.accessnow.orgNow that Access Now published their support templates, we should review and suggest changes (if any) about Tor.
https://communitydocs.accessnow.org/
This issue is being tracked in Access Now Helpline's Gitlab: https://gitlab.com/Access...Now that Access Now published their support templates, we should review and suggest changes (if any) about Tor.
https://communitydocs.accessnow.org/
This issue is being tracked in Access Now Helpline's Gitlab: https://gitlab.com/AccessNowHelpline/community-documentation/-/issues/2GusGushttps://gitlab.torproject.org/tpo/web/team/-/issues/8Remove Documentation -> 2019.www.torproject.org from the menu2021-10-07T13:35:42ZGusRemove Documentation -> 2019.www.torproject.org from the menuWe have too many users visiting the old Tor docs and getting lost or using old instructions. That is because of search engines, but also because we say "Documentation," but most of the docs there live in the Support portal and Community ...We have too many users visiting the old Tor docs and getting lost or using old instructions. That is because of search engines, but also because we say "Documentation," but most of the docs there live in the Support portal and Community portal.
As the main team plan was to replace it with a new developer portal (See: tpo/web/dev), I would like to track the minimal work we need to do to remove that website from the header once for all.
### Tasks
* [ ] Finish old FAQ migration to support portal: https://gitlab.torproject.org/tpo/web/support/-/issues/43
* [ ] Find a new home for little-t-tor manual [stable](https://2019.www.torproject.org/docs/tor-manual.html.en) and [alpha](https://2019.www.torproject.org/docs/tor-manual-dev.html.en). see also: https://gitlab.torproject.org/tpo/core/tor/-/issues/40418
* [ ] Find a temporary place to move this document Tor Browser Design document - https://2019.www.torproject.org/projects/torbrowser/design/https://gitlab.torproject.org/tpo/web/support/-/issues/246Improve and update HTTP or SOCKS Proxy documentation2021-10-07T12:57:16ZemmapeelImprove and update HTTP or SOCKS Proxy documentationIn https://support.torproject.org/tbb/tbb-47/ we are giving too much information, and we are not providing simple instructions for users. We should:
- [x] Remove mentions of HTTPAuthenticator that is deprecated in favor of the HTTPS fla...In https://support.torproject.org/tbb/tbb-47/ we are giving too much information, and we are not providing simple instructions for users. We should:
- [x] Remove mentions of HTTPAuthenticator that is deprecated in favor of the HTTPS flavor
- [ ] Add a code snippet as an example on how to connect to a proxy with authentication
- [x] Maybe link to https://2019.www.torproject.org/docs/tor-manual.html.en#HTTPSProxyAuthenticator
- [ ] Make everything simpler to understandhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25284hidden-service-dir description in dir-spec should reference HSDir protovers2021-09-30T13:50:08Zteorhidden-service-dir description in dir-spec should reference HSDir protoversSince 0.3.0, tor supports HSDir versions 2 and 3 by default, and advertises no hidden-service-dir VersionNums.
But the spec says:
"If any VersionNum(s) are specified, this router supports those descriptor versions. If none are specified...Since 0.3.0, tor supports HSDir versions 2 and 3 by default, and advertises no hidden-service-dir VersionNums.
But the spec says:
"If any VersionNum(s) are specified, this router supports those descriptor versions. If none are specified, it defaults to version 2 descriptors"Tor: 0.3.4.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25277Summarise the format of v3 hidden service addresses in the Tor man page2021-09-30T13:50:08ZTracSummarise the format of v3 hidden service addresses in the Tor man pageWe have regexes for ~~v1~~ v3:
```
^[a-z2-7]{56}\.onion$
```
where the last digit is always "d".
and v2:
```
^[a-z2-7]{16}\.onion$
```
What do the new addresses look like, do they have the same characters and just 56 of them? This sho...We have regexes for ~~v1~~ v3:
```
^[a-z2-7]{56}\.onion$
```
where the last digit is always "d".
and v2:
```
^[a-z2-7]{16}\.onion$
```
What do the new addresses look like, do they have the same characters and just 56 of them? This should be in the manual, which says:
```
Valid onion addresses contain 16 characters in a-z2-7 plus ".onion", and valid auth cookies contain 22 characters in A-Za-z0-9+/.
```
**Trac**:
**Username**: ageisp0lisTor: unspecifiedtraumschuletraumschulehttps://gitlab.torproject.org/tpo/core/tor/-/issues/25661RendPostPeriod and HiddenServiceAuthorizeClient are v2 only2021-09-30T13:46:29ZteorRendPostPeriod and HiddenServiceAuthorizeClient are v2 onlyRendPostPeriod and HiddenServiceAuthorizeClient only apply to v2 onion services. We should update the man page so this is clearer.RendPostPeriod and HiddenServiceAuthorizeClient only apply to v2 onion services. We should update the man page so this is clearer.Tor: 0.3.3.x-final