From: Ben Slusky <sluskyb@paranoiacs.org>
To: Andries.Brouwer@cwi.nl
Cc: fvw@var.cx, linux-kernel@vger.kernel.org, linux-crypto@nl.linux.org
Subject: Re: 2.6.0-test2+Util-linux/cryptoapi
Date: Fri, 1 Aug 2003 14:45:43 -0400 [thread overview]
Message-ID: <20030801184543.GA15828@fukurou.paranoiacs.org> (raw)
In-Reply-To: <UTC200307310941.h6V9fP204094.aeb@smtp.cwi.nl>
On Thu, 31 Jul 2003 11:41:25 +0200, Andries.Brouwer@cwi.nl wrote:
> The patches I got were maximal, too much junk.
> So I went for a minimal version instead.
>
> It is usable (when the kernel part is stable, which it isn't today)
> but mount/losetup may well acquire a few options before it is
> conveniently usable.
Can we discuss those options now? I find the latest losetup to be
completely unusable, tho' I appreciate the effort that's gone into it
so far.
Firstly, are the other key size choices (128-bit, 192-bit) gone for
good? If so then I'll need to redo this entire hard disk (which currently
uses 128-bit AES) before I can test 2.6 on my laptop.
Secondly, there's the issue of passphrase hashing. I agree with the
decision to cut it out of losetup, but where do we put it now? Andries
has suggested an external program, but this isn't as simple as it sounds.
To get this working would require a new way of reading the passphrase,
since the hashed passphrase might contain a newline, or a null. Maybe
change the semantics of the -p option, so that:
losetup -e aes /dev/loop/10 /home/sluskyb/testloop
will work when I give it the passphrase "foobar", but also
pwhash -h sha1 |losetup -e aes -k 128 -p 0 /dev/loop/0 \
/dev/discs/disc0/part3
will read exactly 16 bytes of (probably) non-printable chars and use
that as the key.
Questions? Comments? Flames?
--
Ben Slusky | A free society is a society
sluskyb@paranoiacs.org | where it is safe to be
sluskyb@stwing.org | unpopular.
PGP keyID ADA44B3B | -Adlai Stevenson
next prev parent reply other threads:[~2003-08-01 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 9:41 2.6.0-test2+Util-linux/cryptoapi Andries.Brouwer
2003-08-01 18:45 ` Ben Slusky [this message]
2003-08-13 14:42 ` 2.6.0-test2+Util-linux/cryptoapi Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 16:42 2.6.0-test2+Util-linux/cryptoapi Andries.Brouwer
2003-08-01 21:00 2.6.0-test2+Util-linux/cryptoapi Andries.Brouwer
2003-07-31 3:45 2.6.0-test2+Util-linux/cryptoapi Frank v Waveren
2003-07-31 4:39 ` 2.6.0-test2+Util-linux/cryptoapi James Morris
2003-07-31 5:04 ` 2.6.0-test2+Util-linux/cryptoapi Frank v Waveren
2003-07-31 5:20 ` 2.6.0-test2+Util-linux/cryptoapi James Morris
2003-07-31 16:37 ` 2.6.0-test2+Util-linux/cryptoapi Frank v Waveren
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=20030801184543.GA15828@fukurou.paranoiacs.org \
--to=sluskyb@paranoiacs.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=fvw@var.cx \
--cc=linux-crypto@nl.linux.org \
--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®