Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:56:54Zhttps://gitlab.torproject.org/legacy/trac/-/issues/18240'make test-stem' yields No rule to make target '"./src/or/tor"'2020-06-13T14:56:54ZRoger Dingledine'make test-stem' yields No rule to make target '"./src/or/tor"'Taking Nick's shiny new 0.2.8.1-alpha test tarball, and after building it, on Debian stable I get:
```
$/tmp/tor-0.2.8.1-alpha$ make test-stem
make: *** No rule to make target '"./src/or/tor"', needed by 'test-stem'. Stop.
```
In the M...Taking Nick's shiny new 0.2.8.1-alpha test tarball, and after building it, on Debian stable I get:
```
$/tmp/tor-0.2.8.1-alpha$ make test-stem
make: *** No rule to make target '"./src/or/tor"', needed by 'test-stem'. Stop.
```
In the Makefile I see:
```
test-stem: need-stem-path $(TESTING_TOR_BINARY)
```
where $TESTING_TOR_BINARY is
```
TESTING_TOR_BINARY = "$(top_builddir)/src/or/tor"
```
I have a src/or/tor file just fine.
I don't know make language, so hopefully this is just an easy obvious fix.Tor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/17290Include network tests with ill-behaved clients and servers2020-06-13T13:29:36ZNick MathewsonInclude network tests with ill-behaved clients and serversThis is a deliverable for October 2016.This is a deliverable for October 2016.https://gitlab.torproject.org/legacy/trac/-/issues/17282Chutney could use a HOWTO for writing new test cases, network tests, etc2020-06-13T13:29:35ZNick MathewsonChutney could use a HOWTO for writing new test cases, network tests, etcDue April 2016Due April 2016https://gitlab.torproject.org/legacy/trac/-/issues/17275Package directory authority scripts for debian in compliant packages2020-06-13T16:13:36ZNick MathewsonPackage directory authority scripts for debian in compliant packagesIn order to reduce the difficulty of being an authority, we should make (compliant) packages for the scripts that we hope authorities will run. This will (ideally) improve the code quality and usability of these scripts.
The scripts in...In order to reduce the difficulty of being an authority, we should make (compliant) packages for the scripts that we hope authorities will run. This will (ideally) improve the code quality and usability of these scripts.
The scripts include:
* guard fraction
* bandwidth authority
* bad exit finder
* probably more!Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/17233MinMeasuredBWsForAuthToIgnoreAdvertised should be lower for Testing networks?2020-06-13T14:49:51ZRoger DingledineMinMeasuredBWsForAuthToIgnoreAdvertised should be lower for Testing networks?```
config.c: V(MinMeasuredBWsForAuthToIgnoreAdvertised, INT, "500"),
```
weasel points out that maybe this should be 0 for testing tor networks?```
config.c: V(MinMeasuredBWsForAuthToIgnoreAdvertised, INT, "500"),
```
weasel points out that maybe this should be 0 for testing tor networks?Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/17013Does chutney need to test various rare IPv6/IPv4 combinations?2020-06-13T13:29:31ZteorDoes chutney need to test various rare IPv6/IPv4 combinations?We could make sure that #16954 enables the following combinations:
* IPv6 bridge client - IPv6 bridge -- ---- hs
* IPv6 bridge client - IPv6 bridge -- IPv6-only Exit
* IPv6 bridge client - IPv6 bridge -- IPv6/IPv4 Exit
* IPv6 bridge cli...We could make sure that #16954 enables the following combinations:
* IPv6 bridge client - IPv6 bridge -- ---- hs
* IPv6 bridge client - IPv6 bridge -- IPv6-only Exit
* IPv6 bridge client - IPv6 bridge -- IPv6/IPv4 Exit
* IPv6 bridge client - IPv6 bridge -- IPv4 Exit
* IPv4 bridge client - IPv4 bridge -- IPv6-only Exit
* IPv4 bridge client - IPv4 bridge -- IPv6/IPv4 Exit
This probably also depends on #17011.
* IPv4 client --- IPv6-only Exit
* IPv4 client --- IPv6/IPv4 Exithttps://gitlab.torproject.org/legacy/trac/-/issues/17011chutney doesn't verify using IPv6 addresses2020-06-13T14:52:27Zteorchutney doesn't verify using IPv6 addressesEven when chutney is using IPv6 exits, it doesn't give clients an IPv6 address to connect to when verifying.
When chutney is using IPv6 bridges, I don't know if it gives their IPv6 address to bridge clients.
This is a significant cover...Even when chutney is using IPv6 exits, it doesn't give clients an IPv6 address to connect to when verifying.
When chutney is using IPv6 bridges, I don't know if it gives their IPv6 address to bridge clients.
This is a significant coverage gap that I think is easily fixed by slight modifications to the chutney templating and verification code.https://gitlab.torproject.org/legacy/trac/-/issues/16806Chutney/integration tests for DNS server/client functionality2020-06-13T13:29:24ZNick MathewsonChutney/integration tests for DNS server/client functionality