Date: Tue, 13 May 2003 10:45:58 -0400
From: Chuck Ebbert <76306.1226@compuserve.com>
Subject: Re: The disappearing sys_call_table export.
To: Jesse Pollard <jesse@cats-chateau.net>, Yoav Weiss <ml-lkml@unpatched.org>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Message-ID: <200305131048_MC3-1-38B1-E13F@compuserve.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	 charset=us-ascii
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1112
Lines: 25

Jesse Pollard wrote:

> > However, it'll just give you false sense of security.  First of all, its
> > hardware dependent.  Second, it won't get wipe in case of a crash (which
> > is likely to happen when They come to take your disk).
>
> It is also not a valid wipe either.
> 
> This particular object reuse assumes the hardware is in a secured area. If it
> is in a secured area then you don't need to wipe it. It remains completely 
> under the systems control (even during a crash and reboot). The interval 
> between crash and reboot is covered by the requirement to be in a secured 
> area.

  ...until the admin walks in, shuts down the system, puts it on a cart
and hauls it out the door.  Is he going to wipe the swap area before he
does that?  Sure, you can write a procedure that says that's what he does
but he will not follow it (been there done that.)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/