Files
tor/changes
liberat 4e4c4e72d7 Handle binary IPv6 addresses and bracketed strings in RESOLVE_PTR.
When a SOCKS5 client sends a RESOLVE_PTR request, it must include
either an IPv4 or IPv6 address.  In the past this was required to be a
binary address (address types 1 or 4), but since the refactoring of
SOCKS5 support in Tor 0.3.5.1-alpha, strings (address type 3) are also
allowed if they represent an IPv4 or IPv6 literal.

However, when a binary IPv6 address is provided,
parse_socks5_client_request converts it into a string enclosed in
brackets.  This doesn't match what string_is_valid_ipv6_address
expects, so this would fail with the error "socks5 received
RESOLVE_PTR command with hostname type. Rejecting."

By replacing string_is_valid_ipv4_address/string_is_valid_ipv6_address
with tor_addr_parse, we accept strings both with and without brackets.
This fixes the handling of binary addresses, and also improves
symmetry with CONNECT and RESOLVE requests.

Fixes bug 32315.
2019-11-11 15:34:38 +00:00
..
2018-09-15 23:19:31 +00:00
2018-08-18 19:23:28 +00:00
2018-10-30 10:49:03 -04:00
2018-11-06 15:17:19 -05:00
2018-11-12 15:39:28 -05:00
2018-11-14 07:51:36 -05:00
2018-11-19 15:48:08 -06:00
2018-12-17 10:57:47 -05:00
2019-01-09 08:52:05 -05:00
2019-01-16 14:40:31 -05:00
2019-02-08 08:37:23 -05:00
2019-01-22 12:27:46 -05:00
2019-02-19 11:38:32 -05:00
2019-05-31 12:39:52 -04:00
2019-04-10 12:46:27 +03:00
2019-04-09 12:05:33 -04:00
2019-05-14 19:19:53 -04:00
2019-08-22 22:09:32 +10:00
2019-06-12 08:55:38 -04:00
2019-03-26 12:24:45 +10:00
2018-10-29 15:18:07 -04:00
2018-10-30 11:28:53 -04:00
2018-12-01 11:18:03 -05:00
2019-06-28 21:38:33 +10:00
2019-02-08 08:52:46 -05:00
2019-02-08 10:43:38 -05:00
2019-04-01 14:08:24 +10:00
2019-04-12 08:38:30 -04:00
2019-04-30 09:15:35 +03:00
2019-05-20 08:56:34 -04:00
2019-08-15 08:20:47 -04:00
2019-10-20 22:04:08 +10:00