11:55 a.m.
Has anyone looked at truecrypt? Looks interesting. I D/L the source, but
it says:
Note that Linux kernel headers, located in the 'include' directory, are
not sufficient for compilation of the TrueCrypt kernel module. Fields of
'dm_dev' structure must be accessed by TrueCrypt but they are defined only
in
an internal kernel header 'drivers/md/dm.h'. No appropriate accessor
function
is available. The complete source code of the Linux kernel is required for
compilation of the kernel module.
12:07 p.m.
On Tue, 25 Sep 2007, Neal Becker wrote:
Has anyone looked at truecrypt? Looks interesting. I D/L the
source, but
it says:
Note that Linux kernel headers, located in the 'include' directory, are
not sufficient for compilation of the TrueCrypt kernel module. Fields of
'dm_dev' structure must be accessed by TrueCrypt but they are defined only
in
an internal kernel header 'drivers/md/dm.h'. No appropriate accessor
function
is available. The complete source code of the Linux kernel is required for
compilation of the kernel module.
Don't we BR kernel-devel when building kmods anyway? I don't think this
is a problem at all. (Aside from the possibility of kmod packaging going
anyway, anyway.)
Jima
12:13 p.m.
Jima wrote:
On Tue, 25 Sep 2007, Neal Becker wrote:
> Has anyone looked at truecrypt? Looks interesting. I D/L the source, but
> it says:
>
> Note that Linux kernel headers, located in the 'include' directory, are
> not sufficient for compilation of the TrueCrypt kernel module. Fields of
> 'dm_dev' structure must be accessed by TrueCrypt but they are defined only
> in
> an internal kernel header 'drivers/md/dm.h'. No appropriate accessor
> function
> is available. The complete source code of the Linux kernel is required for
> compilation of the kernel module.
Don't we BR kernel-devel when building kmods anyway? I don't think this
is a problem at all. (Aside from the possibility of kmod packaging going
anyway, anyway.)
But, drivers/md/dm.h is not in kernel-devel.
-Eric
12:15 p.m.
On Tue, 25 Sep 2007 12:07:29 -0500 (CDT)
Jima <jima(a)beer.tclug.org> wrote:
On Tue, 25 Sep 2007, Neal Becker wrote:
> Has anyone looked at truecrypt? Looks interesting. I D/L the source, but
> it says:
>
> Note that Linux kernel headers, located in the 'include' directory, are
> not sufficient for compilation of the TrueCrypt kernel module. Fields of
> 'dm_dev' structure must be accessed by TrueCrypt but they are defined only
> in
> an internal kernel header 'drivers/md/dm.h'. No appropriate accessor
> function
> is available. The complete source code of the Linux kernel is required for
> compilation of the kernel module.
Don't we BR kernel-devel when building kmods anyway? I don't think this
is a problem at all. (Aside from the possibility of kmod packaging going
anyway, anyway.)
It's not a possibility. They are going away.
josh
1:39 p.m.
On Tue, Sep 25, 2007 at 12:55:30PM -0400, Neal Becker wrote:
Has anyone looked at truecrypt? Looks interesting. I D/L the
source, but
it says:
Note that Linux kernel headers, located in the 'include' directory, are
not sufficient for compilation of the TrueCrypt kernel module. Fields of
'dm_dev' structure must be accessed by TrueCrypt but they are defined only
in
an internal kernel header 'drivers/md/dm.h'. No appropriate accessor
function
is available. The complete source code of the Linux kernel is required for
compilation of the kernel module.
Truecrypt is awesome, but their license[0] is a bit questionable. It's a
hybrid of a bunch of different licenses and has some interesting
distribution clauses. IANAL, so we definitely would want to run it by
fedora-legal-list if we hope to get truecrypt into Fedora. There has also
been some talk about this license in the Debian community:
http://lists.debian.org/debian-legal/2006/06/msg00294.html
http://lists.debian.org/debian-legal/2006/07/msg00008.html
luke
[0]: http://www.truecrypt.org/license.php
2:43 p.m.
On Tuesday, 25 September 2007 at 20:39, Luke Macken wrote:
On Tue, Sep 25, 2007 at 12:55:30PM -0400, Neal Becker wrote:
> Has anyone looked at truecrypt? Looks interesting. I D/L the source, but
> it says:
>
> Note that Linux kernel headers, located in the 'include' directory, are
> not sufficient for compilation of the TrueCrypt kernel module. Fields of
> 'dm_dev' structure must be accessed by TrueCrypt but they are defined
only
> in
> an internal kernel header 'drivers/md/dm.h'. No appropriate accessor
> function
> is available. The complete source code of the Linux kernel is required for
> compilation of the kernel module.
Truecrypt is awesome, but their license[0] is a bit questionable. It's a
hybrid of a bunch of different licenses and has some interesting
distribution clauses. IANAL, so we definitely would want to run it by
fedora-legal-list if we hope to get truecrypt into Fedora. There has also
been some talk about this license in the Debian community:
http://lists.debian.org/debian-legal/2006/06/msg00294.html
http://lists.debian.org/debian-legal/2006/07/msg00008.html
luke
[0]: http://www.truecrypt.org/license.php
Here are src.rpms with tools and kmod:
http://rpm.greysector.net/livna/
Feel free to submit them to livna/rpmfusion. I don't have time to maintain
them, but I made those when I was looking for a cryptofs solution for both
Linux and Windows (and settled on LUKS instead).
Regards,
R.
--
Fedora contributor http://fedoraproject.org/wiki/DominikMierzejewski
Livna contributor http://rpm.livna.org MPlayer developer http://mplayerhq.hu
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
4:36 p.m.
Luke Macken wrote:
On Tue, Sep 25, 2007 at 12:55:30PM -0400, Neal Becker wrote:
> Has anyone looked at truecrypt? Looks interesting. I D/L the source, but
> it says:
>
> Note that Linux kernel headers, located in the 'include' directory, are
> not sufficient for compilation of the TrueCrypt kernel module. Fields of
> 'dm_dev' structure must be accessed by TrueCrypt but they are defined only
> in
> an internal kernel header 'drivers/md/dm.h'. No appropriate accessor
> function
> is available. The complete source code of the Linux kernel is required for
> compilation of the kernel module.
Truecrypt is awesome, but their license[0] is a bit questionable. It's a
you can always found the latest kmod in:
http://www.lfarkas.org/linux/packages/fedora/7/
--
Levente "Si vis pacem para bellum!"
1:33 a.m.
On Tuesday, 25 September 2007 at 23:36, Farkas Levente wrote:
Luke Macken wrote:
> On Tue, Sep 25, 2007 at 12:55:30PM -0400, Neal Becker wrote:
>> Has anyone looked at truecrypt? Looks interesting. I D/L the source, but
>> it says:
>>
>> Note that Linux kernel headers, located in the 'include' directory,
are
>> not sufficient for compilation of the TrueCrypt kernel module. Fields of
>> 'dm_dev' structure must be accessed by TrueCrypt but they are defined
only
>> in
>> an internal kernel header 'drivers/md/dm.h'. No appropriate accessor
>> function
>> is available. The complete source code of the Linux kernel is required for
>> compilation of the kernel module.
>
> Truecrypt is awesome, but their license[0] is a bit questionable. It's a
you can always found the latest kmod in:
http://www.lfarkas.org/linux/packages/fedora/7/
Talk about duplicated effort. ;) Why don't you submit your package (perhaps
after merging with mine) to rpmfusion?
Regards,
R.
--
Fedora contributor http://fedoraproject.org/wiki/DominikMierzejewski
Livna contributor http://rpm.livna.org MPlayer developer http://mplayerhq.hu
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
4:21 a.m.
Dominik 'Rathann' Mierzejewski wrote:
On Tuesday, 25 September 2007 at 23:36, Farkas Levente wrote:
> Luke Macken wrote:
>> On Tue, Sep 25, 2007 at 12:55:30PM -0400, Neal Becker wrote:
>>> Has anyone looked at truecrypt? Looks interesting. I D/L the source, but
>>> it says:
>>>
>>> Note that Linux kernel headers, located in the 'include' directory,
are
>>> not sufficient for compilation of the TrueCrypt kernel module. Fields of
>>> 'dm_dev' structure must be accessed by TrueCrypt but they are
defined only
>>> in
>>> an internal kernel header 'drivers/md/dm.h'. No appropriate
accessor
>>> function
>>> is available. The complete source code of the Linux kernel is required for
>>> compilation of the kernel module.
>> Truecrypt is awesome, but their license[0] is a bit questionable. It's a
> you can always found the latest kmod in:
> http://www.lfarkas.org/linux/packages/fedora/7/
Talk about duplicated effort. ;) Why don't you submit your package (perhaps
after merging with mine) to rpmfusion?
i'd be happy if any repo will contain it and i don't have to recompile.
everybody can use my spec in any repo. the main reason that i use it
(ie. i've truecrypt volumes) and i always need the latest kmod for the
latest fedora kernel while most repo is in a few days delay.
--
Levente "Si vis pacem para bellum!"
6055
days inactive
6056
days old
9 comments
7 participants
participants (7)
-
Dominik 'Rathann' Mierzejewski -
Eric Sandeen -
Farkas Levente -
Jima -
Josh Boyer -
Luke Macken -
Neal Becker