Quoting Robert Bihlmeyer (robbe@orcus.priv.at):
> Robert van der Meulen wrote:
> > The format of volumes encrypted by kernel-patch-int and cryptoapi
> > differs, and kernel-patch-int volumes will not be usable by
> > cryptoapi.
>
> If you're alluding to the iv changes, that is not true. At least I
> could get at data on a CDROM crypted under the old scheme after
> burning a few black candles.
>
> So keeping the old kerneli patch around may be unnecessary.
I must admit i haven't looked into cryptoapi deeply enough to give a decent
(and fulfilling) answer on this. I got the impression, that the IV problem
can be circumvented by enabling some code that is specifically there to
provide backwards compatibility, but _does_ hamper/influence the 'newer'
code. If so, I don't feel like offering the backward-compatibility option.
Greets,
Robert
--
( o> Linux Generation <o )
///\ finger rvdm@debian.org for my GnuPG/PGP key. /\\\
\V_/ Microsoft is number one. And you, the millions of consumers \_V/
who use our products, are the zeroes. -- the onion
Attachment:
pgpACFr5cdvS2.pgp
Description: PGP signature