FORTIFY_SOURCE feature of libssp, thus checking the size of arguments to
various string and memory copy and set functions (as well as a few system
calls and other miscellany) where known at function entry. RedHat has
evidently built all "core system packages" with this option for some time.
This option should be used at the top of Makefiles (or Makefile.inc where
this is used for subdirectories) but after any setting of LIB.
This is only useful for userland code, and cannot be used in libc or in
any code which includes the libc internals, because it overrides certain
libc functions with macros. Some effort has been made to make USE_FORT=yes
work correctly for a full-system build by having the bsd.sys.mk logic
disable the feature where it should not be used (libc, libssp iteself,
the kernel) but no attempt has been made to build the entire system with
USE_FORT and doing so will doubtless expose numerous bugs and misfeatures.
Adjust the system build so that all programs and libraries that are setuid,
directly handle network data (including serial comm data), perform
authentication, or appear likely to have (or have a history of having)
data-driven bugs (e.g. file(1)) are built with USE_FORT=yes by default,
with the exception of libc, which cannot use USE_FORT and thus uses
only USE_SSP by default. Tested on i386 with no ill results; USE_FORT=no
per-directory or in a system build will disable if desired.
- delint (void casts, shadow warning on port)
- always cast to unsigned char for isfoo() macros, not sometimes.
- save errno to avoid reporting random error value.
- use warnx() when the error is indeed unknown.
- use getprogname() instead of __progname.
- make all locals static.
with one that is KNF, has ipv6, better error
handling, and recursion. I settled on OpenBSDs.
Christos found some nits and had me commit as
is. Christos will follow up with fixes shortly.
whois.networksolutions.com is just wrong -- it only returns information
for Network Solutions domains.
whois.opensrs.net is a bit better -- it returns information for OpenSRS
domains, and otherwise recurses to the correct whois server for other
domains -- unfortunately it is not canonical, and cannot be construed as
"correct." Other recursing proxies include whois.geektools.com and pallas.
eruditorum.org, neither of which is "official" either.
For good or for ill, we go back to whois.internic.net, which is the canonical
source for this information.
whois.opensrs.net, which does internal recursion for domain data.
Network Solutions' server recurses on only _some_ registries, and has the
damned disclaimer and advertising on no-match results.
the WHOIS service, again. New target: whois.networksolutions.com
This program should be replaced with one that does WHOIS++ so that it
can hit all the registries for data.
ws