GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8)
GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8)
GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8)
GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8)
use these to turn off warnings for most GCC-8 complaints. many
of these are false positives, most of the real bugs are already
commited, or are yet to come.
we plan to introduce versions of (some?) of these that use the
"-Wno-error=" form, which still displays the warnings but does
not make it an error, and all of the above will be re-considered
as either being "fix me" (warning still displayed) or "warning
is wrong."
(ours is patched to not do this) leave in utmp. PR 26168.
I'm doing this by testing for ^:[0-9] in the line field of utmp(x),
rather than by attempting to stat the device name corresponding to the
entry as in Martin's patch, because (1) no valid tty should ever have
a name beginning with a colon, and (2) this way we don't silently skip
over real ttys that should be there but for some reason have disappeared.
(I suppose this might conceivably fail to catch entries for displays
connected via XDCMP; however, ~nobody does that any more and XDCMP is
a security hole anyhow. If anyone's really concerned about this, let
me know.)
In the long run we should look into ways of getting "tty" messages to
users logged in with an X session and no terminal windows open, as
that's probably fairly common for the desktop.
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.
This option may be specified multiple times, and any user in any of the
specified groups will receive the message.
(From OpenBSD, with tweaks from FreeBSD fed back into OpenBSD).
* Ensure that paths are MAXPATHLEN. (From OpenBSD)
* Display timezone when printing time. (From FreeBSD PR 17867 via wall.c 1.14)
mrg