The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-06-27T13:18:57Zhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/19116Add scripts to chutney so it works on a tor binary2020-06-27T13:18:57ZteorAdd scripts to chutney so it works on a tor binaryIf chutney was self-contained and could run tests on a plain tor binary, it would be easier to do jenkins tests using chutney.
To make chutney work, we use parts of the tor git tree, including some Makefile targets to select the tests w...If chutney was self-contained and could run tests on a plain tor binary, it would be easier to do jenkins tests using chutney.
To make chutney work, we use parts of the tor git tree, including some Makefile targets to select the tests we run, and src/test/test-network.sh.
If we move these scripts to the chutney tree, we can run a set of chutney targets anywhere, without requiring a tor build tree.teorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/40119Tor fails to build on Ubuntu Groovy Gorilla: -Wextra-semi only used for Obj-C...2022-11-03T19:44:58ZAlexander Færøyahf@torproject.orgTor fails to build on Ubuntu Groovy Gorilla: -Wextra-semi only used for Obj-C and C++@weasel reported the following error today on `#tor-dev`: https://jenkins.torproject.org/job/tor-ci-linux-master/4880/
The error seems to be:
cc1: error: command-line option '-Wextra-semi' is valid for C++/ObjC++ but not for C [-We...@weasel reported the following error today on `#tor-dev`: https://jenkins.torproject.org/job/tor-ci-linux-master/4880/
The error seems to be:
cc1: error: command-line option '-Wextra-semi' is valid for C++/ObjC++ but not for C [-Werror]
cc1: all warnings being treated as errors
As seen in: https://jenkins.torproject.org/job/tor-ci-linux-master/4880/ARCHITECTURE=amd64,SUITE=groovy/consoleText
We should probably disable `-Wextra-semi` as this seems to only apply for C++ and Objective C.Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/core/torsocks/-/issues/17760Torsocks doesn't quote variables, will choke on spaces and special characters...2020-06-27T14:12:06ZteorTorsocks doesn't quote variables, will choke on spaces and special characters in pathsThe script that launches a command using torsocks checks a lot of paths without quoting them.
This means that paths with spaces will cause errors, and paths with special characters may have unintended effects.The script that launches a command using torsocks checks a lot of paths without quoting them.
This means that paths with spaces will cause errors, and paths with special characters may have unintended effects.David Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/29565Fix broker robots.txt to disallow crawling2020-06-27T13:40:32ZDavid Fifielddcf@torproject.orgFix broker robots.txt to disallow crawlingFrom comment:11:ticket:28848 and https://github.com/ahf/snowflake-notes/blob/fb4304a7df08c6ddeeb103f38fc9103721a20cd9/Broker.markdown#the-robotstxt-handler:
> - Was the question about crawling ever answered? I can't think of a very good...From comment:11:ticket:28848 and https://github.com/ahf/snowflake-notes/blob/fb4304a7df08c6ddeeb103f38fc9103721a20cd9/Broker.markdown#the-robotstxt-handler:
> - Was the question about crawling ever answered? I can't think of a very good reason not to allow it. Even if censors were crawling the web for Snowflake brokers, they could get this information much more easily just from the source code.
I believe the intention behind the robots.txt handler is to prevent search engines from indexing any pages on the site, because there's no permanent information there, not for any security or anti-enumeration reason.
ahf points out that the current robots.txt achieves the opposite: it allows crawling of all pages by anyone. Instead of
```
User-agent: *
Disallow:
```
it should be
```
User-agent: *
Disallow: /
```Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/web/community/-/issues/167[Relay Operations][Getting Help] Add hyperlinks to IRC channel (OFTC webchat)...2021-04-08T20:19:54Zchampionquizzerchampionquizzer@torproject.org[Relay Operations][Getting Help] Add hyperlinks to IRC channel (OFTC webchat) and mailing-list archive1. In this sentence- *You can also get help by joining the IRC channel #tor-relays* on the ['Getting Help' page](https://community.torproject.org/relay/getting-help/), we must redirect the user to #tor-relays IRC channel on OFTC webchat ...1. In this sentence- *You can also get help by joining the IRC channel #tor-relays* on the ['Getting Help' page](https://community.torproject.org/relay/getting-help/), we must redirect the user to #tor-relays IRC channel on OFTC webchat i.e. https://webchat.oftc.net/?channels=tor-relays (to maintain consistency throughout our docs).
2. In this sentence- *Make sure to check out the archives!*, we must hyper link the *archives* to the tor-relays mailing-list archives here: https://lists.torproject.org/pipermail/tor-relays/championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/web/community/-/issues/170Instructions on Fedora relay guide looks incomplete (step 2 and 3)2021-04-08T21:38:31ZGusInstructions on Fedora relay guide looks incomplete (step 2 and 3)
```
2. # 3. Add the following to /etc/yum.repos.d/tor.repo and then install the tor package.
```
http://3gldbgtv5e4god56.onion/relay/setup/guard/fedora/
```
2. # 3. Add the following to /etc/yum.repos.d/tor.repo and then install the tor package.
```
http://3gldbgtv5e4god56.onion/relay/setup/guard/fedora/GusGushttps://gitlab.torproject.org/tpo/web/community/-/issues/173Typo lins -> lines2020-12-14T21:59:27ZGusTypo lins -> linesA translator reported:
> "You can simply add it next to the first ORPort lins in your torrc file."
I guess, the word "lins" in the original text is actually "lines".A translator reported:
> "You can simply add it next to the first ORPort lins in your torrc file."
I guess, the word "lins" in the original text is actually "lines".GusGushttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac/-/issues/13369Typo fix in pt-spec.txt: "KeyWordChar"2020-06-27T13:43:57ZDavid Fifielddcf@torproject.orgTypo fix in pt-spec.txt: "KeyWordChar"This patch fixes inconsistent capitalization of this identifier.This patch fixes inconsistent capitalization of this identifier.George KadianakisGeorge Kadianakishttps://gitlab.torproject.org/tpo/core/chutney/-/issues/20409When some chutney tors die, clean up the rest2020-06-27T13:18:54ZteorWhen some chutney tors die, clean up the restChutney should clean up all the tor processes it starts, and leave all other processes alone.
I think this means adding `pkill -P $$` to the end of chutney/tools/test-network.sh , and making sure it's executed even if chutney returns fa...Chutney should clean up all the tor processes it starts, and leave all other processes alone.
I think this means adding `pkill -P $$` to the end of chutney/tools/test-network.sh , and making sure it's executed even if chutney returns failure.teorteorhttps://gitlab.torproject.org/tpo/core/torsocks/-/issues/22068Make it explicit that Torsocks won't work correctly in certain scenarios in t...2020-06-27T14:12:04ZTracMake it explicit that Torsocks won't work correctly in certain scenarios in the READMEAs far as I understand, Torsocks works by setting LD_PRELOAD, so an application that doesn't uses libc, and instead uses syscalls directly will be able to bypass torsocks and connect directly to the Internet.
I think a warning about it ...As far as I understand, Torsocks works by setting LD_PRELOAD, so an application that doesn't uses libc, and instead uses syscalls directly will be able to bypass torsocks and connect directly to the Internet.
I think a warning about it on the README file, and MAN page is needed, besides making it explicit that using Torsocks is not 100% safe as the README might make you think, for example:
> _Torsocks allows you to use most applications in a safe way with Tor. It ensures that DNS requests are handled safely and explicitly rejects any traffic other than TCP from the application you're using._
> Torsocks is an ELF shared library that is loaded before all others. The library overrides every needed Internet communication libc function calls such as connect(2) or gethostbyname(3).
> _This process is transparent to the user and if torsocks detects any communication that can't go through the Tor network such as UDP traffic, for instance, the connection is denied. If, for any reason, there is no way for torsocks to provide the Tor anonymity guarantee to your application, torsocks will force the application to quit and stop everything._
**Trac**:
**Username**: FranciscouzoDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29749Remove never used "userquery" code2022-01-28T11:02:56ZjugaRemove never used "userquery" codesbws: 2.0.x-final-oldhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29953Parent ticket for easy tickets that do not change version2021-06-15T14:21:22ZjugaParent ticket for easy tickets that do not change versionChild issues:
- #29952
- #28045
- #29294
- #28589
- #28758
- #28759Child issues:
- #29952
- #28045
- #29294
- #28589
- #28758
- #28759sbws: unspecifiedhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29047Improve code style following PEP8 and PEP2572022-02-17T08:49:04ZjugaImprove code style following PEP8 and PEP257sbws: unspecifiedhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29048Remove unused code2022-02-17T08:49:03ZjugaRemove unused codesbws: 1.2.x-finalhttps://gitlab.torproject.org/tpo/web/tpo/-/issues/123Update /press link2020-12-21T17:21:06ZGusUpdate /press link> I can see our blog is listed here: https://www.torproject.org/press/ as a link to an article on techlector.com. I am glad to see that. However, we have rebranded our domain from techlector.com to techreen.com. Could you please re-edit ...> I can see our blog is listed here: https://www.torproject.org/press/ as a link to an article on techlector.com. I am glad to see that. However, we have rebranded our domain from techlector.com to techreen.com. Could you please re-edit this so that the old link (https://techlector.com/tor-project-will-transfer-to-azure-to-continue-offering-domain-fronting/) will be changed to https://techreen.com/tor-project-will-transfer-to-azure-to-continue-offering-domain-fronting/?GusGushttps://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/15178Improve Atlas' error messages2020-06-27T14:25:21ZPhilipp Winterphw@torproject.orgImprove Atlas' error messagesWhenever Onionoo is offline, Atlas shows an error message:
> Backend error!
> The backend server replied with an error to your query. This probably means that you did not properly format your query. If your query was properly formatted ...Whenever Onionoo is offline, Atlas shows an error message:
> Backend error!
> The backend server replied with an error to your query. This probably means that you did not properly format your query. If your query was properly formatted it may mean that there is an issue with your browser/add-ons. Please report which browser/addons/etc. you're using to the bug tracker.
This suggests that the user made a mistake, which results in several trac tickets every time Onionoo is offline. We should improve the error message and make it clear that waiting a little bit might solve the problem. Here's a suggestion:
> Backend error!
> Atlas is unable to get a response from its backend server. This probably means that the backend server is unavailable right now. This can also happen, however, if you did not format your query correctly. Please have a look at [this page](https://atlas.torproject.org/#about) that explains what type of search queries are supported by Atlas.Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/tpo/core/chutney/-/issues/21466Get chutney's scripts working with standard shell script checking options2020-07-23T20:31:12ZteorGet chutney's scripts working with standard shell script checking optionsWe'll make fewer mistakes if we:
```
set -e
set -u
```
at the top of every script.We'll make fewer mistakes if we:
```
set -e
set -u
```
at the top of every script.https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/53GetTor IPFS Provider2022-10-05T13:39:21ZTracGetTor IPFS ProviderI think IPFS could be a good provider by having support for downloading from multiple sources and while the clients don't work through Tor, there are many public gateways.
When attempting to find a list of public gateways, I found https...I think IPFS could be a good provider by having support for downloading from multiple sources and while the clients don't work through Tor, there are many public gateways.
When attempting to find a list of public gateways, I found https://github.com/ipfs/public-gateway-checker/blob/master/gateways.json .
I am not sure how the procedure could be automated, but manually it would work by installing ipfs, creating a folder for requested content, "ipfs add -r directory/" and going to https://example.com/ipfs/HASH (which was given by the previous command) to download it. Alternatively for single file "ipfs add -w file" so a directory is created for it preserving the filename instead of changing it to the hash when downloading.
Volunteers could also host the content by using "ipfs pin add HASH" possibly reducing server load.
**Trac**:
**Username**: Mkaysihttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/30868Modify client rendezvous library to remove hard-coded responses2020-06-27T13:40:27ZCecylia BocovichModify client rendezvous library to remove hard-coded responsesClient tests rely of `client/lib/rendezvous.go` rely on specific HTTP response bodies which are prone to change and unnecessaryClient tests rely of `client/lib/rendezvous.go` rely on specific HTTP response bodies which are prone to change and unnecessaryTor: unspecifiedhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/28432German translation of 'circuit' should be made consistent on the landing page2020-06-27T13:45:03ZwaywardGerman translation of 'circuit' should be made consistent on the landing pageUser pointed out below that the German localization of 'circuit' is inconsistent in various places:
https://blog.torproject.org/comment/277954#comment-277954
"In the German version of TBB, on the introductory page, there are three diff...User pointed out below that the German localization of 'circuit' is inconsistent in various places:
https://blog.torproject.org/comment/277954#comment-277954
"In the German version of TBB, on the introductory page, there are three different translations for the English 'circuit'. There is: 1. Circuit-Ansicht (which is no translation!). 2. In the explanatory text there is 'Zeige deinen Pfad' - here 'circuit' becomes 'Pfad' (= 'path') and users are told to 'choose'( = 'wählen', which should be "click on" = 'klicken auf' - not 'choose') 'Neuer Pfad für diese Seite'. 3. If you do so and click on the "Informations-Symbol" which is the padlock, you will not get 'Neuer Pfad für diese Seite', but 'Neuen Kanal für diese Seite'. (By the way: this should be: 'NeueR Pfad' (nominative) instead of 'NeueN Pfad' (accusative) - but this is only a minor mistake.)
So you have three names for the English word 'circuit': 1. circuit, 2. Pfad, 3. Kanal
On the right, at the bottom of the introduction. you will read 'Pfad' again. If you click on that field, you will get to Duck Duck Go and you will read 'Circuits' again, and:'Relays'. In the old version of TBB you used 'Relais' as translation for 'relay'. And if you click on the green padlock, 'relay' is translated as 'Verteiler'."
We should pick which word works best and change these strings to match where appropriate.emmapeelemmapeel