Re: cryptoloop confusion [repost]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
holy cow, what was I thinking when I wrote this?
I hope the original post was understandable, but here is the corrected version
Sorry for the repost folks
Cheers
Pedro
On Wednesday 28 August 2002 00:44, Pedro Diaz Jimenez wrote:
> Hi,
>
> [Probably not related much to your problems, but you might find it
> interesting]
>
> If all you want is file system encryption you can try the loop-AES patch
> http://loop-aes.sourceforge.net/
>
> I used it for a long time on my laptop and it's been perfectly usable
> (stable, fast to some excent, no compilation problems when upgrading
kernels, etc..).
> It uses the AES cryptosystem, of proven strength . The
> compilation/instalation procedure is quite easy, also
>
> Cheers
> Pedro
>
> On Tuesday 27 August 2002 23:11, Jeff wrote:
> > I've decided to learn how to setup an encrypted filesystem using the
> > cryptoloop method and I'm having troubles getting my kernal source
> > patched correctly. I've read the "Loopback Encrypted Filesystem
> > HOWTO", but it's outdated. Here are a number of patches for kernel
> > 2.4.18 and I'm confused as to which one(s) to use.
> >
> > I've patched using patch-int-2.4.18.2.bz2 successfully, but my
> > compile fails at the cryptoloop part.
> >
> > I've tried using the "make patch-kernel ..." to patch with
> > cryptoloop-0.0.1-pre1.tar.gz and cryptoapi-0.1.0-rc1.tar.gz, both of
> > which failed:
> >
> > root # cd /usr/src/cryptoloop-0.0.1-pre1
> > root # make patch-kernel KDIR=/usr/src/linux-2.4.18_crypt
> > LOOP=iv
> > cp -pf /usr/src/linux-2.4.18_crypt/Rules.make .
> > rm -f arch/
> > ln -s /usr/src/linux-2.4.18_crypt/arch .
> > rm -f include/
> > ln -s /usr/src/linux-2.4.18_crypt/include .
> > make -f Makefile.modules KDIR=/usr/src/linux-2.4.18_crypt version
> > make[1]: Entering directory `/usr/src/cryptoloop-0.0.1-pre1'
> > make[1]: Leaving directory `/usr/src/cryptoloop-0.0.1-pre1'
> > cd patches && ./findpatch.pl /usr/src/linux-2.4.18_crypt iv
> > patching file linux-2.4.16/drivers/block/loop.c
> > patching file linux-2.4.16/include/linux/loop.h
> > cp: cannot stat
> > `/usr/src/linux-2.4.18_crypt/crypto/drivers/Config.in': No such file
> > or directory
> > /bin/sh: /usr/src/linux-2.4.18_crypt/crypto/drivers/Config.in: No such
> > file or directory
> > `cryptoloop.c' -> `/usr/src/linux-2.4.18_crypt/crypto/drivers'
> > cp: accessing `/usr/src/linux-2.4.18_crypt/crypto/drivers/Makefile':
> > Not a directory
> > make: *** [patch-kernel] Error 1
> >
> > and...
> >
> > root # cd /usr/src/cryptoapi-0.1.0-rc1
> > root # make patch-kernel KDIR=/usr/src/linux-2.4.18_crypt
> > LOOP=iv
> > cp -pf /usr/src/linux-2.4.18_crypt/Rules.make .
> > rm -f arch/
> > ln -s /usr/src/linux-2.4.18_crypt/arch .
> > rm -f include/
> > ln -s /usr/src/linux-2.4.18_crypt/include .
> > make -f Makefile.modules KDIR=/usr/src/linux-2.4.18_crypt version
> > make[1]: Entering directory `/usr/src/cryptoapi-0.1.0-rc1'
> > make[1]: Leaving directory `/usr/src/cryptoapi-0.1.0-rc1'
> > touch check.stamp
> > cp -R kernel/crypto /usr/src/linux-2.4.18_crypt
> > cp: cannot overwrite non-directory
> > `/usr/src/linux-2.4.18_crypt/crypto/drivers' with directory
> > `kernel/crypto/drivers'
> > make: *** [patch-kernel] Error 1
> >
> > I'm googling and looking at all the docs in the patches, but I'm not
> > finding clear answers yet.
> >
> > If someone can shed some light on which patch(es) I need and the order
> > I need to apply them, and any other important pieces I'd really
> > appreciate it.
> >
> > thanks,
> > jc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9bAp0nu53feEYxlERAhSPAJ9iFr4U3kqb6v0kxXqXkWx32cmJtQCguFy5
gaqnLHehw9wBADz486apFxQ=
=Mu5m
-----END PGP SIGNATURE-----
Reply to: