right now. new address-of-packed-member and format-overflow
warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd
GCC_NO_FORMAT_OVERFLOW variables to remove these warnings.
apply to a bunch of the tree. mostly, these are real bugs that
should be fixed, but in many cases, only by removing the 'packed'
attribute from some structure that doesn't really need it. (i
looked at many different ones, and while perhaps 60-80% were
already properly aligned, it wasn't clear to me that the uses
were always coming from sane data vs network alignment, so it
doesn't seem safe to remove packed without careful research for
each affect struct.) clang already warned (and was not erroring)
for many of these cases, but gcc picked up dozens more.
new upstream version of traceroute to import.
AS# lookup is still done using host networking. Rationale: the
relevance to where that data comes from with respect to network
tracing is zero (be it socket, local file, db, whatever).
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.
Example:
RC02-02 (195.245.142.66) 45.707 ms 20.418 ms 34.042 ms [MPLS: label: 515, exp: 0x0, ttl: 1]
gr1-p340.attga.ip.att.net (12.123.20.190) 241.878 ms 251.945 ms [MPLS: label: 32133, exp: 0x0, ttl: 1]
Based on PR 22523: By Jesper Skriver (updated by ww@parc.styx.org and Mihai
CHELARU).
Things not in the PR that I changed/added:
* changed exp and label to lower case
* added ttl (probably not worth it but who knows..)
* KNF/style/indent
* C99 uintXX_t
4.4bsd->4.4BSD
PR misc/20747 from Igor Sobrado
Note he also asked for NSFNet -> NSFNET which I didn't do -- it seems
arbitrary and unneeded.
XXX Patch submitted back to traceroute@ee.lbl.gov -- are they still active?
XXX Should this be converted to mdoc?
roy