From owner-freebsd-geom@freebsd.org Sun Sep 9 21:00:15 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 EFA8D109E606 for ; Sun, 9 Sep 2018 21:00:14 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.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 90E7181466 for ; Sun, 9 Sep 2018 21:00:14 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 56071109E5F4; Sun, 9 Sep 2018 21:00:14 +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 43FA9109E5F0 for ; Sun, 9 Sep 2018 21:00:14 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD05A8145F for ; Sun, 9 Sep 2018 21:00:13 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1E5F910041 for ; Sun, 9 Sep 2018 21:00:13 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w89L0CkZ092678 for ; Sun, 9 Sep 2018 21:00:12 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w89L0CfE092671 for geom@FreeBSD.org; Sun, 9 Sep 2018 21:00:12 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201809092100.w89L0CfE092671@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: geom@FreeBSD.org Subject: Problem reports for geom@FreeBSD.org that need special attention Date: Sun, 9 Sep 2018 21:00:12 +0000 MIME-Version: 1.0 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: Sun, 09 Sep 2018 21:00:15 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 218679 | [geli] add a verify command 1 problems total for which you should take action. From owner-freebsd-geom@freebsd.org Tue Sep 11 16:18:23 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 0C7541095BD9 for ; Tue, 11 Sep 2018 16:18:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.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 9E2717DC16 for ; Tue, 11 Sep 2018 16:18:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 62F021095BD8; Tue, 11 Sep 2018 16:18:22 +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 51AD11095BD7 for ; Tue, 11 Sep 2018 16:18:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E03767DC13 for ; Tue, 11 Sep 2018 16:18:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 30F53269A4 for ; Tue, 11 Sep 2018 16:18:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w8BGILJU053153 for ; Tue, 11 Sep 2018 16:18:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w8BGILoC053152 for geom@FreeBSD.org; Tue, 11 Sep 2018 16:18:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: geom@FreeBSD.org Subject: [Bug 230246] GPT label mishandling Date: Tue, 11 Sep 2018 16:18:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: geom@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Tue, 11 Sep 2018 16:18:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230246 Andrey V. Elsukov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ae@FreeBSD.org --- Comment #2 from Andrey V. Elsukov --- For me all looks like I expected. What do you expected to see after these commands? --=20 You are receiving this mail because: You are the assignee for the bug.= 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 From owner-freebsd-geom@freebsd.org Sat Sep 15 19:18:23 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 B22821082773 for ; Sat, 15 Sep 2018 19:18:23 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 3D0DB9577C for ; Sat, 15 Sep 2018 19:18:23 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr1-x42c.google.com with SMTP id a108-v6so13498486wrc.13 for ; Sat, 15 Sep 2018 12:18:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Ox9cPall2BR9rOZ6u4E5qi9EN7hok0Zrjdq5qxhvPJo=; b=oWGv4A4lXzJTfQp1jjOQ8pmzrOrAdJi1Hwh8WLenxsagtGDQLXTO2S9CyDIuDwQGEm 1OakOm/0eY47fHsMgC4/7BeSbzAWMQwzMHnv12qf+mmRfZme/L+3XDYLEwR3JiNKz9WL 3JjSL81/0i0viz2jxDA8XufW+NmKRd0Ngl9dx2hzNOswVEC0EKjffb+ZKK3/WnCklLxC YtDultWLh3zjjso/ZlyRkZDR93c3DGucN8ei767k/eLpmvozq5xYVuDcKXST6jQbFtvk 61Efy3y5eusZmR8O+mM4vYz63geOnfa0G83BdX5JRAvZSp03Q35uu5jAByfJOHgqYgqg FWrg== X-Gm-Message-State: APzg51D8bR98F0JLZ66F5Vk8RTAh/uv1C4CUDfOuBDkhbsuSOD7221vT Czk1208aTly0OQPiA+zzUk7AvTyO X-Google-Smtp-Source: ANB0VdYDrluexJXy2DX3HjgW3/SowDM0SXAfD6RPrcaAc6CezGHo80ytn0BLH5L6MUmQFW3fjDEwjQ== X-Received: by 2002:adf:9a46:: with SMTP id z64-v6mr13238086wrb.109.1537039101756; Sat, 15 Sep 2018 12:18:21 -0700 (PDT) Received: from gumby.homeunix.com ([2.125.48.184]) by smtp.gmail.com with ESMTPSA id a184-v6sm2099942wmh.41.2018.09.15.12.18.20 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 15 Sep 2018 12:18:21 -0700 (PDT) Date: Sat, 15 Sep 2018 20:18:19 +0100 From: RW To: freebsd-geom@freebsd.org Subject: Re: geli - why do I need a keyfile Message-ID: <20180915201819.50ac10a3@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 19:18:23 -0000 On Fri, 14 Sep 2018 17:55:58 -0700 Lee Brown wrote: > I want to create a geli provider as authentication only, no password, > no encryption. I do: ... > Instead: > # echo " " > /tmp/key > solves that issue, but I still don't get why I even need a key file > with -e NULL? Because HMAC itself needs an encrypted secret key, otherwise anyone could write to the device without it being detectable. Without a securely entered passphase, or a passfile on removable media, HMAC doesn't provide any authentication, it just detects bitrot and naive attempts to modify the filesystem. From owner-freebsd-geom@freebsd.org Sat Sep 15 19:37:49 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 874011082FE3 for ; Sat, 15 Sep 2018 19:37:49 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 0D9EB95FEF for ; Sat, 15 Sep 2018 19:37:48 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x234.google.com with SMTP id j198-v6so7588231ita.0 for ; Sat, 15 Sep 2018 12:37:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=0NZYoNwmEqKP3CvFW+q7aug9gkdNyM/lhDlrMAtTL/E=; b=q9LukD4ys0J6LF75ALu62t/XHqr9ZS6+8qhR6aNSdKFrk3noC5YSocCQw2XoOTZUZU ujX4SbxnZU7K+tG226gd3K3wiA0PH8oUeva49ne2rHWDDCWMOWeLN8CgHEZzR9M3HPWe ray89UcMQtl7A/Jn7VHXaw4/ndeGTK+3BLhWgkKult4ZAo+8N9B1cLtAeqQub/BGfG3S Dhruk8x0kuOb47mLxREp3fFfEecfe6XkFRKp32USMY2u3PVfp5VSqLKSPy/65OW1Vldc GIzC4Dg6lsk7MDfjXTISixtfZj/QwAdlCjMNG2MneAvbMhOVuWqsgzLMVv881ME0gg8H 4e6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=0NZYoNwmEqKP3CvFW+q7aug9gkdNyM/lhDlrMAtTL/E=; b=ik4vthANtdCYqsfj2WVln86aoTAGnyFfGPNx4mocqRnLK5CMLzncj8+wvJxsI4oZzP 61B6bSKeuFmtjtfE1HaILIU3E+RPKwbC05klLMr7ijF2GBJOu7Hxh6EHXoopYppuGxyR +0gAkdRyvEmToedcB51se9xA2w+cukKduQerhkCCx+YFSc4vIudv0rgIAdBmonBPx5l+ xb9CVYK7L6R14rA61kE7yJPDJrp69BQJXFmJuGCx2DMB4uk+KHWzmLSK9tHwNnCg8NUy 5jb0F6GBq3VAiDzKVdm8nC3BDhjIvXWrLwJf7SrQq/sgvxQJtqK6gmvd8Zh4zwUPfsqf Fqsw== X-Gm-Message-State: APzg51AfJpevVJE/gdgIp1vHvOyFyCDO6fynuMtJhr9Fb+rKInr1opBi pWHp4Rvi0AITXXHSYcb7YIZre06cU6WQY+eAXZQPVOspiSU= X-Google-Smtp-Source: ANB0VdYFf96+bQZYPjsXu3nuSwYp3Ku1uksVt6K3Jof2DNbVPN4ZZz5SM5IPN5nwjQQJNuBuOr7mWchgRwCdDlrZEr4= X-Received: by 2002:a24:da47:: with SMTP id z68-v6mr7334990itg.59.1537040267402; Sat, 15 Sep 2018 12:37:47 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:d025:0:0:0:0:0 with HTTP; Sat, 15 Sep 2018 12:37:46 -0700 (PDT) In-Reply-To: <20180915201819.50ac10a3@gumby.homeunix.com> References: <20180915201819.50ac10a3@gumby.homeunix.com> From: Lee Brown Date: Sat, 15 Sep 2018 12:37:46 -0700 Message-ID: Subject: Re: geli - why do I need a keyfile To: freebsd-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 19:37:49 -0000 On Sat, Sep 15, 2018 at 12:18 PM, RW via freebsd-geom < freebsd-geom@freebsd.org> wrote: > On Fri, 14 Sep 2018 17:55:58 -0700 > Lee Brown wrote: > > > I want to create a geli provider as authentication only, no password, > > no encryption. I do: > ... > > Instead: > > # echo " " > /tmp/key > > solves that issue, but I still don't get why I even need a key file > > with -e NULL? > > Because HMAC itself needs an encrypted secret key, otherwise anyone > could write to the device without it being detectable. > > Without a securely entered passphase, or a passfile on removable media, > HMAC doesn't provide any authentication, it just detects bitrot and > naive attempts to modify the filesystem. > > Thanks for the explanation, in retrospect I should have read up on HMAC. That's precisely my use-case data integrity verification only. I'm building a RAID1 gmirror on top of 2 geli providers, so if a disk rots it's detected. Now I just need to test how the gmirror reacts when the underlying geli faults. Much appreciated -- lee