Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: Privelege separation

Subject: Re: Privelege separation
Date: Tue, 24 Aug 2004 10:49:52 -0500
On Tue, 2004-08-24 at 16:57:25 +0200, Michel Arboi proclaimed...

Indeed. For FreeBSD, try jails (not as good as a OS MAC, but better
than nothing). For Solaris, buy Trusted Solaris. etc.

We have already talked about this privilege separation stuff, and
my opinion is that it does not really improve the security (whatever
this word means). 

Wow, uh. This comes from a security vendor? The whole idea behind
privsep is that the *least* amount of code runs as root. OpenBSD has
done it for tcpdump, syslogd, etc. So you open up a raw socket, then
for to a child who communicates through some fancy mechanism to
request further privilege-required capabilities. Perhaps this would
protect nessus itself from an overflow that might pop up in the
future; after all, no code is perfect.

Then again, it's your product! :-) and clearly it needs to be
protected by other mechanisms. I just wish, personally, that I could
put nessus on the network and not require 3-4 other layers of
defense in front of it.

Cheers,

- Eric
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>