FreeBSD Jails
BSD Forums writes "A common security breach involves exploiting one application to gain access to another. Keeping separate applications separate can limit the potential damage. OnLamp's Mike DeGraw-Bertsch explains how FreeBSD's jails can help secure necessary applications."
Instead of this adhoc-ish system, wouldn't a better solution be to have a "correct" sandbox in which a policy can be attached to ANY process, which determined what kernel calls can be made, and potentially with what parameters? Then there is no need for wacky interface aliasing and stuff like that.
It's 10 PM. Do you know if you're un-American?
For some fun jail patches have a look at garage.freebsd.pl
Rus
Cheap UK and US VPS
To quote the Makefile for /usr/ports/mail/qmail:
NO_PACKAGE= djb's packaging license does not allow non-standard qmail binary distributions
I would guess this is a big showstopper for using qmail in the FreeBSD basesystem. However, I think it was recently added some glue to sysinstall to let you choose MTA during install.
And better alternatives exist
In your opinion. Personally I dislike sendmail, but love BIND (just don't run it as root). But then I dislike qmail as much as sendmail, and djbdns strikes me as mildly braindamaged - so I'd hate to see them installed by default.
An ideal system would have the entire OS as packages... then all you need to do in to install your favourites....
Do you mind, your karma has just run over my dogma.
The main feature is a configuration that lets you act on jails by name. For instance:
will start those jails, andwill stop that instance. Basically, I wanted to make a system that was convenient for people with large numbers of jails on one machine, but easy enough for everyone.Included are an rc.d script for starting/stopping a set of jails at boot/shutdown, and an snmpd plugin for remote monitoring.
Dewey, what part of this looks like authorities should be involved?