[Solved] cryptsetup update broke cryptfs?

Gentist · Apprentice Joined: 20 Mar 2004 Posts: 247

Yesterday I noticed an update for cryptsetup-luks, which mentioned that it would be replacing cryptsetup. Checking portage, it appeared that it had taken effect (the new cryptsetup was now at version 1.0.5). Since it supposedly fixed one of the problems I was having with the previous version of cryptsetup-luks, I unmerged cryptsetup-luks and emerged cryptsetup. It appeared to solve my problem, but upon next reboot, my encrypted partitions (save /) didn't mount properly.

It appears that it's not reading /etc/conf.d/cryptfs at all. I did copy the file over to /etc/conf.d/dmcrypt, but it doesn't appear to read that either.

Note that I have NOT run "rc-update add dmcrypt boot" since I'm not running baselayout-2. However, since things just stopped working, I must be missing something, but what?

My temporary solution has been to move all of my system vital stuff over to directories on the root partition, and comment out the mount commands in /etc/fstab. This allows me to boot the system properly, but leaves me without a working swap and no added security for /tmp. So, I need this fixed ASAP.

didymos · Posted: Thu Aug 16, 2007 8:21 am Post subject:

Sounds like this:

dmcrypt mappings not creating when rebooting after switching to cryptsetup 1.0.5
_________________
Thomas S. Howard

Gentist · Apprentice Joined: 20 Mar 2004 Posts: 247

Thank you, that solved it.

I don't quite understand why critical fixes like that are applied without bumping the version number though (like 1.0.5-r1). Makes it harder to know when a problem has been taken care of.

didymos · Posted: Thu Aug 16, 2007 9:08 am Post subject:

I don't know. It was basically a dumb typo times three, so I can understand not bumping it. Still, they could have bumped to 1.0.5-r1 and then deleted the 1.0.5 ebuild entirely.
_________________
Thomas S. Howard