From owner-freebsd-current Wed Nov 5 18:23:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA00950 for current-outgoing; Wed, 5 Nov 1997 18:23:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA00935 for ; Wed, 5 Nov 1997 18:23:44 -0800 (PST) (envelope-from nash@Venus.mcs.net) Received: from Venus.mcs.net (nash@Venus.mcs.net [192.160.127.92]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id UAA12212; Wed, 5 Nov 1997 20:23:43 -0600 (CST) Received: from localhost (nash@localhost) by Venus.mcs.net (8.8.7/8.8.2) with SMTP id UAA19556; Wed, 5 Nov 1997 20:23:42 -0600 (CST) Date: Wed, 5 Nov 1997 20:23:41 -0600 (CST) From: Alex Nash To: Matthew Thyer cc: freebsd-current@FreeBSD.ORG Subject: Re: [Fwd: Malicious Linux modules - be worried !] In-Reply-To: <34611335.8601A3B@dsto.defence.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 6 Nov 1997, Matthew Thyer wrote: > I assume FreeBSD LKMs could do this kind of thing too. FreeBSD disallows LKM loading when kern.securelevel > 0. Unfortunately, it's often not practical to run with securelevel set that way. Alex