user librumpres

Include several libc functions in rump.ping6

We need getaddrinfo, getifaddrs, if_indextoname and if_nametoindex
in addition to getnameinfo.

Introduce rump.ping6

We use ping6 frequently in ATF tests so let's have rump-ified one.

fix gcc warnings and eliminate duplicate code.

apply some -Wno-error and/or -fno-strict-aliasing.


all of this should be looked at closer, but some of them are not
very trivial.

Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on the
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.

Remove support support for RFC 2292.

Add support for RFC 3542 Adv. Socket API for IPv6 (which obsoletes 2292).
* RFC 3542 isn't binary compatible with RFC 2292.
* RFC 2292 support is on by default but can be disabled.
* update ping6, telnet and traceroute6 to the new API.

From the KAME project (www.kame.net).
Reviewed by core.

Move WARNS=3 to the Makefile.inc, and add a little const to the remaining
programs that did not compile before.

Kill __P(), use ANSI function declarations; WARNS=3.

no need for KAME_SCOPEID

repair fd_set size attack. from deraadt.
some of cleanups from kame (inet_ntop error check, unnecessary headers,
stddev computation like ping(8)).
$NetBSD$.

branches: 1.5.4;
provide -S for source address specifier.
enable KAME scopeid hack.
cleanups in node information query.
(sync with latest KAME)

branches: 1.4.4;
do not modify BINGRP as there's no reason for.

From: tsubai@netbsd.org

-D... belongs in CPPFLAGS

enable -DIPSEC.

ping for IPv6. try
ping6 ::1
on you node.