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.