Move all runtime options into a structure that is made read-only
(via mprotect) after initialisation to protect against attacks that
overwrite options to turn off malloc protections (e.g. use-after-free)
Allocate the main bookkeeping data (struct dir_info) using mmap(),
thereby giving it an unpredictable address. Place a PROT_NONE guard
page on either side to further frustrate attacks on it.
Add a new 'L' option that maps struct dir_info PROT_NONE except when
in the allocator code itself. Makes attacks on it basically impossible.
feedback tedu deraadt otto canacar
ok otto

as static const

SSH2-RSA size; ok hshoexer@, no objection from miod@

to start the for loop and not 1 which was correct long long time ago.
OK otto@ found by Anirban Sinha ASinha(at)zeugmasystems.com

Add nonblock support for xdrrecs
ok millert blambert & otto; from NetBSD. libc bump to follow soon.

Caught by pcc.
OK martynas

instead of just 1.
ok todd@

pointed out by jmc@

spotted by rainer@, ok uwe@

discussed with and ok uwe@

ok fries, hshoexer, claudio

the page as possible (i.e. make malloc option P a default).
ok art@ millert@ krw@

a page to 0. P default will be changed in a separate commit.
ok millert@ art@ krw@

a separate symbolic constant for the leeway we allow when moving
allocations towards the end of a page. No functional change.

to some stupid ipv6 bug in particular), remove that 'listen' from the list
and continue operation.  issue spotted by naddy
ok henning

(might catch errors closer to the trouble spot) and junk fill pages just
before reuse instead of immediate (we can't access the page anyway)
since we set PROT_NONE in the F case. ok djm@

ok jmc@

tried and how many actually succeeded.

requested by many, "just go for it" deraadt@

but that is OK because both minor 3 and 4 now do the same thing.  eventually,
2 releases from now, everyone will have forgotten about minor 4 and we can
delete the support code for it from sys/dev/rnd.c
various versions of this looked at by millert and todd

which only works in w.europe
- use a more realistic value for udcf correction example
- use a GPS-only receiver for "refid GPS" example
suggested/ok mbalmer

threaded case) but much smaller working set; prompted by and ok deraadt@

non-syscalls, there's just too much code not doing the right thing on
error paths; prompted by and ok deraadt@

kurt@

mapping the region next to the existing one first; there's a pretty
high chance there's a hole there we can use; ok deraadt@ tedu@

too much pressure on the amaps. ok tedu@ deraadt@

spamd-setup hanging if there are various (network?) issues and the system
not proceeding to multiuser so that this can be debugged.  We do not use
& for startup in /etc/rc because this makes the spamd-setup a child of the
rc scripts after bootup (that is gross)
Problem reported in PR 5864, change discussed with beck, ok millert

that should expect to read the manual anyway and it's caused some
confusion in the past.
Add example entries for fixed-address and pxeboot.
ok krw@

the offset since we use monotime for these for some time now, and monotime
is not affected by system time changes (like, duh, that was the reason for
the change). PR5927