|
|
|
|
|
|
by blackflame7000
2542 days ago
|
|
|
Yes, you can, that's what driver signing is for on the OS side. An authentic driver can then tell if it's talking to a counterfeit firmware. In the early days of the Xbox 360, the first hack was to modify the DVD drive firmware so that it would disable the security check that validates authentic Xbox discs and you could play burned games. After a while, Microsoft figured this out and started banning consoles. How did they do this? They simply compared the firmware images and detected a different checksum. There's no real good way to hide this because different code produces different binaries which is what firmware is. If you can flash the drive then you can read its memory and see it's not original. To give an analogy, if we are both running a calculator app that should be identical, but your call stack looks vastly different after we do identical operations, something is fishy. |
|
|
...but even if they are, checking a firmware checksum only mitigates risk if you otherwise trust the hardware.
Counterfeit silicon could report back whatever your driver wants to hear. And even the presence of a a genuine intel chipset with genuine firmware doesn’t mean there isn’t a malicious component elsewhere on the board.
There’s tons of counterfeit silicon out there.
Most of them are just cheap approximations or copies of premium components with the motive to make a profit on their sale, but there’s not much preventing any of them from intentionally or unintentionally compromising their hardware.
The popularity of programmable silicon and the standardization of silicon package sizes make this super cheap and easy to do as well.