I'm not touchin' any of this.

Reminds me an awful lot of the story of the PowerVR leak's cautionary tale:
https://libv.livejournal.com/26972.html

-Matt

On Thu, Aug 6, 2020 at 3:40 PM Simon Newton <simon.new...@gmail.com> wrote:

>
> https://www.tomshardware.com/news/massive-20gb-intel-data-breach-floods-the-internet-mentions-backdoors
>
>
> n fact, the title of many of the documents do correlate to the list of
> purported information posted by the leaker:
>
>    - Intel ME Bringup guides + (flash) tooling + samples for various
>    platforms
>    - Kabylake (Purley Platform) BIOS Reference Code and Sample Code +
>    Initialization code (some of it as exported git repos with full history)
>    - Intel CEFDK (Consumer Electronics Firmware Development Kit
>    (Bootloader stuff)) SOURCES
>    - Silicon / FSP source code packages for various platforms
>    - Various Intel Development and Debugging Tools
>    - Simics Simulation for Rocket Lake S and potentially other platforms
>    - Various roadmaps and other documents
>    - Binaries for Camera drivers Intel made for SpaceX
>    - Schematics, Docs, Tools + Firmware for the unreleased Tiger Lake
>    platform
>    - (very horrible) Kabylake FDK training videos
>    - Intel Trace Hub + decoder files for various Intel ME versions
>    - Elkhart Lake Silicon Reference and Platform Sample Code
>    - Some Verilog stuff for various Xeon Platforms, unsure what it is
>    exactly.
>    - Debug BIOS/TXE builds for various Platforms
>    - Bootguard SDK (encrypted zip)
>    - Intel Snowridge / Snowfish Process Simulator ADK
>    - Various schematics
>    - Intel Marketing Material Templates (InDesign)
>    - Lots of other things
>
>
> --
> Kind Regards,
>
> Simon Newton
>
> E: simon.new...@gmail.com
> _______________________________________________
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-le...@coreboot.org
>
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

Reply via email to