Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think I'm finally getting the hang of compiling TrueCrypt (6.1a) on RHEL 4 (2.6.9-78.0.13.ELsmp)*. I am however having some post build issues.
When I attempt to mount the new volume I get a message:
Code:
Your system uses an old version of the Linux kernel.
Due to a bug in the Linux kernel, your system may stop
responding when writing data to a TrueCrypt volume.
This problem can be solved by upgrading the kernel
to version 2.6.24 or later.
Does anybody know what bug they are referring to and what is meant by "may" (RFC2119 does not seem to apply).
I don't really have the option of stepping up to RHEL 5 at this time. Can I fix it in 4?
*Kernel Source Extraction, Fuse, wxWidgets, encryption headers, RTFM/RTFRM etc.
Many thanks in advance.
i
Last edited by isoides; 03-10-2009 at 01:05 PM.
Reason: Add tags, change name to TrueCrypt and RHEL4
I think I'm finally getting the hang of compiling TrueCrypt (6.1a) on RHEL 4 (2.6.9-78.0.13.ELsmp)*. I am however having some post build issues.
When I attempt to mount the new volume I get a message:
Code:
Your system uses an old version of the Linux kernel.
Due to a bug in the Linux kernel, your system may stop
responding when writing data to a TrueCrypt volume.
This problem can be solved by upgrading the kernel
to version 2.6.24 or later.
Does anybody know what bug they are referring to and what is meant by "may" (RFC2119 does not seem to apply).
I don't really have the option of stepping up to RHEL 5 at this time. Can I fix it in 4?
*Kernel Source Extraction, Fuse, wxWidgets, encryption headers, RTFM/RTFRM etc.
Many thanks in advance.
i
You don't have to upgrade to RHEL5 to get the latest kernel. Get in touch with RedHat (since you've got RHEL), and get the latest kernel from them, complete with installation instructions. I *THINK* you could do it by typing in "yum upgrade kernel", but there may be some gotchas there.
Why don't you rather use dm-crypt (which is the Linux standard way of encrypting disks), install the cryptsetup command (should be available as RHEL4 package) and you are ready to go, much easier than compiling truecrypt.
I'm going to play with dm-crypt for a day or two and see how friendly it is.
Looks like I'll have to upgrade the Kernel either way.
http://mareichelt.de/pub/texts.cryptoloop.php
"Both cryptoloop and dm-crypt in kernels prior to 2.6.10 are
vulnerable, and even recent dm-crypt still suffers from a weak crypto
implementation."
Given the complexity of all of this, I'm a bit intimidated by loop-AES. Thanks for the dm-crypt suggestion tux.
Just for closure sake.
We switched over to dm-crypt and haven't looked back. It took me and the dba a bit of time to figure out where to create the partition. I used LVM and neither of us has much experience with that tool. Should have been easier but it will be next time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.