-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Oct 06, 2001 at 12:23:04PM -0400, David Kramer wrote:
> On Sat, 6 Oct 2001, Derek D. Martin wrote:
> 
> > keys I posess.  I also keep my home directory on all systems which
> > might contain sensitive data on an encrypted partition.  I feel
> 
> What do you use for that?

I formerly used the Linux international crypto API patches, found at
www.kerneli.org (the i after kernel is NOT a type-o).  These patches
had some problems in that they require modification to the kernel, and
there weren't patches that worked with all kernel releases.  The
maintainers didn't release often enough for my tastes...

I now use this:

  http://sourceforge.net/projects/loop-aes/

This project exists solely for disk encryption, whereas the crypto API
stuff was intended to be more broad in purpose.  It works with any
kernel and eliminates some of the other limitations of the old crypto
API.  The basic process for creating encrypted disks is basically the
same.  I'll admit that when I first used the crypto API to encrypt a
partition, I had to re-read the docs several times to figure out how
to get it all working...  I think it's not for people who are
squeamish about such things as compiling kernels and risking data
loss...  :)

There's also a new version of the crypto API on sourceforge, here:

  http://sourceforge.net/projects/cryptoapi/

If I get bored enough, I could probably whip up a quick how-to which
might explain what to do a bit better than the docs.  IIRC the docs
that come with loop-AES were a bit better... YMMV.


- -- 
- ---------------------------------------------------
Derek Martin          |   Unix/Linux geek
ddm@pizzashack.org    |   GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7wIgldjdlQoHP510RAslsAKCOM6TZDkUspcKy1eG52+71uaEjDACghCx/
XNOwjkq3IgSeGtPHsrDiO2A=
=QCLc
-----END PGP SIGNATURE-----
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request@blu.org (Subject line is ignored).