public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kishore, Ajay via groups.io" <Ajay.Kishore=dell.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] Clarification on Missing "Secure Boot Runtime Services Tests" in SCT
Date: Mon, 9 Jun 2025 04:05:42 +0000	[thread overview]
Message-ID: <PH7PR19MB700221FEBADCDC5919D44367E86BA@PH7PR19MB7002.namprd19.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

Hello,
I am currently working with the UEFI SCT tool and have encountered an issue related to the Secure Boot validation. Specifically, I am unable to locate the "Secure Boot Runtime Services Tests" under the Services → Runtime Services Test section in the test menu.
Could you please clarify the following:

  *   Are these Secure Boot-related test cases implemented in the current public version of the SCT tool?
  *   If so, is there a specific version, branch, or configuration required to access them?
  *   Are there any known prerequisites or procedures that must be followed to enable these tests?
Your guidance would be highly appreciated, as it will help me ensure proper coverage for Secure Boot validation in our test workflows.

Looking forward to your response.

Thanks.
Ajay Kishore


Internal Use - Confidential


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121410): https://edk2.groups.io/g/devel/message/121410
Mute This Topic: https://groups.io/mt/113565405/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 8136 bytes --]

                 reply	other threads:[~2025-06-10  6:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH7PR19MB700221FEBADCDC5919D44367E86BA@PH7PR19MB7002.namprd19.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox