Re: [edk2-devel] pixiefail

2024-01-24 Thread vincent zimmer
I agree on your sentiment about Bugzilla (bz) not being ideal for this. This space has been a multi-year journey from usrt-based tickets, bespoke advisories, bz, etc into today's world of tianocore infosec, tianocore as its own CVE Naming Authority (CNA) and working to leverage the extant features

Re: [edk2-devel] purpose of EFI_LOCK

2023-05-05 Thread vincent zimmer
Random and tl;dr fun friday fact. You can see the efi locks replaced w/ spinlocks in https://github.com/tianocore/edk2-staging/tree/MpNetworkStack to support the use case described in https://uefi.org/sites/default/files/resources/7_Maciej%20Vincent_INTEL_network%20stack%20performance.pdf. These ch

Re: [edk2-devel] Clarification of Memory management in PEI phase

2022-06-23 Thread vincent zimmer
sounds like a good idea. As a next step, perhaps a candidate activity for https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Code-First-Process in anticipation of future inclusion in PI? Vincent On Wed, Jun 22, 2022 at 2:41 PM Brian J. Johnson wrote: > > Andrew, > > Yes, adding a new

Re: [edk2-devel] Build failure

2022-03-08 Thread Vincent Zimmer
This surprised me. Maybe edksetup.sh can do something like "nasm -v" and flag this compat issue? I used the following to update my Debian-based OS's like Ubuntu (bare-metal, WSL, etc). wget http://www.nasm.us/pub/nasm/releasebuilds/2.15.05/nasm-2.15.05.tar.bz2 tar xfj nasm-2.1

Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

2021-06-29 Thread Vincent Zimmer
FYI For IPv6, the TFTP-based network boot process (i.e., pxe) is called Netboot6 & detailed in "24.3.1 Netboot6"/" 24.3.1.2 IPv6-based PXE boot", and for IPV4 PXE we also curate changes/clarifications in "E.4.20 PXE 2.1 specification wire protocol clarifications", all of which are found in http

Re: [edk2-devel] [edk2-non-osi] [PATCH V3 0/1] Add Intel® Management Engine Firmware Binaries for 2nd Generation Intel® Xeon®

2020-02-10 Thread Vincent Zimmer
Reviewed by: vincent zimmer -Original Message- From: devel@edk2.groups.io On Behalf Of Desimone, Nathaniel L Sent: Monday, February 10, 2020 3:53 PM To: devel@edk2.groups.io Cc: Oram, Isaac W ; Zimmer, Vincent Subject: [edk2-devel] [edk2-non-osi] [PATCH V3 0/1] Add Intel® Management

Re: [edk2-devel] [tianocore-docs EDK_II_Secure_Coding_Guide PATCH] Add Appendix: Threat Mode for EDK II.

2019-08-07 Thread Vincent Zimmer
threat models in addition to the general threat > model. > > > The full gitbook can be also avaiable at > > https://github.com/jyao1/EDK_II_Secure_Coding_Guide/tree/Threat_model. > > > Cc: Vincent Zimmer > Signed-off-by: Jiewen Yao > > Re

Re: [edk2-devel] [tianocore-docs EDK_II_Secure_Coding_Guide PATCH] Add Appendix: Threat Mode for EDK II.

2019-08-05 Thread Vincent Zimmer
This looks good. Helps address some of the concerns brought up in evaluating secure coding guidelines for alternate feature implementations, too. Reviewed-by: Vincent Zimmer -Original Message- From: Yao, Jiewen Sent: Monday, August 5, 2019 12:48 AM To: devel@edk2.groups.io Cc

Re: [edk2-devel] [RFC] Propose update of security bug handling process

2019-04-15 Thread Vincent Zimmer
I agree w/ your comments Jian. Great input from Lazlo, too. I also want to let the community know that this specific process posting has 2 parts. This first was to post the process used by infosec bz team today, which Jian did well with https://github.com/jwang36/tianocore.github.io/wiki/Propo