From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web11.5579.1687175472268259001 for ; Mon, 19 Jun 2023 04:51:12 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=BOJGysRm; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1687175471; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ITDTv7hbHOuQagT2hdpnnAU5zL87tudP8+qq60AwbwI=; b=BOJGysRmcG9/Uya7WmjGbATtR2Q8mwIZk2aI1gzdT6VbYoBxFUKceW2W1yl+nxZOWk9qik ryMFzRp1xAXRVTQ51w6nXBb0SGQjX89PpxgnWW8dCOQz5A7b5n4DXuxKHIqC+pTkgdmGBQ lKNx/x2qRJHy7qBJj4YtlXR54H0kNJo= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-668-cRZPNX7hPi6B0HfMo0s_Tg-1; Mon, 19 Jun 2023 07:51:10 -0400 X-MC-Unique: cRZPNX7hPi6B0HfMo0s_Tg-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 946598030AC; Mon, 19 Jun 2023 11:51:09 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.194.241]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3AD8A2026D49; Mon, 19 Jun 2023 11:51:09 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 28B2C18003AB; Mon, 19 Jun 2023 13:51:07 +0200 (CEST) Date: Mon, 19 Jun 2023 13:51:07 +0200 From: "Gerd Hoffmann" To: devel@edk2.groups.io, chat@joursoir.net Cc: Ard Biesheuvel , Jiewen Yao , Jordan Justen , Rebecca Cran Subject: Re: [edk2-devel] [PATCH] OvmfPkg/README: Document Secure Boot Message-ID: References: <1765BEFF9799FDDB.7352@groups.io> <20230616005155.275150a1@reeva> MIME-Version: 1.0 In-Reply-To: <20230616005155.275150a1@reeva> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jun 16, 2023 at 12:51:55AM +0400, Joursoir wrote: > +cc to maintainers > > On Sat, 3 Jun 2023 01:44:40 +0400 > "Joursoir" wrote: > > > Add the new section for Secure Boot. > > > > Signed-off-by: Alexander Goncharov > > --- > > OvmfPkg/README | 36 ++++++++++++++++++++++++++++++++++++ > > 1 file changed, 36 insertions(+) > > > > diff --git a/OvmfPkg/README b/OvmfPkg/README > > index 0a408abf01..e106e19818 100644 > > --- a/OvmfPkg/README > > +++ b/OvmfPkg/README > > @@ -120,6 +120,42 @@ $ OvmfPkg/build.sh -a X64 qemu -cdrom > > /path/to/disk-image.iso To build a 32-bit OVMF without debug messages > > using GCC 4.8: $ OvmfPkg/build.sh -a IA32 -b RELEASE -t GCC48 > > > > +=== Secure Boot === > > + > > +Secure Boot is a security feature that ensures only trusted and > > digitally +signed software is allowed to run during the boot process. > > + > > +* In order to support Secure Boot, OVMF must be built with the > > + "-D SECURE_BOOT_ENABLE" option. Also note that you need either a read-only varstore or SMM support, otherwise it is trivial to bypass secure boot by writing directly to flash varstore. > > +* By default, OVMF is not shipped with any SecureBoot keys installed. > > The user > > + need to install them with "Secure Boot Configuration" utility in > > the firmware > > + UI, or enroll the default UEFI keys using the > > OvmfPkg/EnrollDefaultKeys app. + Alternatively use https://gitlab.com/kraxel/virt-firmware take care, Gerd