From: bert hubert <ahu@ds9a.nl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, christophe@saout.de
Subject: dmcrypt works well on 2.6.3 WAS: Re: 2.6.3-mm1
Date: Wed, 18 Feb 2004 13:14:16 +0100 [thread overview]
Message-ID: <20040218121416.GA13364@outpost.ds9a.nl> (raw)
In-Reply-To: <20040217232130.61667965.akpm@osdl.org>
> People need to test and use this please. There is documentation at
> http://www.saout.de/misc/dm-crypt/.
Works amazingly well. Starting from stock 2.6.3 I applied 'dm*' from the
broken out 2.6.3-mm1, no fuzz or offset, and ran make on the kernel I had
built this morning.
I then turned on the device mapper and its crypto support and loaded the
modules, without rebooting.
Downloaded ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz
./configure && make && sudo make install
sudo ./scripts/devmap_mknod.sh (to create /dev/mapper)
Downloaded http://www.stwing.org/~sluskyb/util-linux/hashalot-0.2.0.tar.gz
./configure && make && sudo make install
Downloaded http://www.saout.de/misc/cryptsetup
ran: cryptsetup -h plain create crypted /dev/hdb1
(the -h plain isn't necessary, I didn't have hashalot
earlier, and even with -h plain it wants hashalot)
entered a passphrase (already forgotten though)
e2fsck /dev/mapper/crypted
mount /dev/mapper/crypted /mnt
mke2fs proved to be a significant CPU load (all sy) and took a minute or two
to run, which could be forgiven, it had to mke2fs 200G.
I then copied the entire Linux build tree to /mnt, ran make clean, make, and
12 minutes later I had a new kernel. System load was below <10% at all
times, mostly <5%.
Then I did the whole thing again but then with ext3, which worked too. System
load appeared slightly higher, the build however took 12 minutes as well.
Kudos!
Suggestions
-----------
1) Add a reference to the hashalot location to
http://www.saout.de/misc/dm-crypt/ and add some units to 'cryptsetup',
something like this (probably tab/space damaged):
--- cryptsetup 2003-12-26 21:27:08.000000000 +0100
+++ cryptsetup.ahu 2004-02-18 12:46:18.000000000 +0100
@@ -229,10 +229,10 @@
gettable "$NAME"
echo "$DMPATH$NAME is active:"
echo " cipher: $CIPHER"
- echo " keysize: $[${#KEY}/2]"
+ echo " keysize: $[${#KEY}/2] bytes"
echo " device: $DEVICE"
echo " offset: $SKIPPED"
- echo " size: $SIZE"
+ echo " size: $SIZE sectors"
[ $SKIPPED -gt 0 ] && echo " skipped: $SKIPPED"
unset KEY
else
The output can be mighty confusing otherwise.
2) Remove dependence on hashalot for -h plain
3) Add pointer to hashalot on the main page
4) make make install of the device mapper userspace run the mknod script
> filesystems. ie: ext3 on cryptoloop will no longer be crash-proof.
(...)
> After that we should remove cryptoloop altogether.
Big fat warnings might be wise in the meantime. I sincerely hope that
dm-crypt can be merged sooner rather than later. It feels good and it Just
Works.
Thanks!
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-02-18 12:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 7:21 2.6.3-mm1 Andrew Morton
2004-02-18 7:43 ` 2.6.3-mm1 Andrew Morton
2004-02-18 9:25 ` 2.6.3-mm1 Andrew Morton
2004-02-18 13:42 ` 2.6.3-mm1 Rusty Russell
2004-02-18 18:50 ` 2.6.3-mm1 Andrew Morton
2004-02-18 11:13 ` 2.6.3-mm1 Sean Neakums
2004-02-18 11:14 ` 2.6.3-mm1 Jonathan Brown
2004-02-18 12:37 ` 2.6.3-mm1 Sean Neakums
2004-02-18 12:14 ` bert hubert [this message]
2004-02-18 14:26 ` 2.6.3-mm1 Ramon Rey Vicente
2004-02-18 18:55 ` 2.6.3-mm1 Andrew Morton
2004-02-18 19:06 ` 2.6.3-mm1 Matthew Wilcox
2004-02-18 16:16 ` 2.6.3-mm1 Bill Davidsen
2004-02-18 20:04 ` 2.6.3-mm1 Brandon Low
2004-02-18 20:22 ` 2.6.3-mm1 Andrew Morton
2004-02-18 20:33 ` 2.6.3-mm1 Brandon Low
2004-02-18 20:52 ` 2.6.3-mm1 Andrew Morton
2004-02-18 20:52 ` 2.6.3-mm1 Brandon Low
2004-02-18 21:00 ` 2.6.3-mm1 Andrew Morton
2004-02-18 22:15 ` 2.6.3-mm1 Christophe Saout
2004-02-19 0:33 ` 2.6.3-mm1 Brandon Low
2004-02-19 12:39 ` 2.6.3-mm1 Christophe Saout
2004-02-18 17:50 ` 2.6.3-mm1 James Simmons
2004-02-22 2:46 ` 2.6.3-mm1 William Lee Irwin III
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=20040218121416.GA13364@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=akpm@osdl.org \
--cc=christophe@saout.de \
--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
all inboxes | Powered by JetHome®