From: Ben Ford <ben@kalifornia.com>
To: David Wagner <daw@mozart.cs.berkeley.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: summary Re: encrypted swap
Date: Tue, 07 Aug 2001 20:30:09 -0700 [thread overview]
Message-ID: <3B70B241.40908@kalifornia.com> (raw)
In-Reply-To: <fa.g4fleqv.1mle133@ifi.uio.no> <Pine.GSO.4.31.0108071419300.2838-100000@cardinal0.Stanford.EDU> <9kq1v4$ku7$1@abraham.cs.berkeley.edu>
David Wagner wrote:
>You missed some scenarios. Suppose I run a server that uses crypto.
>If swap is unencrypted, all the session keys for the past year might
>be laying around on swap. If swap is encrypted, only the session keys
>since the last boot are accessible, at most. Therefore, using encrypted
>swap clearly reduces the impact of a compromise of your machine (whether
>through theft or through penetration). This is a good property.
>
Wiping swap on boot will achieve the same effect.
-b
--
Please note - If you do not have the same beliefs as we do, you are
going to burn in Hell forever.
next prev parent reply other threads:[~2001-08-08 3:33 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 [this message]
2001-08-08 2:59 ` David Lang
2001-08-08 7:05 ` David Ford
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=3B70B241.40908@kalifornia.com \
--to=ben@kalifornia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox