summaryrefslogtreecommitdiff
path: root/changes/bug21280
diff options
context:
space:
mode:
authorjunglefowl <junglefowl@riseup.net>2017-01-24 18:40:01 +0000
committerNick Mathewson <nickm@torproject.org>2017-02-07 09:27:00 -0500
commitc4920a60c6af935cc347fe3436dd7ff62a9e380d (patch)
tree633c12bb5af5e44e6e2f388901152323fdbc184e /changes/bug21280
parent9379984128365487d732a89a851a1132b8edbfa0 (diff)
downloadtor-c4920a60c6af935cc347fe3436dd7ff62a9e380d.tar.gz
tor-c4920a60c6af935cc347fe3436dd7ff62a9e380d.zip
Do not truncate too long hostnames
If a hostname is supplied to tor-resolve which is too long, it will be silently truncated, resulting in a different hostname lookup: $ tor-resolve $(python -c 'print("google.com" + "m" * 256)') If tor-resolve uses SOCKS5, the length is stored in an unsigned char, which overflows in this case and leads to the hostname "google.com". As this one is a valid hostname, it returns an address instead of giving an error due to the invalid supplied hostname.
Diffstat (limited to 'changes/bug21280')
0 files changed, 0 insertions, 0 deletions