The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-06-27T13:41:18Zhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29722Document that authorities are not measured2020-06-27T13:41:18ZjugaDocument that authorities are not measuredsbws: 1.1.x-finaljugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29295Remove three consecutive attempts to build a circuit2020-12-13T13:16:35ZjugaRemove three consecutive attempts to build a circuitCurrently, ~~a relay is measured to~~ when measuring a relay, circuits are attempted to be built a maximum of 3 consecutives times when the previous ~~measurements fail~~ attempt fails, but in most of the cases, when ~~measuring a relay~...Currently, ~~a relay is measured to~~ when measuring a relay, circuits are attempted to be built a maximum of 3 consecutives times when the previous ~~measurements fail~~ attempt fails, but in most of the cases, when ~~measuring a relay~~ building a circuit fails the first time, it will also fail the consecutives times.
The relay will be measured anyway in the next iteration.
Based on what we talked in https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetworkTeam/Notes/SBWSRoadmap#Questions
Edit: the three attempts happen when trying to build the circuit when measuring a relay, but it's not three attempts to measure the relay.sbws: 1.0.x-finaljugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29294Create an script to automate releases2021-02-18T15:39:51ZjugaCreate an script to automate releasessbws: unspecifiedjugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29149Update/improve documentation on how the scanner/generator work2020-06-27T13:41:21ZjugaUpdate/improve documentation on how the scanner/generator workCurrently, the main documentation about sbws works is https://sbws.readthedocs.io/en/latest/specification.html, but it's not updated.
There's also no documentation about what the main functions (`run_speed_test` and `DestinationList`).
I...Currently, the main documentation about sbws works is https://sbws.readthedocs.io/en/latest/specification.html, but it's not updated.
There's also no documentation about what the main functions (`run_speed_test` and `DestinationList`).
It'd also be useful to document how the threads work.sbws: 1.0.x-finaljugajugahttps://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/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/29046Remove unused testnets2022-02-17T08:49:03ZjugaRemove unused testnetsThey were replaced by tests/integration/net and they are not being used anymoreThey were replaced by tests/integration/net and they are not being used anymoresbws: 1.0.x-finaljugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/28759Upload sbws to PyPI2022-02-17T09:44:16ZanadahzUpload sbws to PyPIPackage sbws and upload it to the Python Package Index repository.Package sbws and upload it to the Python Package Index repository.sbws: unspecifiedhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/28758Add requirements files2022-02-17T09:44:16ZanadahzAdd requirements filesAdd a requirements.txt file with the required sbws dependencies.Add a requirements.txt file with the required sbws dependencies.sbws: unspecifiedhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/28045Start supporting python 3.7, python 3.8, and pypy3.52021-02-18T15:39:51ZjugaStart supporting python 3.7, python 3.8, and pypy3.5sbws: 1.2.x-finaljugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/26751sbws should log its version and python's version on startup2020-06-27T13:41:43Zpastlysbws should log its version and python's version on startupAnd maybe stem and requests, if possible.
Low priority.And maybe stem and requests, if possible.
Low priority.sbws: 1.0.x-finalhttps://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/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/core/torsocks/-/issues/14268torsocks "make check" target broken in out of tree builds2020-06-27T14:12:10ZYawning Angeltorsocks "make check" target broken in out of tree buildsShould be obvious from the summary, but this fails, when it shouldn't:
```
$ sh autogen.sh
$ mkdir build
$ cd build
$ ../configure; make; make check
```
The failures happen because the build system assumes that the following files are p...Should be obvious from the summary, but this fails, when it shouldn't:
```
$ sh autogen.sh
$ mkdir build
$ cd build
$ ../configure; make; make check
```
The failures happen because the build system assumes that the following files are present under the location that make was run from:
* tests/run.sh
* tests/test_list
* tests/unit/fixtures
Copying the files manually to the right places under "build" fixes things, so this should be easy to fix.David Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/fallback-scripts/-/issues/26502Stop using the fallback blacklist, and delete it2021-09-16T14:48:14ZteorStop using the fallback blacklist, and delete itWe require relay operators to opt-in to being fallbacks, and we won't ever switch to opt-out. (See legacy/trac#24789.)
So we don't need the fallback blacklist any more.
We should stop loading the blacklist in the script, then delete it.We require relay operators to opt-in to being fallbacks, and we won't ever switch to opt-out. (See legacy/trac#24789.)
So we don't need the fallback blacklist any more.
We should stop loading the blacklist in the script, then delete it.Tor: 0.3.5.x-finalhttps://gitlab.torproject.org/tpo/core/fallback-scripts/-/issues/24791Remove excessive address info from the fallback script log2020-06-27T14:11:40ZteorRemove excessive address info from the fallback script logThis makes it easier for people to focus on the info that actually matters. Also, it makes it fit in a single terminal window.This makes it easier for people to focus on the info that actually matters. Also, it makes it fit in a single terminal window.Tor: 0.3.3.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/fallback-scripts/-/issues/24790When 0.2.5 is EOL, remove the fallback script comment that refers to 0.2.8 an...2020-06-27T14:11:40ZteorWhen 0.2.5 is EOL, remove the fallback script comment that refers to 0.2.8 and earlierWe don't accept unsupported Tor versions as fallbacks, so there's no reason to talk about other bugs in unsupported versions.We don't accept unsupported Tor versions as fallbacks, so there's no reason to talk about other bugs in unsupported versions.Tor: 0.3.4.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/34382Don't require M_SYSCALL in sandbox.c2022-07-07T00:49:01ZNick MathewsonDon't require M_SYSCALL in sandbox.cIn sandbox.c, we have a platform-dependent M_SYSCALL macro that is used to extract the syscall from a ucontext_t pointer.
But we only use this value for debugging. Perhaps instead we should make it optional, so that platforms where we ...In sandbox.c, we have a platform-dependent M_SYSCALL macro that is used to extract the syscall from a ucontext_t pointer.
But we only use this value for debugging. Perhaps instead we should make it optional, so that platforms where we don't have it defined can still build with m_syscall.
See also legacy/trac#32904 and legacy/trac#30987Tor: 0.4.4.x-finalAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/34311Space out code in relay.c2020-06-27T13:47:38ZNeel Chauhanneel@neelc.orgSpace out code in relay.cYes, I do understand that Tor is working on automatic code checks for things like code spacing and that I should work on that instead of sending spacing patches, but I still noticed a lot of spacing issues in relay.c (more than normal) s...Yes, I do understand that Tor is working on automatic code checks for things like code spacing and that I should work on that instead of sending spacing patches, but I still noticed a lot of spacing issues in relay.c (more than normal) so I just **had** to submit this.
My PR fixes all (or at least most) of relay.c.Tor: 0.4.4.x-finalNeel Chauhanneel@neelc.orgNeel Chauhanneel@neelc.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/34246Add a link to the formatted architecture docs in src/mainpage.md2021-07-22T16:18:20ZteorAdd a link to the formatted architecture docs in src/mainpage.mdWhen I open up src/mainpage.md. it's obviously meant to be formatted by a markdown parser. (And GitHub's markdown doesn't seem to handle "@" directives.)
Can you add a link to the formatted output at the top of mainpage.md ?When I open up src/mainpage.md. it's obviously meant to be formatted by a markdown parser. (And GitHub's markdown doesn't seem to handle "@" directives.)
Can you add a link to the formatted output at the top of mainpage.md ?Tor: 0.4.4.x-final