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 49593740040 for ; Mon, 4 Nov 2024 18:32:43 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=zasADrQ1LLfj/hfCgV8fOgbay82PyFC1KMtnqQRUX9o=; c=relaxed/simple; d=groups.io; h=MIME-Version:From:Date:Message-ID:Subject:To:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Resent-Date:Resent-From:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type; s=20240830; t=1730745162; v=1; x=1731004361; b=eLsdMy83jzUckeT2HG3dg20Fb7csaTJzbGbJqqIezoTlhrFaBvcXk6UfVpeqAPl6UbIrtwvs LRtIpJrf5ToJP1pkSPGgn48kqqVQFoDqSnnLcN9tH5O0hXlabprlW9ToZFC12UevfqxdnGiNg7h 2Tvl9lVqPWyiQX5C5wx1srKO270ZUgmqOtS1vfPxa1Ek7/KUIxwsCu9NlXKm+0r8uD1Ahgv9ks3 HBE8buyTryQJ1arSgonshLwkEmKpRbDbFNl0GpNQX4yxrS8A4ixYJYlW6tVCsjoM3WVhOa5KxbK r7wneQotmpu4IyIdCIvObF37DcE7ClwFEm+S5hNZ4zWaQ== X-Received: by 127.0.0.2 with SMTP id p5HUYY7687511xrkTEE3xn28; Mon, 04 Nov 2024 10:32:41 -0800 X-Received: from mail-lj1-f169.google.com (mail-lj1-f169.google.com [209.85.208.169]) by mx.groups.io with SMTP id smtpd.web10.3063.1730745160580368762 for ; Mon, 04 Nov 2024 10:32:40 -0800 X-Received: by mail-lj1-f169.google.com with SMTP id 38308e7fff4ca-2fb4af0b6beso68384471fa.3 for ; Mon, 04 Nov 2024 10:32:40 -0800 (PST) X-Gm-Message-State: xQZEWNQgtWeqwX03jO1JqmL7x7686176AA= X-Google-Smtp-Source: AGHT+IFuIkMNjkUr8l86BZLGrrsibPamryQ+vliZDNrkRWn4IsWZ6s+r+N1K4ykMLlsqR/4cbD1Ot4EMREM4YiPiBYo= X-Received: by 2002:a2e:be0d:0:b0:2fa:d4ef:f234 with SMTP id 38308e7fff4ca-2fedb794b44mr89908331fa.1.1730745156864; Mon, 04 Nov 2024 10:32:36 -0800 (PST) MIME-Version: 1.0 From: "Rafael Machado" Date: Mon, 4 Nov 2024 15:32:14 -0300 Message-ID: Subject: [edk2-devel] Question about OS to UEFI DXE module communication To: devel@edk2.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 Resent-Date: Mon, 04 Nov 2024 10:32:40 -0800 Resent-From: rafaelrodrigues.machado@gmail.com Reply-To: devel@edk2.groups.io,rafaelrodrigues.machado@gmail.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: Content-Type: multipart/alternative; boundary="00000000000045979206261a82e1" X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20240830 header.b=eLsdMy83; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 45.79.224.7 as permitted sender) smtp.mailfrom=bounce@groups.io --00000000000045979206261a82e1 Content-Type: text/plain; charset="UTF-8" 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] -=-=-=-=-=-=-=-=-=-=-=- --00000000000045979206261a82e1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello everyone.
I have a question.

I need one OS agent (windows application)=C2=A0 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 s= ome knowledge about other possible options, which are safer than=C2=A0using= UEFI variables.

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

Any idea about= other approaches=C2=A0I can follow to have this "communication channe= l" between OS and the BIOS (data processed at the next boot)

Thanks
Rafael Machado
_._,_._,_
Groups.io Links:

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

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

_._,_._,_
--00000000000045979206261a82e1--