7 ms·
Related thread, https://twitter.com/binarly_io/status/1654287041339998208 https://twitter.com/binarly_io/status/1654287041339998208
by transpute 4y ago
Related thread, https://twitter.com/binarly_io/status/1654287041339998208 https://twitter.com/binarly_io/status/1654287041339998208
- csdvrx 4y agoHow can you scan your firmware on linux, without running an unknown payload, to know if you're affected? How can you test the leaked key say to edit your bios, resign it, then reflash it?
- transpute 4y ago> How can you scan your firmware on linux, without running an unknown payload, to know if you're affected? According to the Twitter thread above, you would upload the original OEM firmware for your device to Binarly's web portal at https://fwhunt.run https://fwhunt.run. The firmware file matching your device could be obtained from the OEM's website, rather than the running system. I haven't tried this myself, don't know if it requires unpacking or pre-processing the OEM firmware file format.
- csdvrx 4y agoThey must be doing the equivalent of a grep. It seems safe, but I'd rather do that locally.
- transpute 4y agoMaybe someone could add key manifest inspection to this OSS tool, https://fiedka.app https://fiedka.app. Hopefully Intel and OEMs will make official statements soon. If you're copying a firmware file from the OEM's website to Binarly's website, then receiving a text report, they would have an IP address, browser fingerprint and device model number, but little else.