Yet to report another hit of this bug. Took me some hours to find out why my swap wouldn't come at boot time, altough I followed all the documentation.
I am really surprised to find that cryptsetup depends on dynamic libraries. Not only the ones in /usr/lib, but in general it is a bad idea. This executable is critical for the early boot phase, Messing around with it is playing with fire.
Found a workaround, which is to list /usr as a dependency in crypdisks, but this only works since I only have swap encrypted for the moment. Thinking of what have happend if I'd just naively had encrypted my root partition. Undermines my confidence in Ubuntu.
Yet to report another hit of this bug. Took me some hours to find out why my swap wouldn't come at boot time, altough I followed all the documentation.
I am really surprised to find that cryptsetup depends on dynamic libraries. Not only the ones in /usr/lib, but in general it is a bad idea. This executable is critical for the early boot phase, Messing around with it is playing with fire.
Found a workaround, which is to list /usr as a dependency in crypdisks, but this only works since I only have swap encrypted for the moment. Thinking of what have happend if I'd just naively had encrypted my root partition. Undermines my confidence in Ubuntu.