Some enterprise environments use a custom OS, or highly customized version of an existing OS across all machines, connected to a central login server.
Rather than install the OS every time they get new hardware, or manually install updates across millions of machines, especially if they're scattered across multiple physical locations, it makes sense to have a single Operating System image that can be updated and forced out to all the machines on the network.
It's possible (though with all the shady dealings, my benefit of the doubt is pretty low on this one) that Dominion ordered a BIOS image and didn't bother to order the default to have PXE disabled, and whoever Dominion got to build their BIOS just set the default they normally do for their enterprise customers.
Point is, unless someone can force Dominion to give up the data, it's hard to way what happened, though the odds aren't int heir favor...
If they ordered a custom BIOS, it wouldn't have been from the manufacturer. Maybe through a third party channel partner, but that would still leave too many witnesses who see your election management system is configured for network booting. Even Dominion isn't that stupid.
I do think it's possible they pushed out a very lean image to a hidden partition on the drive via PXE. Post election, just delete the partition.
Nah, I'm saying there's a 1 in 1mil chance that both Dominion and whoever makes their BIOS dropped the ball, and they ended up with a "boot-from-network" by default in their BIOS by accident.
I highly doubt it, but there's a very slim chance that incompetence was at play here, in which case Dominion still can't be trusted with election integrity...
Force of habit, probably.
Some enterprise environments use a custom OS, or highly customized version of an existing OS across all machines, connected to a central login server.
Rather than install the OS every time they get new hardware, or manually install updates across millions of machines, especially if they're scattered across multiple physical locations, it makes sense to have a single Operating System image that can be updated and forced out to all the machines on the network.
It's possible (though with all the shady dealings, my benefit of the doubt is pretty low on this one) that Dominion ordered a BIOS image and didn't bother to order the default to have PXE disabled, and whoever Dominion got to build their BIOS just set the default they normally do for their enterprise customers.
Point is, unless someone can force Dominion to give up the data, it's hard to way what happened, though the odds aren't int heir favor...
If they ordered a custom BIOS, it wouldn't have been from the manufacturer. Maybe through a third party channel partner, but that would still leave too many witnesses who see your election management system is configured for network booting. Even Dominion isn't that stupid.
I do think it's possible they pushed out a very lean image to a hidden partition on the drive via PXE. Post election, just delete the partition.
Nah, I'm saying there's a 1 in 1mil chance that both Dominion and whoever makes their BIOS dropped the ball, and they ended up with a "boot-from-network" by default in their BIOS by accident.
I highly doubt it, but there's a very slim chance that incompetence was at play here, in which case Dominion still can't be trusted with election integrity...