From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 067EDC4332F for ; Mon, 28 Nov 2022 01:35:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229602AbiK1Bf2 (ORCPT ); Sun, 27 Nov 2022 20:35:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47798 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229475AbiK1Bf2 (ORCPT ); Sun, 27 Nov 2022 20:35:28 -0500 Received: from cavan.codon.org.uk (cavan.codon.org.uk [176.126.240.207]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 73A69AE65; Sun, 27 Nov 2022 17:35:24 -0800 (PST) Received: by cavan.codon.org.uk (Postfix, from userid 1000) id 15B6A424A2; Mon, 28 Nov 2022 01:35:23 +0000 (GMT) Date: Mon, 28 Nov 2022 01:35:23 +0000 From: Matthew Garrett To: "Jason A. Donenfeld" Cc: linux-efi@vger.kernel.org, linux-crypto@vger.kernel.org, patches@lists.linux.dev, linux-kernel@vger.kernel.org, ardb@kernel.org Subject: Re: [PATCH v3 2/5] efi: stub: use random seed from EFI variable Message-ID: <20221128013523.GA6780@srcf.ucam.org> References: <20221122020404.3476063-1-Jason@zx2c4.com> <20221122020404.3476063-3-Jason@zx2c4.com> <20221127211244.GB32253@srcf.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Mon, Nov 28, 2022 at 02:12:38AM +0100, Jason A. Donenfeld wrote: > Yea this is a bummer. During my first attempt at this, I actually > overwrote the whole thing with zeros and then deleted it. But Ard > pointed out that this doesn't make a difference anyway. But, as it turns > out, that's more or less the same thing that happens with seed files on > SSDs (nobody calls fstrim after overwriting a seed file). So at the very > least, it's no worse? Anyone with the ability to directly read the flash variable store is almost certainly in a position to do worse things, so I wouldn't worry about it.