3. It could default to strictly secure but accept a command-line
option to relax the constraints. And an rc.conf knob could be added
to control whether or not it was strict at boot time.
What do you folks think about this?
Following on the "tools, not policy" the 3rd option has support.
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
ph...@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message