[gentoo] truecrypt on gentoo issue

[RabbieBurns]

After a fun battle to get truecrypt to install on Gentoo, Ive finally got it running, created my encrypted container etc, all fine.

 

However when trying to mount the encrypted container, I get the following error:

 

Error: device-mapper: reload ioctl failed: Invalid argument
Command failed

 

I had to add FUSE to the kernel before TC would install, which I did as a module.

 

Ive not rebooted, but I dont think I need to with just a modular kernel change rather than compiling it within?

 

Any suggestions?

[RabbieBurns]

oasis ~ # truecrypt /enc/files.enc
Enter mount directory [default]: /home/user/secret
Enter password for /enc/files.enc:
Enter keyfile [none]:
Protect hidden volume? (y=Yes/n=No) [No]: n
Error: device-mapper: reload ioctl failed: Invalid argument
Command failed

 

I'm still no further on with this.. hope its OK to bump in case anyone's got any ideas..

[Geoff]

Please post the more detailed error message that gets spammed to your syslog when you do that.

[RabbieBurns]

oasis ~ # cat /var/log/messages | grep ioctl
Jan 19 14:51:15 oasis device-mapper: ioctl: error adding target to table
Jan 19 14:54:12 oasis device-mapper: ioctl: error adding target to table

[Geoff]

Install lvm2 and dmraid.

[RabbieBurns]

Installed both. Same error. I missed a line out the logs last time.

 

Jan 19 16:00:38 oasis device-mapper: table: 254:0: crypt: unknown target type
Jan 19 16:00:38 oasis device-mapper: ioctl: error adding target to table

[RabbieBurns]

been away for a couple of weeks.. still not managed to solve this problem - does anyone else have any ideas?

[RabbieBurns]

Geoff, if I gave you access to the machine would you be willing to have a look into this for me please?

[gentoo]

since you're gentoo user i guess you have your own kernel so

 

1) check whether you have appropriate modules compiled in kernel that is:

 

<*>Device Drivers

<*>Block Devices

<*>Loopback device support

.....

<*>Multiple Devices driver support (LVM and RAID)

<*>Device mapper support

<*>Crypt target support

 

if you have all of these go to truecrypt>settings>preferences>system integration

 

and check "Do not use kernel cryptographic services"

 

if you have the same error (or maybe other now)

 

2) Check if you have all cipher and hash/digest methods used by truecrypt (and chosen by you) compiled in your kernel/as modules (then load them)

 

these are:

 

<*>Cryptographic API

<*>XTS support

<*>RIPEMD-160 digest algorithm |default for truecrypt

<*>SHA384 and SHA512 digest algorithms |you can choose

<*>Whirpool digest algorithm |sha512 and whirpool too

 

<*>AES cipher algorithms |default truecrypt cipher

<*>AES cipher algorithm (x86_64) -> if you are on such architecture

or/and:

<*>Serpent cipher algorithm

<*>Twofish cipher algorithm

<*>Twofish cipher algorithm(x86_64)

 

it worked for me

 

hope it helps

 

but i'm disgusted by lack of ANY support for linux instalation (or linux support at all) on truecrypt home page... there are only methods how to use your system less useable (those hidden volumes, hidden systems etc. are overkill - if sbd would interrogate you - you would get skompolomine injection and told them not only passwords but some things you don't even know that you remember) that's why i posted this solution (usually i don't).

[RabbieBurns]

thanks for that, i will give it a try as soon as i can. I dont use X but am sure i can implement the setting you recommend from the cli.

[gentoo]

i don't recomend this option cause it affects performance - i suggest enabling it for testing if the lack of crypto algorithm is the cause of your error (i had number 253 in my error but...)

 

if it's the case then after enabling it everything should work (very slow though).

if you can't mount volume despite enabling it your problem lies somewhere else (probably:P)

 

i have compiled in the kernel (on my laptop), but if you can't reboot your system (without X -> i guess server) you can compile them as modules (device mapper as well)

 

I came to this solution recalling old days when truecrypt was kernel module, and loading it required all other crypto modules loaded:)

 

good luck