Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34525 - cryptsetup 1.6.0

Attached to Project: Arch Linux
Opened by Deleted (engineer_h) - Saturday, 30 March 2013, 23:01 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 07 April 2013, 22:02 GMT
Task Type Bug Report
Category Security
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I wanted to setup a clean full encryption for my system. Creating 2 partitions that each of'em separated for sake boot processes (/ & /boot).
Before anything, I have upgraded my USB, which holds all the required installation with pacman -Syu after that, I decide to encrypt my second partition (/) with this command:

cryptsetup -c serpent-xts-plain64 -s 512 -h sha512 --iter-time 5000 --use-random luksFormat /dev/sda2

Sadly, I got several errors after confirming the passphrase.

However, I didn't have any type of errors BEFORE I do the upgrading (pacman -Su) which is really strange.
__________________________________________________________

Additional info:
* package version(s): cryptsetup 1.6.0
__________________________________________________________

Steps to reproduce:

# pacman -Syu (got some updates for pacman and other packages and I have installed all of'em)
# cryptsetup -c serpent-xts-plain64 -s 512 -h sha512 --iter-time 5000 --use-random luksFormat /dev/sda2

Error:

[ 1455.751731] device-mapper: table: 254:1: crypt: unknown target type
device-mapper: reload ioctl on temporary-cryptsetup-3968 failed: Invalid agrument
Failed to setup dm-crypt key mapping for device /dev/sda2.
Check that kernel supports serpent-xts-plain64 cipher
__________________________________________________________

NOTE: I have tried aes one but with same results above.
NOTE: # modprobe dm_mod is not required (already running).
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 07 April 2013, 22:02 GMT
Reason for closing:  None
Comment by Deleted (engineer_h) - Sunday, 07 April 2013, 21:30 GMT
Problem has been solved by using the latest release; archlinux-2013.04.01.

Loading...