public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rafael Machado" <rafaelrodrigues.machado@gmail.com>
To: devel@edk2.groups.io
Subject: [edk2-devel] Question about OS to UEFI DXE module communication
Date: Mon, 4 Nov 2024 15:32:14 -0300	[thread overview]
Message-ID: <CACgnt7-7n0hzHwx7V8FvtUbg7qcWSmKTk5p+0Q28S=cVeJK6xA@mail.gmail.com> (raw)

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

Hello everyone.
I have a question.

I need one OS agent (windows application)  sending some data to a UEFI DXE
module, which will only process that data at the next boot.

I know the first thing that comes to mind in this case is to use UEFI
variables, but I would like to know if you guys can share some knowledge
about other possible options, which are safer than using UEFI variables.

In case I use UEFI variables here I will not be that comfortable with
having a variable available at boot time and runtime, which can be
easily accessed from the OS. This will create the need of several controls
and logic at the dxe driver to make sure the data I am receiving is
reliable, it is not a replay attack and other security related scenarios.

Any idea about other approaches I can follow to have this "communication
channel" between OS and the BIOS (data processed at the next boot)

Thanks
Rafael Machado


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120711): https://edk2.groups.io/g/devel/message/120711
Mute This Topic: https://groups.io/mt/109391181/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: 1863 bytes --]

                 reply	other threads:[~2024-11-04 18:32 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='CACgnt7-7n0hzHwx7V8FvtUbg7qcWSmKTk5p+0Q28S=cVeJK6xA@mail.gmail.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