[SOLVED?] Kernel/System update removed twofish option from ecryptfs

Hiato · 2011-01-14 11:29:15

The title says it all. After a pacman -Syyu last night and some manual module stuff for ATI and rtl wireless, and some cyclic dependency annoyances (ghc and gtk2hs I am looking at you) it all went smoothly. However, as it turned out ecryptfs no longer supports twofish. It's not listed as an option in the menu thing, nor taken as a mount option (-22 invalid argument). Reinstalling the relevant AUR packages did nothing either. Nor did reboots, or modprobes and such.

I'm sort of at wits end now, what with my home being encrypted with twofish and it being, well, my home. Any suggestions - short of ugly things like reinstall - as to how to remedy this? I would be most grateful.

Hiato

EDIT: Just to clarify, my options look like this:

Select cipher:
 1) aes: blocksize = 16; min keysize = 16; max keysize = 32 (not loaded)
 2) blowfish: blocksize = 16; min keysize = 16; max keysize = 56 (not loaded)
 3) des3_ede: blocksize = 8; min keysize = 24; max keysize = 24 (not loaded)
 4) cast6: blocksize = 16; min keysize = 16; max keysize = 32 (not loaded)
 5) cast5: blocksize = 8; min keysize = 5; max keysize = 16 (not loaded)
Selection [aes]:

EDIT some more: Upgrading to the 2.6.37 testing kernel and headers and rebuilding the ecryptfs-utils package (from the AUR, again) seemed to change nothing either, nor did reloading the (newly found, to me anyway) twofish_generic and twofish_common modules. Interestingly, mount tells me to check the system logs, but dmesg shows me nothing related to this. I'm really starting to get pretty desperate here.

SOLVED:

Well, after a while I just became desperate, so I cd'd to the sourco of the ecryptfs-utils AUR package and ran

grep twofish /src/ecryptfs-utils-84/src/*/*

hoping for something, anything. As it turned out, this was the key. The one .c file referenced a module called twofish.ko while I had only the twofish_common.ko and twofish_general.ko loaded. There must have been a name change in the crypto api since my last update, and the ecryptfs-utils package had not yet been patched to accomodate this. So, I unloaded those, built the one that came with the package, loaded it and et voila!

tl;dr = Make sure you load the twofish.ko module and not the ones that are loaded by default with the new kernels: twofish_common and twofish_general.

Furthermore, I'm not sure who to notify about this naming mismatch, and I would patch it myself if not for the lack of understanding in what the difference is between the three modules and which the ecryptfs-utils package actually needs. Does anyone have any input on this?

Last edited by Hiato (2011-01-14 18:50:32)

anrxc · 2011-01-19 08:25:13

With 2.6.36.3, and now 2.6.37 from [testing] I have no such problems, on i686 My home is too encrypted with twofish. Following modules are loaded:

twofish_generic         5381  0 
twofish_i586            4537  1314 
twofish_common         12357  2 twofish_generic,twofish_i586

KoS · 2012-01-23 12:48:46

I had a similar problem with blowfish and this post pointed it out that all I need to do is load the kernel module(s).

Arch Linux

#1 2011-01-14 11:29:15

[SOLVED?] Kernel/System update removed twofish option from ecryptfs

#2 2011-01-19 08:25:13

Re: [SOLVED?] Kernel/System update removed twofish option from ecryptfs

#3 2012-01-23 12:48:46

Re: [SOLVED?] Kernel/System update removed twofish option from ecryptfs

Board footer