[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-patch problem statement (update)

To: Marc Mutz <Marc.Mutz@uni-bielefeld.de>
Subject: Re: I-patch problem statement (update)
From: Jari Ruusu <jari.ruusu@pp.inet.fi>
Date: Thu, 06 Sep 2001 14:51:35 +0300
CC: Herbert Valerio Riedel <hvr@hvrlab.org>, linux-crypto@nl.linux.org
References: <Pine.LNX.4.33.0109060853050.16159-100000@janus.txd.hvrlab.org> <0GJ80028MHDKM1@mail.uni-bielefeld.de>
Sender: owner-linux-crypto@nl.linux.org

Marc Mutz wrote:
> On Thursday 06 September 2001 09:10, Herbert Valerio Riedel wrote:
> > another subsystem; virtual memory encryption, can make use of the
> > cryptoapi as well...
> 
> - - encrypted swap, which would be really nice, esp. since it requires no
> key management (you just grab a random number from the kernel's entropy
> pool on each swapon)

HVR is still playing catch-up as loop-AES-v1.4d does encrypted swap already.

Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>


Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/

Follow-Ups:
- Re: I-patch problem statement (update)
  - From: Marc Mutz <Marc.Mutz@uni-bielefeld.de>

References:
- Re: I-patch problem statement (update)
  - From: Herbert Valerio Riedel <hvr@hvrlab.org>
- Re: I-patch problem statement (update)
  - From: Marc Mutz <Marc.Mutz@uni-bielefeld.de>

Prev by Date: Re: I-patch problem statement (update)
Next by Date: Why no mainline kernel crypto? (was: Re: I-patch problem statement(update))
Prev by thread: Re: I-patch problem statement (update)
Next by thread: Re: I-patch problem statement (update)
Index(es):
- Date
- Thread