luksAddKey hangs for ~85 minutes and then fails

[Joe Hillenbrand <joehillen@xxxxxxxxx>]

I've been trying and trying to add a new key to one of my devices so
that I can automount,
but it consistently fails.

I run the following command. It hangs for ~85 minutes every time (I've
tried at least 5 times)
and then fails with the "Not compatible PBKDF2 options" message and exit code 1.

    $ sudo cryptsetup luksAddKey /dev/md1 /etc/.md1.key
    Enter any existing passphrase:
    Not compatible PBKDF2 options (using hash algorithm sha256).

I've tried generating several different keys of different sizes.
Exact same behavior for all of them.

    dd bs=512 count=4 if=/dev/urandom of=/etc/.md1.key iflag=fullblock
    dd bs=1 count=32 if=/dev/urandom of=/etc/.md1.key iflag=fullblock
    dd bs=8192KB count=1 if=/dev/urandom of=/etc/.md1.key iflag=fullblock
    head -c 2880 /dev/urandom | uuencode -m - | head -n 65 | tail -n
64 | sudo tee /etc/.md1.key

Here is some other information.

    $ uname -r
    4.6.2-1-ARCH

    $ cryptsetup --version
    cryptsetup 1.7.1

    $ sudo cryptsetup luksDump /dev/md1
    LUKS header information for /dev/md1

    Version:           1
    Cipher name:       aes
    Cipher mode:       xts-plain64
    Hash spec:         sha256
    Payload offset:    4096
    MK bits:           256
    MK digest:         xxxxx
    MK salt:           xxxxxx
    MK iterations:     333750
    UUID:

    Key Slot 0: ENABLED
        Iterations:             xxxxxxx
        Salt:                   xxxxxxx
        Key material offset:    8
        AF stripes:                4000
    Key Slot 1: DISABLED
    Key Slot 2: DISABLED
    Key Slot 3: DISABLED
    Key Slot 4: DISABLED
    Key Slot 5: DISABLED
    Key Slot 6: DISABLED
    Key Slot 7: DISABLED

    $ sudo mdadm --detail /dev/md1
    /dev/md1:
            Version : 1.2
      Creation Time : Thu Jun  9 14:01:50 2016
        Raid Level : raid5
        Array Size : 5860063232 (5588.59 GiB 6000.70 GB)
      Used Dev Size : 2930031616 (2794.30 GiB 3000.35 GB)
      Raid Devices : 3
      Total Devices : 3
        Persistence : Superblock is persistent

      Intent Bitmap : Internal

        Update Time : Fri Jun 17 13:13:00 2016
              State : clean
    Active Devices : 3
    Working Devices : 3
    Failed Devices : 0
      Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K


        Number   Major   Minor   RaidDevice State
          0       8       17        0      active sync   /dev/sdb1
          1       8       33        1      active sync   /dev/sdc1
          3       8       81        2      active sync   /dev/sdf1
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt