lkml.org 
[lkml]   [2003]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: The disappearing sys_call_table export.
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/

\
 
 \ /
  Last update: 2005-03-22 13:35    [W:0.027 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site