cryptsetup update may makes your crypted devices unreadable!

[gerd]

Only devices created with whirlpool hash may be affected.
Read 8.3 of this
https://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#8._Issues_with_Specific_Versions_of_cryptsetup

[DeKa]

Where is the problem?

Code: [Select]

root@siductionbox:/home/deka# apt-cache policy cryptkeeper
cryptkeeper:
  Installiert:           0.9.5-5.1
  Installationskandidat: 0.9.5-5.1
  Versionstabelle:
 *** 0.9.5-5.1 0
        500 http://ftp2.de.debian.org/debian/ unstable/main amd64 Packages
        500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
        500 http://ftp.is.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
root@siductionbox:/home/deka# apt-cache policy cryptsetup
cryptsetup:
  Installiert:           2:1.6.6-1
  Installationskandidat: 2:1.6.6-1
  Versionstabelle:
 *** 2:1.6.6-1 0
        500 http://ftp2.de.debian.org/debian/ unstable/main amd64 Packages
        500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
        500 http://ftp.is.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

[bluelupo]

No problem here with dm-crypt (LUKS), cryptkeeper.

[ReinerS]

Also no problem here. My encfs-folder are ok, when mounting via cryptkeeper.
I used the standard encfs method to create those, maybe therefore this whirlpol hash feature is not in effect.

regards

Reiner