> How could any hardware manufacturer think it was a good idea to let a userspace program permanently alter EEPROM, ever?
Because most hardware manufactures are selling to consumers and not cypherpunks.
Re:"BadBIOS" features explained
by stephengillie on Friday November 01, 2013 @08:11PM
(#6657464)
This brings us full circle to the original question, though: Did the security researcher write a program to dump the contents of EEPROM rather than desoldering the chips? if so, then he may have been hoodwinked by the virus.
Is this different than getting a dump of the BIOS before flashing it? Are we talking about different chips on the motherboard?
I'm speechless that this horrible idea was ever taken seriously, much less implemented. That answers my question as to how a BIOS could become infected.
I'm seriously sitting here in shock. How could any hardware manufacturer think it was a good idea to let a userspace program permanently alter EEPROM, ever? One does not need to be very intelligent to realize hackers will hack that.
This brings us full circle to the original question, though: Did the security researcher write a program to dump the contents of EEPROM rather than desoldering the chips? if so, then he may have been hoodwinked by the virus.