>>14259317 (pb)

> Traceable log

Not necessarily.

If their hack was 100% in memory, there would be nothing on the machine itself. All the records and logs would be on their PXE/DHCP server or the router/firewall.

That's why they won't turn over the Splunk logs.

>>14259330 (pb)

> Wireless module

This can be faked.

If they've comp'd the operating system via PXE, then can have the OS list the WWAN as offline, even though the PXE loader has fired it up and put it to use.

The x86 and AMD64 commandset are filled with undocumented instructions, many of which were intentionally created to allow the systems to be compromised by (((intelligence agencies))).

The undocumented instruction set is a real thing.

https://hackaday.com/2021/03/26/undocumented-x86-instructions-allow-microcode-access/

>>14259433

> Dubs

> NYPD cops doing their best to earn a lethal injection

>>14259499

> Moar dubs to confirm

Fuckers need to pay.

>>14259551

> War between people with guns and lots of training, and people who are afraid to breath the air.

Gee. I wonder how that conflict will end.

>>14259633

> Dumb dubs

Read again, fren. It's disabled.

But since PXE boot is enabled, and it's a UEFI system with an Intel hypervisor, that's meaningless.

The system is rooted, and they can do w/e they want with it.

>>14259681

> Suggests that network fags need to ponder PXE as a vulnerability

When shopping for network cards, I specifically avoid ones capable of PXE boot.

I also turn it off, first thing, as soon as I start work on a new system.

In the thirty years I've been working on computers, I've only used it twice.

Once to Ghostcast to a bunch of machines, and once for fun.

On small-to-medium sized networks, it's nothing but a vulnerability. And on large networks, it's hardly ever used owing to its complexity.