Date: Fri, 17 Sep 1999 17:16:56 -0500 From: "Matthew D. Fuller" <fullermd@futuresouth.com> To: Brett Glass <brett@lariat.org> Cc: security@FreeBSD.ORG Subject: Re: Securing a system that's been rooted remotely (Was: BPF on in 3.3-RC GENERIC kernel) Message-ID: <19990917171656.H4975@futuresouth.com> In-Reply-To: <4.2.0.58.19990917155850.047bd680@localhost>; from Brett Glass on Fri, Sep 17, 1999 at 04:00:14PM -0600 References: <4.2.0.58.19990916232349.047c27a0@localhost> <4.2.0.58.19990916185341.00aaf100@localhost> <Pine.SOL.3.96L.990916210821.19993A-100000@unix8.andrew.cmu <4.2.0.58.19990916232349.047c27a0@localhost> <19990917134343.P16305@futuresouth.com> <4.2.0.58.19990917155850.047bd680@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 17, 1999 at 04:00:14PM -0600, a little birdie told me that Brett Glass remarked > > If securelevel isn't set high, a hacker can switch you BACK to the generic > kernel with a few keystrokes. You missed my main thrust. Why would you go to all the trouble to enable securelevels (usefully. read; flagging everyone and their mother), and still be running GENERIC? If you're not running GENERIC, you're running a custom kernel. If you're running a custom kernel, you're customizing stuff anyway, so you can take out/put in bpf or whatever you want. Where's the problem? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990917171656.H4975>