From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail05.groups.io (mail05.groups.io [45.79.224.7]) by spool.mail.gandi.net (Postfix) with ESMTPS id 66C687803CD for ; Tue, 21 Jan 2025 13:49:53 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=gxcQV8OGYPHQxdbOA+Xe0vWMKA74oLwSF3B+j1cvxSc=; c=relaxed/simple; d=groups.io; h=Subject:To:From:User-Agent:MIME-Version:Date:Message-ID:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type; s=20240830; t=1737467393; v=1; x=1737726591; b=wvvWb6PoFGGmARLySULoHrdvNamLA5eB8vueDPtJ3yomkZH98xBbsdcimHV3Lnm7c6VW9gcC rOs8+NPaFherCf4F4gLisyCVeL9lva/HQzMtqsa28zV5iwMoEPYaloeraUxJ59zy/rdX70av/Dp H1ZI+30Jol2zh7taD21C3fNd+WSJf2t2IIQVBBAvVaL6Tc8alYwUMlLHx661chnW/EftzZAuCgy q0sVj2gG5JiPH1qtupuXVLzSsaBRIRst4gxi5zIjsceUcNII5llUfKD0d8nuWzE4rBPfFkyzG0W UJKt0sIuJpmTdpbyOzIdzN7ULvYd1WW/Rj55GfWrMSuiQ== X-Received: by 127.0.0.2 with SMTP id b9uRYY7687511xG1G9HBHjp7; Tue, 21 Jan 2025 05:49:51 -0800 Subject: [edk2-devel] Secure Boot verification To: devel@edk2.groups.io From: "xpahos via groups.io" X-Originating-Location: Moscow, RU (93.158.190.111) X-Originating-Platform: Mac Chrome 126 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Tue, 21 Jan 2025 05:49:46 -0800 Message-ID: <5puX.1737467386062515435.kHC1@groups.io> Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,xpahos@gmail.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: SDgPATYsO161MHILqkwyIpoax7686176AA= Content-Type: multipart/alternative; boundary="HjOsiwvhv1JfkoXlJmip" X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20240830 header.b=wvvWb6Po; dmarc=pass (policy=none) header.from=groups.io; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 45.79.224.7 as permitted sender) smtp.mailfrom=bounce@groups.io --HjOsiwvhv1JfkoXlJmip Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, I found a presentation from https://uefi.org/sites/default/files/resources/= Understanding%20UEFI%20Testing%20Webinar_Final_1.30.pdf that briefly mentio= ns UEFI SCT. As I see here https://github.com/tianocore/edk2-test/blob/3605= beb86128ba31ae2719f9251c2fb22f6e588e/uefi-sct/Doc/TestCaseSpec/04_Services_= Runtime_Services_Test.md the SecureBootState test can be used to test Secur= e Boot behaviour. But I can't find any tests for this in the source tree. M= aybe I'm looking in the wrong place? I would like to be able to verify Secure Boot behaviour in pre-commit tests= . Now I'm thinking about implementing such a feature, but in a slightly dif= ferent way. I think I need to add the code to the main edk2 branch, because= it becomes impossible to verify the correct behaviour when Secure Boot req= uires a signed binary and the binary has an incorrect signature because the= EFI application will simply not be able to boot and return some result/log= it. Maybe there is some out-of-the-box solution and I'm doing something wr= ong? -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#121033): https://edk2.groups.io/g/devel/message/121033 Mute This Topic: https://groups.io/mt/110733213/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- --HjOsiwvhv1JfkoXlJmip Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Hello,
 
I found a presentation from https://uefi.org/sites/default/files/resou= rces/Understanding%20UEFI%20Testing%20Webinar_Final_1.30.pdf that briefly m= entions UEFI SCT. As I see here https://github.com/tianocore/edk2-test/blob= /3605beb86128ba31ae2719f9251c2fb22f6e588e/uefi-sct/Doc/TestCaseSpec/04_Serv= ices_Runtime_Services_Test.md the SecureBootState test can be used to test = Secure Boot behaviour. But I can't find any tests for this in the source tr= ee. Maybe I'm looking in the wrong place?
I would like to be able to verify Secure Boot behaviour in pre-commit = tests. Now I'm thinking about implementing such a feature, but in a slightl= y different way. I think I need to add the code to the main edk2 branch, be= cause it becomes impossible to verify the correct behaviour when Secure Boo= t requires a signed binary and the binary has an incorrect signature becaus= e the EFI application will simply not be able to boot and return some resul= t/log it. Maybe there is some out-of-the-box solution and I'm doing somethi= ng wrong?
_._,_._,_
Groups.io Links:

=20 You receive all messages sent to this group. =20 =20

View/Reply Online (#121033) | =20 | Mute= This Topic | New Topic
Your Subscriptio= n | Contact Group Owner | Unsubscribe [rebecca@openfw.io]

_._,_._,_
--HjOsiwvhv1JfkoXlJmip--