Skip to contentSkip to conversation

TruCrypt

DISCUSSION Dave Haywood 2 participants 2 messages Nov 21, 2007

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I see that the TruCrypt build borks under the latest -rc kernels.
See https://bugs.gentoo.org/show_bug.cgi?id=198394 for an example.

I think this is because the kernel interfaces tc uses have changed.

Is anyone aware of any fixes to correct this problem?

Has anyone considered incorporating the non-userland parts of tc
into the kernel to avoid this borkage in the future? tc is under some non-GPL license so this may not be possible?

Thx,

Dave.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFHRGFks7shH0x9UrgRAgmbAJ91AFFTN9RkoQlnIJYMmOPpgiS0eACfcpED yReT7yk/1Pv3oGdmGNmrHU4=
=GICs
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#1 lore raw
Quoted 8 lines · Dave Haywood

Hi,

I see that the TruCrypt build borks under the latest -rc kernels.
See https://bugs.gentoo.org/show_bug.cgi?id=198394 for an example.

Has anyone considered incorporating the non-userland parts of tc
into the kernel to avoid this borkage in the future? tc is under some non-GPL license so this may not be possible?

It's been discussed on the lkml. The author never submitted it for inclusion in the kernel.
Take a look at http://lkml.org/lkml/2007/11/5/369

Kristof