From owner-freebsd-current  Wed Nov  5 18:35:41 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA01659
          for current-outgoing; Wed, 5 Nov 1997 18:35:41 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA01649
          for <freebsd-current@FreeBSD.ORG>; Wed, 5 Nov 1997 18:35:25 -0800 (PST)
          (envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id VAA22035;
	Wed, 5 Nov 1997 21:35:09 -0500 (EST)
Date: Wed, 5 Nov 1997 21:35:09 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199711060235.VAA22035@khavrinen.lcs.mit.edu>
To: Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au>
Cc: freebsd-current@FreeBSD.ORG
Subject: [Fwd: Malicious Linux modules - be worried !]
In-Reply-To: <34611335.8601A3B@dsto.defence.gov.au>
References: <34611335.8601A3B@dsto.defence.gov.au>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

<<On Thu, 06 Nov 1997 11:15:41 +1030, Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au> said:

> I assume FreeBSD LKMs could do this kind of thing too.

Indeed.  That's why LKM ``write'' access is disabled when running in
secure mode.  Always run important machines in secure mode.

-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