From: James Morris <jmorris@intercode.com.au>
To: Frank v Waveren <fvw@var.cx>
Cc: linux-kernel@vger.kernel.org, <Andries.Brouwer@cwi.nl>,
<linux-crypto@nl.linux.org>
Subject: Re: 2.6.0-test2+Util-linux/cryptoapi
Date: Thu, 31 Jul 2003 14:39:45 +1000 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0307311420080.21102-100000@excalibur.intercode.com.au> (raw)
In-Reply-To: <1059621603HIC.fvw@tracks.var.cx>
On Thu, 31 Jul 2003, Frank v Waveren wrote:
> Moving to the slightly more ontopic stuff for lk@vger: Is access to
> the cryptoapi algorithms exposed to userspace yet?
No, there is no point (apart from testing) unless the kernel API is
providing access to crypto hardware.
> Thirdly, has the encryption setup changed again since 2.4.x with hvr's
> testing cryptoapi stuff? I have a filesystem encrypted with 256 bits
> serpent, yet it won't decrypt using 2.6.0-test2 and util-linux 2.12.
The kerneli serpent implementation is incorrect (it's reversed, a common
implementation problem with this algorithm).
> Lastly: Why the move from a /proc/crypto directory containing files
> for all the algorithms to one monolithic /proc/crypto file? Isn't the
> former a lot nicer from the userspace programmer's point of view?
Possibly, although it's probably too late to change now for 2.6.
- James
--
James Morris
<jmorris@intercode.com.au>
next prev parent reply other threads:[~2003-07-31 4:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 3:45 2.6.0-test2+Util-linux/cryptoapi Frank v Waveren
2003-07-31 4:39 ` James Morris [this message]
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
2003-07-31 9:41 2.6.0-test2+Util-linux/cryptoapi Andries.Brouwer
2003-08-01 18:45 ` 2.6.0-test2+Util-linux/cryptoapi Ben Slusky
2003-08-13 14:42 ` 2.6.0-test2+Util-linux/cryptoapi Bill Davidsen
2003-08-01 21:00 2.6.0-test2+Util-linux/cryptoapi Andries.Brouwer
2003-08-13 16:42 2.6.0-test2+Util-linux/cryptoapi Andries.Brouwer
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=Mutt.LNX.4.44.0307311420080.21102-100000@excalibur.intercode.com.au \
--to=jmorris@intercode.com.au \
--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®