From: "Eugene Khoruzhenko" <sun2sirius@gmail.com>
To: Paulo Henrique Lacerda de Amorim
<phlamorim@riseup.net>,devel@edk2.groups.io
Subject: Re: [edk2-devel] Interpretation of specification
Date: Mon, 25 Nov 2019 22:08:43 -0800 [thread overview]
Message-ID: <17919.1574748523014243625@groups.io> (raw)
In-Reply-To: <8bcef1fa-c8a4-2b1b-dcd3-adb45cc7254e@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
No, we do not have access to the manufacturer's PK/KEK, so I created my own keys and certs. Theoretically, to debug this you can send me the GUID/Name and payload you are trying to write, I can check if I can write your variable with my tool and signing. Then I could look at your code and compare with mine and see why it does not work. If your code works on my devices, maybe the specific model you have has some issue? BTW, try the other vendors, like Lenovo and HP. I only cannot promise when I will be able to get to it with holidays approaching and many other things to do...
[-- Attachment #2: Type: text/html, Size: 588 bytes --]
next prev parent reply other threads:[~2019-11-26 6:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 17:12 Interpretation of specification phlamorim
2019-10-24 12:33 ` [edk2-devel] " Laszlo Ersek
2019-11-15 18:51 ` phlamorim
2019-11-15 21:32 ` Laszlo Ersek
2019-11-23 4:59 ` Eugene Khoruzhenko
2019-11-23 13:08 ` Paulo Henrique Lacerda de Amorim
2019-11-26 6:08 ` Eugene Khoruzhenko [this message]
2019-11-26 15:22 ` Paulo Henrique Lacerda de Amorim
2020-01-03 19:52 ` Eugene Khoruzhenko
2020-01-04 17:17 ` Paulo Henrique Lacerda de Amorim
2020-01-07 18:13 ` Eugene Khoruzhenko
2020-01-08 11:24 ` Laszlo Ersek
2020-01-08 19:13 ` James Bottomley
2020-01-09 17:17 ` Laszlo Ersek
2020-01-09 17:20 ` James Bottomley
2020-01-10 10:55 ` Laszlo Ersek
2020-01-10 16:04 ` James Bottomley
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=17919.1574748523014243625@groups.io \
--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