You would think that. Unfortunately, the systemd people are trying to replace a lot of things that worked well before, not just cryptsetup. My guess would be this is an attempt at embrace-extend-extinguish and I can only recommend to avoid systemd altogether. This group here is the original group for cryptsetup, the systemd version is an, apparently badly made, clone. Regards, Arno On Thu, Sep 21, 2017 at 18:28:34 CEST, Jerry Lowry wrote: > 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? > > ----------------------------------------------------------------------- > ---- > Jerold Lowry > Principal Network/Systems Engineer > Engineering Design Team (EDT), Inc. a HEICO company > 3423 NW John Olsen Pl > Hillsboro, Oregon 97124 (U.S.A.) > Phone: 503-690-1234 / 800-435-4320 > Fax: 503-690-1243 > Web: [1]www.edt.com > > > On 9/21/2017 12:25 AM, Michael Kjörling wrote: > > On 20 Sep 2017 15:38 -0700, from [2]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/sdb > > 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). > > > > Sep 20 14:19:53 jubilee systemd[1]: Starting Cryptography Setup for > /dev/mapper/testcui... > -- Subject: Unit [3]systemd-cryptsetup@-dev-mapper-testcui.service has > begun start-up > -- Defined-By: systemd > -- Support: [4]https://url.emailprotection.link/?aU9kur6wsNUi02sZK7jqbqHUDJAa-o4 > ToSDYQrs9syxvrrIdB1sQAdzV3HPUijEgCYM0mtOEY4w7RKS2IUkVivQ~~ > > At a minimum, run cryptsetup directly (not through systemd) with the > --debug flag and post back with the output thus obtained. > > References > > 1. http://www.edt.com/ > 2. mailto:jlowry@xxxxxxx > 3. mailto:systemd-cryptsetup@-dev-mapper-testcui.service > 4. https://url.emailprotection.link/?aU9kur6wsNUi02sZK7jqbqHUDJAa-o4ToSDYQrs9syxvrrIdB1sQAdzV3HPUijEgCYM0mtOEY4w7RKS2IUkVivQ~~ > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- A good decision is based on knowledge and not on numbers. -- Plato If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
