Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:35:45Zhttps://gitlab.torproject.org/legacy/trac/-/issues/11603Tor DNS resolver returns A record for AAAA query2020-06-13T14:35:45ZTracTor DNS resolver returns A record for AAAA queryMy normal system resolver:
mike@glue:~$ dig +short aaaa gmail.com @localhost
2a00:1450:4009:803::1015
mike@glue:~$
The Tor DNS resolver running on port 5304:
mike@glue:~$ dig +short aaaa gmail.com @localhost -p 5304
173.194.65.18
mik...My normal system resolver:
mike@glue:~$ dig +short aaaa gmail.com @localhost
2a00:1450:4009:803::1015
mike@glue:~$
The Tor DNS resolver running on port 5304:
mike@glue:~$ dig +short aaaa gmail.com @localhost -p 5304
173.194.65.18
mike@glue:~$
**Trac**:
**Username**: mickeycTor: 0.2.5.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/5847Better error message on GETINFO desc/* when you only have MDs.2020-06-13T14:19:34ZTracBetter error message on GETINFO desc/* when you only have MDs.The "GETINFO desc/id/OR identity" and "GETINFO desc/name/OR nick" options don't seem to work on the Tor control port:
GETINFO desc/id/DD397148A4AB4D43E5E6CB9C5F45E922872CC2D3
552 Unrecognized key "desc/id/DD397148A4AB4D43E5E6CB9C5F45E92...The "GETINFO desc/id/OR identity" and "GETINFO desc/name/OR nick" options don't seem to work on the Tor control port:
GETINFO desc/id/DD397148A4AB4D43E5E6CB9C5F45E922872CC2D3
552 Unrecognized key "desc/id/DD397148A4AB4D43E5E6CB9C5F45E922872CC2D3"
If I replace "desc" with "md" I get the expected response, and they're both described in the spec as taking the same arguments...
**Trac**:
**Username**: mickeycTor: 0.3.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/5796Crashing Tor with SETCIRCUITPURPOSE2020-06-13T14:19:28ZTracCrashing Tor with SETCIRCUITPURPOSEI seem to be able to consistently crash Tor, with nothing being added to the log file by doing the following:
alfa:~# telnet localhost 9051
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
AUTHENTICATE **********
25...I seem to be able to consistently crash Tor, with nothing being added to the log file by doing the following:
alfa:~# telnet localhost 9051
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
AUTHENTICATE **********
250 OK
EXTENDCIRCUIT 0
250 EXTENDED 24
SETCIRCUITPURPOSE 24 general
Connection closed by foreign host.
alfa:~# telnet localhost 9051
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
alfa:~#
**Trac**:
**Username**: mickeycTor: 0.2.2.x-finalAaron GibsonAaron Gibsonhttps://gitlab.torproject.org/legacy/trac/-/issues/5723ADDRMAP reversed IP bug2020-06-13T14:19:22ZTracADDRMAP reversed IP bugIn the following control port debug log you'll see I look up the IP address of "grepular.com" three times in a row. Look how the octets of the IP address in the ADDRMAP responses are reversed in the second and third responses:
```
mike@...In the following control port debug log you'll see I look up the IP address of "grepular.com" three times in a row. Look how the octets of the IP address in the ADDRMAP responses are reversed in the second and third responses:
```
mike@alfa:~$ telnet localhost 9051
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
AUTHENTICATE XXXXX
250 OK
SETEVENTS addrmap
250 OK
RESOLVE grepular.com
250 OK
650 ADDRMAP grepular.com 178.79.145.246 "2012-05-01 01:21:07" EXPIRES="2012-05-01 00:21:07"
RESOLVE grepular.com
650 ADDRMAP grepular.com 246.145.79.178 "2012-05-01 01:21:07" EXPIRES="2012-05-01 00:21:07"
250 OK
RESOLVE grepular.com
650 ADDRMAP grepular.com 246.145.79.178 "2012-05-01 01:21:07" EXPIRES="2012-05-01 00:21:07"
250 OK
```
If I disconnect and reconnect, they're reversed from the very first response. If I restart Tor and try again, then the first response is correct, but the subsequent responses are all reversed again. This happens for any domain I test. The "tor-resolve" command doesn't display this problem. I'm running version "0.2.3.14-alpha"
**Trac**:
**Username**: mickeycTor: 0.2.3.x-finalNick MathewsonNick Mathewson