tor_inet_pton(...) ipv6 addr. parsing inconsistencies
Currently: * "0x10::" is a valid addr according to tor_inet_pton but not according to inet_pton. * ":" is a seg fault waiting to happen. (src[1] <- out of bound) * "000010::" is an invalid addr according to tor_inet_pton but not according to inet_pton. I suggest changing tor_inet_pton to make it consistent with inet_pton (as the doc states it should be). I'll update the ticket with a patch in a moment. **Trac**: **Username**: 4ZM
issue