The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-07-22T16:26:01Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/6304CircuitBuildTimeout default value does not match man page2021-07-22T16:26:01ZDavid Fifielddcf@torproject.orgCircuitBuildTimeout default value does not match man pageRunning tor with
```
LearnCircuitBuildTimeout 0
```
and not specifiying any `CircuitBuildTimeout` gives a misleading warning about a timeout of 0:
```
Jul 05 02:48:16.974 [warn] CircuitBuildTimeout is shorter (0 seconds) than recommended...Running tor with
```
LearnCircuitBuildTimeout 0
```
and not specifiying any `CircuitBuildTimeout` gives a misleading warning about a timeout of 0:
```
Jul 05 02:48:16.974 [warn] CircuitBuildTimeout is shorter (0 seconds) than recommended (10 seconds), and LearnCircuitBuildTimeout is disabled. If tor isn't working, raise this value or enable LearnCircuitBuildTimeout.
```
The ticket that resulted in this warning is legacy/trac#5452.Tor: 0.2.4.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/6024documentation: HiddenServicePort is TCP only2021-07-22T16:26:23Zmakerdocumentation: HiddenServicePort is TCP only< rransom> Unfortunately, the man page doesn't say that HiddenServicePort is TCP only. Please open a Trac ticket for that.< rransom> Unfortunately, the man page doesn't say that HiddenServicePort is TCP only. Please open a Trac ticket for that.Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/5685Publish node best practices doc and scripts2021-07-22T16:26:23ZMike PerryPublish node best practices doc and scriptsI need to convert the Tor Node Best Practices tor-relays post into a wiki page and container creation+update scripts for CentOS/RHEL and Ubuntu LTS.
https://lists.torproject.org/pipermail/tor-relays/2012-April/001268.htmlI need to convert the Tor Node Best Practices tor-relays post into a wiki page and container creation+update scripts for CentOS/RHEL and Ubuntu LTS.
https://lists.torproject.org/pipermail/tor-relays/2012-April/001268.htmlTor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/5437man page: IsolateClientProtocol needs clarification?2021-07-22T16:26:23Zcypherpunksman page: IsolateClientProtocol needs clarification?IsolateClientProtocol says
"Don't share circuits with streams using a different protocol. (... TransPort connections, NATDPort connections and DNSPort requests are all considered to be different protocols.)"
But further down: "By defau...IsolateClientProtocol says
"Don't share circuits with streams using a different protocol. (... TransPort connections, NATDPort connections and DNSPort requests are all considered to be different protocols.)"
But further down: "By default, streams received on different ports are always isolated from one another.)"
Isn't the first one redundant then? It still applies to SOCKS v4 vs v5 but not really to different ports.Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/5259Man page entry for MaxCircuitDirtiness is incomplete2021-07-22T16:26:23ZRobert RansomMan page entry for MaxCircuitDirtiness is incompleteThe man page description of MaxCircuitDirtiness doesn't mention that it is applied based on the _last_ time a stream was attached to a hidden-service rendezvous circuit, rather than the _first_ time as for general-purpose circuits.
It a...The man page description of MaxCircuitDirtiness doesn't mention that it is applied based on the _last_ time a stream was attached to a hidden-service rendezvous circuit, rather than the _first_ time as for general-purpose circuits.
It also doesn't mention any minimum or maximum values. (I sure hope there is a minimum value -- we don't want users thinking that it's specified in minutes and setting it to 5.)Tor: 0.2.2.x-finalRobert RansomRobert Ransomhttps://gitlab.torproject.org/tpo/core/tor/-/issues/5106Clarify obfsproxy proposal wrt use of TOR_PT_EXTENDED_SERVER_PORT env variable2021-07-22T16:26:23ZSebastian HahnClarify obfsproxy proposal wrt use of TOR_PT_EXTENDED_SERVER_PORT env variableIn legacy/trac#5097 we made some changes, and then made some more changes in Tor on top of rransom's 5097 branches. We should extend the spec to say that if Tor sets an empty env variable, that means tor doesn't use the extended orport f...In legacy/trac#5097 we made some changes, and then made some more changes in Tor on top of rransom's 5097 branches. We should extend the spec to say that if Tor sets an empty env variable, that means tor doesn't use the extended orport functionality.Tor: 0.2.3.x-finalGeorge KadianakisGeorge Kadianakishttps://gitlab.torproject.org/tpo/core/tor/-/issues/5005False statement in ClientOnly man-page description2021-07-22T16:26:23ZRobert RansomFalse statement in ClientOnly man-page descriptionThe man page states: “Tor is pretty smart at figuring out whether you are reliable and high-bandwidth enough to be a useful server.” This statement is false.
Reported by XD.The man page states: “Tor is pretty smart at figuring out whether you are reliable and high-bandwidth enough to be a useful server.” This statement is false.
Reported by XD.Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/4310alphabetize torrc options within sections2021-07-22T16:26:23ZRoger Dingledinealphabetize torrc options within sectionsOnce upon a time the man page entries were alphabetical. Then we started adding a few near the other ones when it made sense. Now it's a mishmash of alphabetical-except-when-we-decided-not-to-do-it-that-way.
We should take a step back a...Once upon a time the man page entries were alphabetical. Then we started adding a few near the other ones when it made sense. Now it's a mishmash of alphabetical-except-when-we-decided-not-to-do-it-that-way.
We should take a step back and think about a way to organize the options into categories so it's possible to a) get a sense of what all you can configure, and b) find the thing you're looking for.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/4260[PATCH] Update TOR build instructions for mingw2021-07-22T16:26:23ZTrac[PATCH] Update TOR build instructions for mingwHi,
I've updated the documentation for building TOR on MinGW, and attached the result (and the patch). Please, consider replacing the file <doc/tor-win32-mingw-creation.txt> with it.
Here are the main changes:
- the MinGW installer in...Hi,
I've updated the documentation for building TOR on MinGW, and attached the result (and the patch). Please, consider replacing the file <doc/tor-win32-mingw-creation.txt> with it.
Here are the main changes:
- the MinGW installer includes the MSYS and DTK packages, so there no need to download and install them separately.
- there's no more issue with symlinks for openssl.
- specifying "mingw" to the "Configure" command is enough to disable openssl ciphers/hashes that don't compile on MinGW.
- since v1.2.5, zlib needs some extra (?) environment variables for its installation.
- the libraries download links have been updated so that they point to the latest version to date.
- instructions for executing unit-tests have been added for the libraries and TOR.
Maybe zlib should be built before openssl since some optional features of openssl seems to depend on zlib. I followed these instructions in order to build TOR successfully on my WinXP computer.
**Trac**:
**Username**: Tey'Tor: unspecifiedErinn ClarkErinn Clarkhttps://gitlab.torproject.org/tpo/core/tor/-/issues/4210Undefined version comparisions2021-07-22T16:26:23ZDamian JohnsonUndefined version comparisionsWhile writing the version parsing for stem I noticed that the version spec [1] doesn't define how to compare empty tags and patch levels. For instance, if "1.2.3.4-myTag" is a greater or lower version than "1.2.3-myTag".
My suggestion w...While writing the version parsing for stem I noticed that the version spec [1] doesn't define how to compare empty tags and patch levels. For instance, if "1.2.3.4-myTag" is a greater or lower version than "1.2.3-myTag".
My suggestion would be to add a note that an undefined patch is zero and undefined tag equates to the empty string. Ie...
"1.2.3-myTag" == "1.2.3.0-myTag"
"1.2.3.4" == "1.2.3.4-"
Cheers! -Damian
[1] https://gitweb.torproject.org/torspec.git/blob/HEAD:/version-spec.txtTor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/3964'--service install' ignores all other command-line arguments2021-07-22T16:26:23ZRobert Ransom'--service install' ignores all other command-line argumentsI ran `tor --service install -f C:/WORK/Tor/etc/torrc` as a Windows administrator, and it created a Windows NT service to run the command '`"C:\WORK\Tor\bin\tor.exe" --nt-service`'. It should have included '`-f C:/WORK/Tor/etc/torrc`' o...I ran `tor --service install -f C:/WORK/Tor/etc/torrc` as a Windows administrator, and it created a Windows NT service to run the command '`"C:\WORK\Tor\bin\tor.exe" --nt-service`'. It should have included '`-f C:/WORK/Tor/etc/torrc`' on the service's command line.Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/3771Man page does not say that HiddenServiceDir must already exist2021-07-22T16:26:22ZRobert RansomMan page does not say that HiddenServiceDir must already existTor: 0.2.2.x-finalRobert RansomRobert Ransomhttps://gitlab.torproject.org/tpo/core/tor/-/issues/3176Spec the max descriptor sizes2021-07-22T16:26:22ZcypherpunksSpec the max descriptor sizesAllowing arbitrarily large descriptors is bad for everyone, because they have to fetch all that data. Tor currently limits descriptors to 200000 bytes, we should actually spec that out tho.Allowing arbitrarily large descriptors is bad for everyone, because they have to fetch all that data. Tor currently limits descriptors to 200000 bytes, we should actually spec that out tho.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/2987specify the lines in Tor's state file2021-07-22T16:26:22ZRoger Dingledinespecify the lines in Tor's state fileWhen looking through the state file to try to sort out legacy/trac#2704, I realized that I'm only guessing as to the *intended* meaning of lines like BWHistoryWriteMaxima.
We should write them down somewhere so we can keep track of what...When looking through the state file to try to sort out legacy/trac#2704, I realized that I'm only guessing as to the *intended* meaning of lines like BWHistoryWriteMaxima.
We should write them down somewhere so we can keep track of what to expect and what it means.
Nick suggests that this shouldn't be a spec file, but instead might go in the doc directory.Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/2865Update manpage for *Statistics options2021-07-22T16:26:22ZSebastian HahnUpdate manpage for *Statistics optionsWhen we changed some defaults for 0.2.3.x, we forgot to update the manpage. This should probably explain the default in the different modes of operation.When we changed some defaults for 0.2.3.x, we forgot to update the manpage. This should probably explain the default in the different modes of operation.Tor: 0.2.3.x-finalSebastian HahnSebastian Hahnhttps://gitlab.torproject.org/tpo/core/tor/-/issues/2177Typo in Tor manpage2021-07-22T16:26:22ZJens KubiezielTypo in Tor manpageThere is a typo in `man` `torrc`. From tor.1.txt:
`**ConLimit** __NUM__::`
However the document further writes `ConnLimit` and also `tor --list-torrc-options` uses to 'n'. I'm using Tor (git: c109ffaef9a166e99778e401deaa4d842d749d40).There is a typo in `man` `torrc`. From tor.1.txt:
`**ConLimit** __NUM__::`
However the document further writes `ConnLimit` and also `tor --list-torrc-options` uses to 'n'. I'm using Tor (git: c109ffaef9a166e99778e401deaa4d842d749d40).Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/1384Document what happens if options are defined more than once2021-07-22T16:26:22ZSebastian HahnDocument what happens if options are defined more than onceCurrently, we're allowing users to set some options like DataDirectory or User as often as they want. I've looked around, but we don't tell anyone what will happen in that case - currently, the option that is defined later will win, and ...Currently, we're allowing users to set some options like DataDirectory or User as often as they want. I've looked around, but we don't tell anyone what will happen in that case - currently, the option that is defined later will win, and command-line options win over torrc options.
Did I just not find this anywhere, or is that more than an implementation detail? Do we want to warn when some option is specified twice, and it can only have one value?
Question raised by roconnor on #tor, who wants to package Tor for NixOS.Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/tpo/web/manual/-/issues/158Update instructions about using built-in bridges in Tor Browser2024-03-18T18:04:33Zebanamebanam@torproject.orgUpdate instructions about using built-in bridges in Tor Browserhttps://tb-manual.torproject.org/circumvention/
The UX has changed a bit. Let's review and update this section about using built-in bridges with Tor Browser.
> USING PLUGGABLE TRANSPORTS
>
> To use a pluggable transport, click "Configu...https://tb-manual.torproject.org/circumvention/
The UX has changed a bit. Let's review and update this section about using built-in bridges with Tor Browser.
> USING PLUGGABLE TRANSPORTS
>
> To use a pluggable transport, click "Configure Connection" when starting Tor Browser for the first time. Under the "Bridges" section, locate the option "Choose from one of Tor Browser's built-in bridges" and click on "Select a Built-In Bridge" option. From the menu, select whichever pluggable transport you'd like to use.
>
> Once you've selected the pluggable transport, scroll up and click "Connect" to save your settings.
>
> Or, if you have Tor Browser running, click on "Settings" in the hamburger menu (≡) and then on "Connection" in the sidebar. Under the "Bridges" section, locate the option "Choose from one of Tor Browser's built-in bridges" and click on "Select a Built-In Bridge" option. Choose whichever pluggable transport you'd like to use from the menu. Your settings will automatically be saved once you close the tab.
/cc @nina @emmapeelebanamebanam@torproject.orgebanamebanam@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/358Add Letterboxing to the glossary2024-03-18T16:11:22ZemmapeelAdd Letterboxing to the glossaryWe need to add Letterboxing to the glossary, as it is a new term that we use on the documentation.We need to add Letterboxing to the glossary, as it is a new term that we use on the documentation.https://gitlab.torproject.org/tpo/web/manual/-/issues/157Add entry about letterboxing (about:manual#letterboxing)2024-03-12T20:36:03Zma1Add entry about letterboxing (about:manual#letterboxing)We're implementing a `Learn more` link in the new user-facing letteboxing preferences (tpo/applications/tor-browser#41916) and we need some content to be referenced by about:manual#letterboxing :)
@donuts' [comment](https://gitlab.torp...We're implementing a `Learn more` link in the new user-facing letteboxing preferences (tpo/applications/tor-browser#41916) and we need some content to be referenced by about:manual#letterboxing :)
@donuts' [comment](https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/32324#note_2876483):
> It's on support-dot, but possibly not the manual?
> https://support.torproject.org/tbb/maximized-torbrowser-window/ebanamebanam@torproject.orgebanamebanam@torproject.org