If that's what you _really_ did, I'm pretty sure it can't have worked. The newline notwithstanding, whitespace still matters, and there is no --verify parameter (you probably meant to use --verify-passphrase).Yes, I did you verify-passphrase, just a typo! So, from the replies that I have gotten it sounds like there are two different camp ( groups) that are doing something with cryptsetup. Isn't that a duplication of effort? ---------------------------------------------------------------------------
On 9/21/2017 12:25 AM, Michael Kjörling
wrote:
On 20 Sep 2017 15:38 -0700, from jlowry@xxxxxxx (Jerry Lowry):I have created an encrypted drive using the following commands: #>cryptsetup --verify=passphrase -- hash=sha256 --keyfile=/dir/file create /dev/mapper/testcui /dev/sdbIf that's what you _really_ did, I'm pretty sure it can't have worked. The newline notwithstanding, whitespace still matters, and there is no --verify parameter (you probably meant to use --verify-passphrase).Sep 20 14:19:53 jubilee systemd[1]: Starting Cryptography Setup for /dev/mapper/testcui... -- Subject: Unit systemd-cryptsetup@-dev-mapper-testcui.service has begun start-up -- Defined-By: systemd -- Support: https://url.emailprotection.link/?aU9kur6wsNUi02sZK7jqbqHUDJAa-o4ToSDYQrs9syxvrrIdB1sQAdzV3HPUijEgCYM0mtOEY4w7RKS2IUkVivQ~~At a minimum, run cryptsetup directly (not through systemd) with the --debug flag and post back with the output thus obtained. |
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
