Comment 3 for bug 367577

Was hit by this one when updating from intrepid. Apparently went fine until I discovered that in jaunty only one of my encrypted partitions was being mounted, namely the one with a 256 bit keysize. None of the others did, took me well into the night fearing all data on those disks was lost before finding this bug report putting me on track to the solution.

The patch doesn't appear to work for me though, it does cause a "-s" parameter to be used but with the wrong bitsize (104 instead of 448). Manually, everything works again when using the cryptsetup command when setting the hash parameter to ripemd160 and using the -s options with the correct keysize.

Overall, this is a severe regression, updating from a perfectly working system without any useful warning users end up with apparently unusable encrypted partitions; getting error messages like "mount: you must specify the filesystem type" suggesting there is no recognisable data on disk or some kind of severe filesystem corruption. This really needs to be fixed!