The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-07-22T16:19:44Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/31478CodeStructure.md is not markdown compliant2021-07-22T16:19:44ZTracCodeStructure.md is not markdown compliantHello,
While going through the Tor project documentation, I saw a TODO in the file `doc/HACKING/CodeStructure.md` which is currently using a malformed markdown.
I will re-format the documentation in this file if that's fine for you.
*...Hello,
While going through the Tor project documentation, I saw a TODO in the file `doc/HACKING/CodeStructure.md` which is currently using a malformed markdown.
I will re-format the documentation in this file if that's fine for you.
**Trac**:
**Username**: aveuillerTor: 0.4.2.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/31418Fix some typos in the man page2021-07-22T16:19:44ZteorFix some typos in the man pageTor: 0.4.2.x-finalteorteorhttps://gitlab.torproject.org/tpo/web/support/-/issues/10Add instructions how to verify signatures on Android2021-08-23T16:30:49ZGusAdd instructions how to verify signatures on Androidneeds a section for Android.
migrated from: https://trac.torproject.org/projects/tor/ticket/27514needs a section for Android.
migrated from: https://trac.torproject.org/projects/tor/ticket/27514https://gitlab.torproject.org/tpo/core/tor/-/issues/31320Add an IPv6 ORPort example to the torrc.minimal.in-staging and torrc.sample.i...2021-07-22T16:19:44ZteorAdd an IPv6 ORPort example to the torrc.minimal.in-staging and torrc.sample.in filesWe don't currently have any IPv6 ORPorts in the example torrc files, but we should.We don't currently have any IPv6 ORPorts in the example torrc files, but we should.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/31190List all valid DirPort urls2021-09-16T14:23:38ZDamian JohnsonList all valid DirPort urlsHi network team. Every so often folks stumble on DirPort resources Stem doesn't recognize...
https://trac.torproject.org/projects/tor/ticket/30930
https://trac.torproject.org/projects/tor/ticket/31187
Unfortunately section 'B' is the c...Hi network team. Every so often folks stumble on DirPort resources Stem doesn't recognize...
https://trac.torproject.org/projects/tor/ticket/30930
https://trac.torproject.org/projects/tor/ticket/31187
Unfortunately section 'B' is the closest enumeration we have, but even it doesn't include everything...
https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n3888
Could we spec a listing of all urls the DirPort supports (similar to the GETINFO section in the control-spec)?
Thanks!https://gitlab.torproject.org/tpo/core/tor/-/issues/31189potential docs update needed for GuardLifetime?2020-07-14T22:24:18Zcypherpunkspotential docs update needed for GuardLifetime?The documentation for the GuardLifetime torrc option says:
```
If nonzero, and UseEntryGuards is set, minimum time to keep a guard before
picking a new one. If zero, we use the GuardLifetime parameter from the
consensus directo...The documentation for the GuardLifetime torrc option says:
```
If nonzero, and UseEntryGuards is set, minimum time to keep a guard before
picking a new one. If zero, we use the GuardLifetime parameter from the
consensus directory. No value here may be less than 1 month or greater
than 5 years; out-of-range values are clamped. (Default: 0)
```
In commit hash 385602e9826e79dbf0d8b51abfd925e59f275708 it appears that there was a behavior change which allows guard lifetimes of 1 day or greater (grep for `get_options()->GuardLifetime >= 86400`). `git blame` indicated the docs for the `GuardLifetime` option haven't been touched in 6-7 years, so I think they need an update after this change.
Is the expected behavior that setting `UseEntryGuards 1` and `GuardLifetime 1 day` will result in guards being used for no longer than one day?Tor: 0.4.2.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/web/community/-/issues/72[Content][Community Resources] GoodBad ISPs page improvements2023-11-08T23:50:48ZGus[Content][Community Resources] GoodBad ISPs page improvements* [x] Create link anchors for the countries
* [ ] Create Table of Content* [x] Create link anchors for the countries
* [ ] Create Table of ContentJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/31116clarify socks-extensions.txt spec resolve command and response2022-06-17T13:11:42Zcypherpunksclarify socks-extensions.txt spec resolve command and responsehttps://gitweb.torproject.org/torspec.git/tree/socks-extensions.txt
The spec leaves multiple open questions:
- What does "initiates a remote lookup of the hostname" mean?
The spec could be improved by saying "A" or/and "AAAA" DNS looku...https://gitweb.torproject.org/torspec.git/tree/socks-extensions.txt
The spec leaves multiple open questions:
- What does "initiates a remote lookup of the hostname" mean?
The spec could be improved by saying "A" or/and "AAAA" DNS lookup is performed.
- There is no information about the response in torspec.git/tree/socks-extensions.txt at all
related:
legacy/trac#31115
https://lists.torproject.org/pipermail/tor-dev/2019-July/013931.htmlhttps://gitlab.torproject.org/tpo/web/community/-/issues/60[Content][Onion Services] Terminology2022-05-04T14:17:09ZGus[Content][Onion Services] TerminologyBe consistent in our documentation, and apply the terminology:
* onionsites: websites using Onion Services.
* Onion Services: to talk about the technology.Be consistent in our documentation, and apply the terminology:
* onionsites: websites using Onion Services.
* Onion Services: to talk about the technology.https://gitlab.torproject.org/tpo/core/tor/-/issues/31078improve docs for config var abstraction2021-11-06T13:27:41ZTaylor Yuimprove docs for config var abstractionIn ticket:30864#comment:11, I commented on some vagueness in the code comments that made it difficult for me to understand some of what's going on.
We should revise those comments to use improved terminology to help other developers und...In ticket:30864#comment:11, I commented on some vagueness in the code comments that made it difficult for me to understand some of what's going on.
We should revise those comments to use improved terminology to help other developers understand what's going on. This might need to wait until the other refactoring on that branch is done.Tor: 0.4.7.x-freezeNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30955Update the fallback entry in the man page2021-07-22T16:19:44ZteorUpdate the fallback entry in the man page"FallbackDir ipv4address:port"
"FallbackDir ipv4address:dirport"
"DirAuthority [nickname] [flags] ipv4address:port"
"DirAuthority [nickname] [flags] ipv4address:dirport"
And similarly for orport.
"The provided port value is a dirport;..."FallbackDir ipv4address:port"
"FallbackDir ipv4address:dirport"
"DirAuthority [nickname] [flags] ipv4address:port"
"DirAuthority [nickname] [flags] ipv4address:dirport"
And similarly for orport.
"The provided port value is a dirport; clients ignore this in favor of the specified "orport=" value."
"Clients always use the orport. Relays prefer the dirport, but will use the orport in some circumstances."
Add something to the FallbackDir entry talking about how the DirPort is used by the checking script?Tor: 0.4.2.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30745Document disabled CI2021-07-22T16:19:44ZteorDocument disabled CIAdd a section to our CI status page for disabled CI
Add a section to doc/HACKING/ReleasingTor.md reminding releasers to
manually check the status of whatever the disabled CI would have
checked.
CI person should periodically look at the...Add a section to our CI status page for disabled CI
Add a section to doc/HACKING/ReleasingTor.md reminding releasers to
manually check the status of whatever the disabled CI would have
checked.
CI person should periodically look at these jobs.Tor: 0.4.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30630Put CI URLs in ReleasingTor.md2021-07-22T16:19:44ZteorPut CI URLs in ReleasingTor.mdarma asked us where the CI builders are.
The list is in ReleasingTor.md and on the wiki, but only the wiki has the URLs:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailures#CIBuildersarma asked us where the CI builders are.
The list is in ReleasingTor.md and on the wiki, but only the wiki has the URLs:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailures#CIBuildersTor: 0.4.1.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30455Improve documentation for chutney warnings in "make test-network-all"2021-07-22T16:19:43ZNick MathewsonImprove documentation for chutney warnings in "make test-network-all"It appears that in fb32c522320430f, we added a second call to test-network.sh inside our test-network-all loop. Now the code looks like this:
```
for f in $$flavors; do \
$(SHELL) $(top_srcdir)/test-driver --test-name $$f --log-file...It appears that in fb32c522320430f, we added a second call to test-network.sh inside our test-network-all loop. Now the code looks like this:
```
for f in $$flavors; do \
$(SHELL) $(top_srcdir)/test-driver --test-name $$f --log-file $(TEST_NETWORK_ALL_LOG_DIR)/$$f.log --trs-file $(TEST_NETWORK_ALL_LOG_DIR)/$$f.trs $(TEST_NETWORK_ALL_DRIVER_FLAGS) $(top_srcdir)/src/test/test-network.sh --flavor $$f $(TEST_NETWORK_FLAGS); \
$(top_srcdir)/src/test/test-network.sh $(TEST_NETWORK_WARNING_FLAGS); \
done; \
```
I might be wrong, but it looks to me like we're calling test-network.sh twice in each loop: once through `test-driver`, and once directly.
I'm not going to work on this till teor is back, though, since there are dragons here that I do not understand.Tor: 0.4.2.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30349Document member-hiding conventions for structs2022-06-17T14:06:50ZTaylor YuDocument member-hiding conventions for structsWe should document whatever conventions we choose for hiding struct members, probably in doc/HACKING. Also we should make tools for searching for violations, e.g., code that directly accesses private members without using the appropriate...We should document whatever conventions we choose for hiding struct members, probably in doc/HACKING. Also we should make tools for searching for violations, e.g., code that directly accesses private members without using the appropriate macros. (A fairly simple Coccinelle script should work for this.)https://gitlab.torproject.org/tpo/core/tor/-/issues/30261Add "How do I find bug or feature versions?" to doc/HACKING2021-07-22T16:19:43ZteorAdd "How do I find bug or feature versions?" to doc/HACKINGWe need to find bugfix versions for changes files and backports, and feature versions for specifications.
Let's document the git commands to do that.
For an example, see:
https://trac.torproject.org/projects/tor/ticket/30224#comment:4We need to find bugfix versions for changes files and backports, and feature versions for specifications.
Let's document the git commands to do that.
For an example, see:
https://trac.torproject.org/projects/tor/ticket/30224#comment:4Tor: 0.4.1.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30240Tor should ship docker images of onion services (and other services)2022-06-17T16:09:30ZGeorge KadianakisTor should ship docker images of onion services (and other services)Seems like people are interested in docker images of Tor relays, or onion services (or even bridgedb). We should consider providing docker images for the people who want to use them.
Here is a recent attempt by Alessandro Fiori:
https:/...Seems like people are interested in docker images of Tor relays, or onion services (or even bridgedb). We should consider providing docker images for the people who want to use them.
Here is a recent attempt by Alessandro Fiori:
https://lists.torproject.org/pipermail/tor-dev/2019-March/013756.html
and there have been previous attempts as well here:
https://blog.jessfraz.com/post/running-a-tor-relay-with-docker/ (tor relay)
Also see this page for an organized version of infrastructure related projects:
https://trac.torproject.org/projects/tor/wiki/community/relay_infrastructure
https://www.andreafortuna.org/2018/11/05/easily-setup-a-onion-service-using-docker/
https://0day.work/dockerized-tor-onion-services-with-vanity-v3-tor-addresses/ (onion services)
We should figure out how to make these unofficial attempt useful to other people by legitimizing them and offering them to people in a useful way.https://gitlab.torproject.org/tpo/core/tor/-/issues/30119cert-spec uses binary encodings but does not specify byte order2021-07-22T16:19:43Zirlcert-spec uses binary encodings but does not specify byte orderFrom looking at the Tor implementation (in a black box way, didn't look at the source code) these seem to be big endian byte order. We should have a note in cert-spec for implementors so they don't have to guess.From looking at the Tor implementation (in a black box way, didn't look at the source code) these seem to be big endian byte order. We should have a note in cert-spec for implementors so they don't have to guess.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30112Fix outdated comments in dirserv_read_measured_bandwidths()2021-09-16T14:19:58ZteorFix outdated comments in dirserv_read_measured_bandwidths()We refactored the function to use tor_getdelim(), but didn't remove the comments about fgets().We refactored the function to use tor_getdelim(), but didn't remove the comments about fgets().Tor: 0.4.1.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30109Document that MapAddress is automatically strict, but does not handle redirects2021-08-23T15:16:06ZteorDocument that MapAddress is automatically strict, but does not handle redirectsWe should document that:
1. StrictNodes does not apply to MapAddress
2. MapAddress ~~falls back to a random exit by default~~ fails rather than falling back to a random exit
Edited to add:
3. If the site does a redirect, MapAddress does...We should document that:
1. StrictNodes does not apply to MapAddress
2. MapAddress ~~falls back to a random exit by default~~ fails rather than falling back to a random exit
Edited to add:
3. If the site does a redirect, MapAddress does not apply to the new siteTor: 0.4.0.x-final