I'm sure you're all aware of just how viscerally aware I am that UEFI is absolutely cursed and let me tell you it is nowhere near as cursed as vendor network stacks

@mjg59 Having worked at a prominent network equipment vendor in their IPv6 compliance testing group, I have seen some of what you describe. About all I could muster was "...Why‽"

@mjg59 sometimes the UEFI contains a vendor network stack

the packets are coming from inside the house

@mjg59 snmp implementations too. Why use a table when jamming all the unrelated values into one reply will do?

@mjg59 @Mirppc sips his 12% ABV cider while remembering OpenFirmware on NewWorldMacs as well as the early Uboot for older arm SBC's.

@mjg59

In my opinion UEFI is malware waiting to happen.
It's badly designed replacement of BIOS. (IMHO)

@FandaSin I don't know what "Malware waiting to happen" means - BIOS simply has no security model, there's no way anything could be worse in that respect

@mjg59

BIOS started system and then have no way to get back the ownership of RAM / HW / ....
UEFI is paralel OS to my OS and can access most of HW any time.

(or am I totaly wrong?)

@FandaSin you're totally wrong. UEFI runtime services are just a nicer version of BIOS interrupts - in both cases the firmware is hanging around waiting for the OS to call it

@mjg59

I've seen some UEFI Rootkits / Bootkits few years back and never looked into it deeper.
Thanks for expanding my knowledge.👍

@FandaSin BIOS bootkits existed before UEFI did - that's what a boot sector virus was

@mjg59 Is one memory-safe network stack everyone uses too much to ask for?