| Age | Commit message (Collapse) | Author |
|---|
|
|
|
test 154
|
|
|
|
|
|
option instead of just assuming it is present.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
more involved, but should hopefully not generate any compiler warnings on
win32 systems (that can't check the socket based on the numeric).
|
|
is no longer only present when built with SSL support.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
style build
|
|
|
|
on a host with a buggy resolver that strips all but the bottom 8 bits of
each octet. The resolved address in this case (192.0.2.127) is guaranteed
never to belong to a real host (see RFC3330).
|
|
|
|
|
|
|
|
|
|
the default options set in the Makefile
|
|
between platforms
|
|
these days...!
|
|
|
|
|
|
|
|
|
|
options used by runtests.pl during testing (useful for disabling valgrind).
|
|
|
|
scripts use the version in packages/vms/
|
|
|
|
server
|
|
inet_addr() functions seems to use &255 on all numericals in a ipv4 dotted
address which makes a different failure... Now I've modified the ipv4
resolve code to use inet_pton() instead in an attempt to make these systems
better detect this as a bad IP address rather than creating a toally bogus
address that is then passed on and used.
|
|
|
|
|
|
but using illegal values
|
|
|
|
|
|
|
|
never executed code when -Wunreachable-code is used
|
