From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from v1.tansi.org (mail.tansi.org [84.19.178.47]) by mail.server123.net (Postfix) with ESMTP for ; Mon, 22 Jun 2020 09:33:41 +0200 (CEST) Received: from gatewagner.dyndns.org (81-6-44-245.init7.net [81.6.44.245]) by v1.tansi.org (Postfix) with ESMTPA id 0CDA414022A for ; Mon, 22 Jun 2020 09:33:39 +0200 (CEST) Date: Mon, 22 Jun 2020 09:33:40 +0200 From: Arno Wagner Message-ID: <20200622073340.GA9075@tansi.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dm-crypt] FAQ 2.2 Scenario (1) - clarification concerning "encrypted root" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On Sun, Jun 21, 2020 at 22:20:21 CEST, moreejt@yahoo.com wrote: > I think I can get secure boot working so that the system will not boot > unless the kernel and initrd match sign d files > That would be an option, yes. Regards, Arno -- 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