cryptsetup 2.1.1.2 is not compatible withs 2.1.1.0

Bug #605339 reported by Jaanus Rauk
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cryptsetup

I-m mounting a volume with following commands:
cryptsetup create crypt /dev/sda3
mount /dev/mapper/crypt /home

After cryptsetup upgrade to '2.1.1.2-1ubuntu1 (maverick)' the mount doesn't recognize media any more.

So I'm stuck with version '2.1.1.0~rc2-1ubuntu13 (lucid)' for now

Revision history for this message
asi (gmazyland) wrote : Re: [Bug 605339] [NEW] cryptsetup 2.1.1.2 is not compatible withs 2.1.1.0

On 07/14/2010 11:48 AM, Jaanus Rauk wrote:
> Public bug reported:
>
> Binary package hint: cryptsetup
>
> I-m mounting a volume with following commands:
> cryptsetup create crypt /dev/sda3
> mount /dev/mapper/crypt /home
>
> After cryptsetup upgrade to '2.1.1.2-1ubuntu1 (maverick)' the mount
> doesn't recognize media any more.

please read:
http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup

iow you must use now
 cryptsetup create -c aes-cbc-plain -s 256 -h ripemd160

Milan

Revision history for this message
asi (gmazyland) wrote :

Btw if Ubuntu cryptsetup maintainers want to be backward compatible
in stable branch, I suggest reading package release notes and build
package with

configure --with-luks1-keybits=128 --with-plain-mode=cbc-plain

which set default to be fully compatible
(luks change is not problem here, plain mode is)

m.

Revision history for this message
Jaanus Rauk (jaanusrauk) wrote :

cryptsetup create -c aes-cbc-plain -s 256 -h ripemd160 crypt /dev/sda3
works for me, thanks.

Revision history for this message
mejo (jonas-freesources) wrote :

the changes of default cipher and size have been documented in debian/NEWS. i consider this bug as invalid.

Changed in cryptsetup (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.