[tor-bugs] #17846 [Tor]: 32bit decimal IP address fail (i.e. no octets) on nbsd and obsd

[Tor Bug Tracker & Wiki]

#17846: 32bit decimal IP address fail (i.e. no octets) on nbsd and obsd
----------------------+-------------------------------
 Reporter:  amonk     |          Owner:
     Type:  defect    |         Status:  new
 Priority:  Very Low  |      Milestone:
Component:  Tor       |        Version:  Tor: 0.2.6.10
 Severity:  Minor     |     Resolution:
 Keywords:  lorax     |  Actual Points:
Parent ID:            |         Points:
  Sponsor:            |
----------------------+-------------------------------
Changes (by yawning):

 * keywords:   => lorax


Comment:

 The issue isn't in `tor_addr_parse()`, which is backed by a correctly
 implemented `inet_pton()` implementation.  `tor_addr_lookup()` first tries
 to `inet_pton()` the address as `AF_INET` and `AF_INET6`, and falls back
 to `getaddrinfo()` on systems that support it.

 NetBSD (and I assume OpenBSD) both have a `getaddrinfo()` based entirely
 around `inet_pton()`, with code that would make this work `#if 0`-ed out.

 http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/net/getaddrinfo.c?rev=1.112
 &content-type=text/x-cvsweb-markup&only_with_tag=MAIN

 So IMO it's a Net/OpenBSD libc bug, assuming you think they should provide
 a standards compliant `getaddrinfo()` (IEEE Std 1003.1, 2013 Edition
 mandates the X/Open behavior).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17846#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online