From: David Ford <david@blue-labs.org>
To: David Lang <david.lang@digitalinsight.com>
Cc: Ben Ford <ben@kalifornia.com>,
David Wagner <daw@mozart.cs.berkeley.edu>,
linux-kernel@vger.kernel.org
Subject: Re: summary Re: encrypted swap
Date: Wed, 08 Aug 2001 03:05:44 -0400 [thread overview]
Message-ID: <3B70E4C8.2020400@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0108071957170.3450-100000@dlang.diginsite.com>
You can't guarantee much if the machine is physically compromised. In
the situation of wiping, you probably won't need swap immediately after
boot so you can afford to execute a script that wipes the file/partition
then mounts it.
It's all easily accomplished in userspace.
David
David Lang wrote:
>only if you can guarenty that there is no way to avoid wiping it even if
>this is the 2nd (or 3rd) hard drive (and what about how swap drives that
>get added to a system after boot)
>
>also this had better be a configuration option. I don't want to wait for
>2g of swap space to be wiped when I boot by webserver (which defeates my
>previous requirement)
>
>David Lang
>
next prev parent reply other threads:[~2001-08-08 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.g4fleqv.1mle133@ifi.uio.no>
2001-08-07 21:34 ` summary Re: encrypted swap Ted Unangst
2001-08-07 21:39 ` David Spreen
2001-08-08 0:43 ` David Wagner
2001-08-08 3:30 ` Ben Ford
2001-08-08 2:59 ` David Lang
2001-08-08 7:05 ` David Ford [this message]
2001-08-08 22:34 ` Marty Poulin
2001-08-09 4:56 ` David Ford
2001-08-09 5:02 ` David Wagner
2001-08-09 15:29 ` Andreas Dilger
2001-08-09 20:31 ` EOT " Rik van Riel
2001-08-09 0:19 ` David Wagner
2001-08-08 4:58 ` David Wagner
[not found] <fa.fk6d0vv.vgmm1i@ifi.uio.no>
2001-08-08 5:37 ` Ted Unangst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B70E4C8.2020400@blue-labs.org \
--to=david@blue-labs.org \
--cc=ben@kalifornia.com \
--cc=david.lang@digitalinsight.com \
--cc=daw@mozart.cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.