src/release/sysinstall/config.c, branch main

Sysinstall has been repocopied to src/usr.sbin/sysinstall and everything

2001-01-17T07:14:45+00:00

now uses the sources found there.

Replace GNOME + Afterstep choice with GNOME + sawfish. This is a more

2000-11-14T00:03:52+00:00

popular configuration now.

For High security profile, set securelevel to 1 to protect /dev/*mem

2000-11-07T23:05:14+00:00

and mounted disks, among other things.

Requested by:	kirk

Add another security configuration profile, call it "high" and

2000-10-14T21:02:31+00:00

rename the previous one to indicate that it's not just high, it's
extreme (everything off, secure level raised).

Submitted mostly by:	Tony Finch

PR: 21729

2000-10-05T23:27:32+00:00

Approved by:	jkh

Write kern_securelevel_enable variable to rc.conf if user selects
medium or low security in sysinstall.  This overrides the case where a
user selects fascist security and then tries to go back to a lower
setting.

One small tweak on the security profile code; don't be verbose if

2000-09-24T06:44:00+00:00

setting up default values for an express/custom install.  It would
be confusing to see the informational popup completely out of context.

One whack at the idea of having "security profiles" which select the

2000-09-22T19:12:41+00:00

appropriate(?) defaults for "low", "medium" and "high" security
environments.  Medium is basically what we currently have with a little
seat-belt tightening where it made sense.  Low is the same as medium but
without the tightening.  High is positively fascist with nothing turned
on by default and an automatic call to 911 if it can find a modem.

enable sshd by default. This only effects new installs, so

2000-09-04T15:50:15+00:00

upgraders will not receive any unpleasant surprises.

Remove a stray backspace character.

2000-08-27T18:49:12+00:00

Reviewed by:	Eivind Eklund

Change the defaults for portmap, sendmail and inetd to be not running them.

2000-07-28T22:45:36+00:00

Make sysinstall override this on install, so the effective behavioural
change for a newly installed system is null.  Overall, this makes a system
with an empty /etc/rc.conf not run any network services, and makes the
FreeBSD-provided network services that are running visible in /etc/rc.conf
(instead of making people look through /etc/defaults/rc.conf to find the
things they need to disable to secure the system.)

Reviewed by:	jhb
Discussed with:	The usual cabal