From owner-freebsd-security Thu May 21 10:28:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17357 for freebsd-security-outgoing; Thu, 21 May 1998 10:28:16 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17341 for ; Thu, 21 May 1998 10:28:11 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id NAA29451; Thu, 21 May 1998 13:28:05 -0400 (EDT) (envelope-from wollman) Date: Thu, 21 May 1998 13:28:05 -0400 (EDT) From: Garrett Wollman Message-Id: <199805211728.NAA29451@khavrinen.lcs.mit.edu> To: Keith Stevenson Cc: freebsd-security@FreeBSD.ORG Subject: LKMs (Was: Virus on FreeBSD) In-Reply-To: <19980521111653.A9283@homer.louisville.edu> References: <199805210018.RAA04596@passer.osg.gov.bc.ca> <199805210149.LAA25157@frenzy.ct> <199805211431.KAA17444@brain.zeus.leitch.com> <19980521111653.A9283@homer.louisville.edu> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk < said: > Ok, I'll buy off on the idea that LKMs can be bad from a security standpoint. > How does one go about removing that functionality from the system? In the case of FreeBSD, set the security level to 2. The functionality isn't removed -- we don't provide for that -- but it is inaccessible. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message