From: Frank v Waveren <fvw@var.cx>
To: James Morris <jmorris@intercode.com.au>
Cc: linux-kernel@vger.kernel.org, linux-crypto@nl.linux.org
Subject: Re: 2.6.0-test2+Util-linux/cryptoapi
Date: Thu, 31 Jul 2003 18:37:18 +0200 [thread overview]
Message-ID: <1059669067FAU.fvw@tracks.var.cx> (raw)
In-Reply-To: <Mutt.LNX.4.44.0307311515260.21304-100000@excalibur.intercode.com.au>
On Thu, Jul 31, 2003 at 03:20:48PM +1000, James Morris wrote:
> > Owch. But I assume this didn't sneak in since the testing cryptoAPI
> > patches? Or have the algorithms been redone?
> I'm not sure what you mean.
I'm currently using hvr's testing cryptoAPI patches for 2.4.x, and I
have a block device encrypted with 256 bits serpent. This cannot be
correctly decrypted with linux-2.6.0-test2. Has something in the use
of serpent changed since then (or has block numbering changed again)?
Or should I go bug-hunting?
--
Frank v Waveren Fingerprint: 21A7 C7F3
fvw@[var.cx|stack.nl|chello.nl] ICQ#10074100 1FF3 47FF 545C CB53
Public key: hkp://wwwkeys.pgp.net/fvw@var.cx 7BD9 09C0 3AC1 6DF2
next prev parent reply other threads:[~2003-07-31 16:37 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 ` 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 ` Frank v Waveren [this message]
-- strict thread matches above, loose matches on Subject: below --
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=1059669067FAU.fvw@tracks.var.cx \
--to=fvw@var.cx \
--cc=jmorris@intercode.com.au \
--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