All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Basics
Date: Wed, 30 Sep 2015 17:00:03 +0200	[thread overview]
Message-ID: <20150930150003.GA21363@tansi.org> (raw)
In-Reply-To: <20150930121626.GA25001@manjaro.chello.hu>

You are using /dev/sdb1 as your keyfile. cryptsetup
has a compiled-in size limit on keyfiles, which is
per default 8kB. If /dev/sdb1 is larger, you get the
error you observe.

Regards,
Arno


On Wed, Sep 30, 2015 at 14:16:26 CEST, Mike Nagie wrote:
> Why is this happening? I'm trying to create encrypted luks partition 
> with a keyfile.
> 
> cryptsetup luksFormat /dev/sda2 /dev/sdb1
> 
> WARNING!
> This will overwrite data on /dev/sda2 irrevocably.
> 
> Are you sure? (Type uppercase yes): YES
> Maximum keyfile size exceeded.
> cryptsetup luksFormat /dev/sda2 /dev/sdb1 10.54s user 4.55s system 83% 
> cpu 18.1
> 
> (and sometimes: command failed with code 22 invalid argument)
> 
> cryptsetup open --type luks /dev/sda2 home -d /dev/sdb1
> Maximum keyfile size exceeded.
> cryptsetup open --type luks /dev/sda2 home -d /dev/sdb1  10.43s user 
> 4.64s system 99% cpu 15.103 total
> -- 
> You are so lucky!
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
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

  reply	other threads:[~2015-09-30 15:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 17:33 [dm-crypt] Basics Mike Nagie
2015-09-25 17:55 ` Mistave
2015-09-25 19:44 ` Michael Kjörling
2015-09-25 19:48   ` Michael Kjörling
2015-09-25 21:48   ` Mike Nagie
2015-09-25 22:24     ` Michael Kjörling
2015-09-25 23:03       ` Arno Wagner
2015-09-26  7:14       ` Mike Nagie
2015-09-26  7:32         ` Mistave
2015-09-26  8:27           ` Mike Nagie
2015-09-26 10:24             ` Mistave
2015-09-26 13:12         ` Robert Nichols
2015-09-26 15:38         ` Michael Kjörling
2015-09-27 11:08           ` Mike Nagie
2015-09-27 13:47             ` Michael Kjörling
2015-09-27 14:08             ` Arno Wagner
2015-09-27 14:15               ` Michael Kjörling
2015-09-27 14:34                 ` Arno Wagner
2015-09-27 16:12                 ` Mike Nagie
2015-09-27 16:51                   ` Michael Kjörling
2015-09-27 18:20                     ` Mike Nagie
2015-09-27 18:55                   ` Heinz Diehl
2015-09-27 18:57                     ` Heinz Diehl
2015-09-27 21:50                     ` Mike Nagie
2015-09-27 22:08                       ` Michael Kjörling
2015-09-28 20:11                       ` Heinz Diehl
2015-09-29 10:52                         ` Mike Nagie
2015-09-30 12:16                         ` Mike Nagie
2015-09-30 15:00                           ` Arno Wagner [this message]
2015-09-30 17:49                             ` Mike Nagie
2015-09-30 19:27                               ` Arno Wagner
2015-09-30 15:40                           ` Heinz Diehl
2015-09-25 20:12 ` Arno Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150930150003.GA21363@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.