https://slack.com/
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Kevin D
Davis
Sent: Friday, November 16, 2018 9:35 AM
To: stephano ; edk2-devel@lists.01.org
Subject: Re: [edk2] [edk2-announce][RFC] Collaboration Software
[mailto:rafaelrodrigues.mach...@gmail.com]
Sent: Monday, October 15, 2018 12:17 PM
To: Zimmer, Vincent
Cc: edk2-devel@lists.01.org
Subject: Re: [edk2] Where to find the fix for security issue id 686
Hi Vincent
Thanks for the answer.
The problem is that when I try to access this link I have
You can find reference to patches via the advisory entry
"31. EDK II TIANOCOMPRESS BOUNDS CHECKING ISSUES" advisory entry
https://edk2-docs.gitbooks.io/security-advisory/content/edk-ii-tianocompress-bounds-checking-issues.html
has an embedded link to
;> Ard Biesheuvel
>> Sent: Wednesday, September 12, 2018 6:22 AM
>> To: edk2-devel@lists.01.org
>> Cc: Ni, Ruiyu ; Zimmer, Vincent
>> ; Dong, Eric ; Andrew
>> Fish ; ag...@suse.de; Richardson, Brian
>> ; Kinney, Michael D
>> ; Laszlo Ersek ; Zeng,
>> St
URL? I keep getting this error message: 404
- This is not the web page you are looking for.
Thanks,
Tapan
-Original Message-
From: Zimmer, Vincent [mailto:vincent.zim...@intel.com]
Sent: Wednesday, October 18, 2017 5:58 PM
To: Shah, Tapan <tapands...@hpe.com>; edk2-devel@lists.01.
For #1.
Typically the OS. The platform already has its own PlatformRecovery.
For #2
There's a prototype available to UEFI members that was used to vet some of the
changes during UEFI 2.7 deliberations at
https://github.com/UEFI/uefiproto/tree/master/OsRecovery
You can request access as a UEFI
Good points on the use case. I'll take a look.
Thanks again
Vincent
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Marvin
Häuser
Sent: Wednesday, September 20, 2017 2:26 PM
To: edk2-devel@lists.01.org
Cc: Zimmer, Vincent <vincent.
Marvin:
Thanks for all of the feedback on the SPI items from the most recent UEFI PI
spec. We're updating the PI spec now responsive to your findings and these
corrections will be reflected in an upcoming errata.
Sorry for the delayed response to you on the findings. I'll follow up w/ UEFI
Yes. For IPV4 TFTP-based PXE the wire protocol adheres to the PXE 2.1
specification with some errata that supercedes that frozen document found under
section "E.4.20 PXE 2.1 specification wire protocol clarifications" of the UEFI
2.6 specification. For IPV6 PXE-style TFTP boot the wire
9 matches
Mail list logo
