From owner-freebsd-geom@freebsd.org Sat Sep 15 00:56:05 2018 Return-Path: Delivered-To: freebsd-geom@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14A041098278 for ; Sat, 15 Sep 2018 00:56:05 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8C9047877A for ; Sat, 15 Sep 2018 00:56:04 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4D3B21098277; Sat, 15 Sep 2018 00:56:04 +0000 (UTC) Delivered-To: geom@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1301D1098276 for ; Sat, 15 Sep 2018 00:56:04 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8676878779 for ; Sat, 15 Sep 2018 00:55:59 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x229.google.com with SMTP id p129-v6so4771127ite.3 for ; Fri, 14 Sep 2018 17:55:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=yDU8LRKD4dCQPGoY+78/TE2bgdjgTS/ftF48xoBcduQ=; b=QC2X3NZY9Q7W42d3lpPwR3UPTte/UAXNEkdZesziO+gR7Uxz3ZkxinR4fDrF+ThAlF lrD1+STki3cOkfCuP/EwJf2w1efyDCHIcJHi845lpxI2J1h6LNFuGXAYWs+QEiZ8W8Pa SdkQW6pkLAbndAFWgf/lW0r26W1XWLc8tB6Iek6d8diuPBN9TbOd9fSzTfjK1L/tGHvX vQMTaWYbxZ9295inKLn/0qKLVct2IQjj68cVLSjZ8SlY0RCC6t+vW1XxZpNhA1Dh4vTj 5GY6RzNu466htWoIbVWoVetLIsokdu+/o/m67dAtaakbYUSyBxvqfLv7CLaBPY4CXD/1 DrAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=yDU8LRKD4dCQPGoY+78/TE2bgdjgTS/ftF48xoBcduQ=; b=RWV2EjHe/wcf8wpuw0dj22tloWsxNYPd3ICV38+7t/U0Mu86ZQt4RtiqDluNDSmZyv gYdlb7o6aHTJruHBR6SQWAHVoSxVP2aHscE+ZX7Exp3CFDN3tV+RP3Gsr9dEQi4aQ4M9 HZUb+tmHk0GHem/JXNSLuZjYrWVrh2+HU1k9wizkEukIMTTKrvMMVmaLyLH0K8Lmd/j1 I1WoFDbcUw2F6vY0yA7h0zcMr7KAMra6m4jVAut9mCbyXjlU2rkqesjSE8nWRIBw4HYQ tMK3tP727j801CPuwBi29LMbb7y8eHg4mL8AnOmlsqCzWgqDb7pl0QaQHaCqXj735jUF UllQ== X-Gm-Message-State: APzg51AD1DV7mvmAVoxAcWWstOL0c4v5GV/EC6Xh2wRUIXTIGWUXdY/8 qABFF085zo+YmMAB+sQp9/G2gJJidJ4WWuQzpS3k2oTYXKw= X-Google-Smtp-Source: ANB0VdbwKy0+tJNKgR13K5HSEN6kHZLB7cEmieNwFzfT7ek4q8CiHiGKIbqKGmLd3UBQuBFD0d8d5ZRrp1s4lgtcZf8= X-Received: by 2002:a24:da47:: with SMTP id z68-v6mr4736731itg.59.1536972958942; Fri, 14 Sep 2018 17:55:58 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:d025:0:0:0:0:0 with HTTP; Fri, 14 Sep 2018 17:55:58 -0700 (PDT) From: Lee Brown Date: Fri, 14 Sep 2018 17:55:58 -0700 Message-ID: Subject: geli - why do I need a keyfile To: geom@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2018 00:56:05 -0000 I want to create a geli provider as authentication only, no password, no encryption. I do: # geli init -a HMAC/SHA256 -e NULL -P -s 4096 geli: No key components given. instead I tried # touch /tmp/key # geli init -a HMAC/SHA256 -e NULL -P -s 4096 -k /tmp/key test it # geli attach -p -k /tmp/key but during boot that fails with with "Cannot find key file size for /boot/keys/key" # ls -l /boot/keys/key -rw-r--r-- 1 root wheel 0 Sep 14 11:44 /boot/keys/key Instead: # echo " " > /tmp/key solves that issue, but I still don't get why I even need a key file with -e NULL? I'm fine if this is a corner case to be ignored (keyfile required), but I do think the attach with a zero length key file should fail if it's not going to work at boot time. It should be consistent one way or another. Let me know if I should file a bug report and which way it should be filed (ie zero length keyfile attach should fail, or zero length keyfile should work at boot) Thanks -- lee