5 ms·
Microcode Research Team
- opportune 5y agoThe IME JTAG is pretty dang interesting. Shame they are sanctioned. IMO the fact a huge portion of hardware ships with obscure, unverifiably secure microcode is one the biggest threat vectors in existence today.
- regnull 5y agoIs that the same Dmitry Sklyarov who was arrested by the FBI back in 2001, triggering a protest campaign? https://en.wikipedia.org/wiki/United_States_v._Elcom_Ltd https://en.wikipedia.org/wiki/United_States_v._Elcom_Ltd. Ah, memories.
- NetOpWibby 5y agoWho are these people?
- pabs3 5y agoIts the work of Positive Technologies according to this article from grsecurity: https://grsecurity.net/watch_your_stepping_atoms_breaking_apart https://grsecurity.net/watch_your_stepping_atoms_breaking_ap... https://www.ptsecurity.com/ https://www.ptsecurity.com/ Positive Technologies got sanctioned by the US government. Seems Google deleted their blog as a result. https://web.archive.org/web/20210419105554/http://blog.ptsecurity.com/2021/04/positive-technologies-official.html https://web.archive.org/web/20210419105554/http://blog.ptsec...
- ComputerGuru 5y agoIt’s a pretty BS sanction - PT is sanctioned just because the FSB is/was one of their clients with no claims that PT had anything to do with the actual hacks, at least as far as what was publicly disclosed. Compare what the link below says about PT vs what it says about some of the other entities insofar as to their complicity in the malicious incidents. https://home.treasury.gov/news/press-releases/jy0127 https://home.treasury.gov/news/press-releases/jy0127
- chrismorgan 5y agoLooks like https://raw.githubusercontent.com/chip-red-pill/Sildes/master/ZN2021/HOW_WE_ACHIEVED_TO_EXECUTE_uCODE.pdf https://raw.githubusercontent.com/chip-red-pill/Sildes/maste... (PDF, 1.8MB) might be a more useful link for general information?
- newbie789 5y agoWhat is this?
- peter_d_sherman 5y agoI would love to see an open-source x86 Microcode (or x86 subset Microcode) which would enable a separate open-source RISC CPU (i.e., https://opencores.org/projects?expanded=Processor https://opencores.org/projects?expanded=Processor) to run x86 instructions, or a subset of x86 instructions... Perhaps the path to such an endeavor is simply taking an existing open-source FPGA RISC CPU (RISC-V would be a good choice) -- and then trying to implement a single x86 instruction in open-source Microcode, on it... Success? Well, then let's try another x86 instruction! Eventually we'll have a few! If this or other x86 microcodes are copyrighted and/or patent-protected, what could occur is that a new microcode format (non-copyright or patent infringing) could be defined during this process... Also, an x86 subset FPGA "Soft" CPU -- would never be as fast or as instruction-complete as current Intel or AMD CPU's... In other words, such devices would be for hobbyist and/or educational use only -- they wouldn't compete with current Intel or AMD CPU's...
- pabs3 5y agoWhat would be the use-case for this? Most open source software is trivially portable across architectures. For the stuff that isn't there are code transformation tools like qemu-user-static.
- peter_d_sherman 5y agoYour argument is one of convenience, mine is one of education/understanding... Sure, one could use every computer program in existence without becoming a computer programmer and gain useful function from them, and this would not be wrong in any way -- but there are also those of us who wish to understand things at a very deep level... There are those of us who not only want to understand how computer programs work -- but how ISA's work, how the underlying hardware works, everything down to the substructures, the the adders, the logic gates, the flip-flops, the transistors, everything... And that list includes (but is not limited to!)... x86 microcode... Or more specifically, microcode in general...
- pabs3 5y agoI think it would be better to abandon x86 than to try to understand it :)
- kvathupo 5y agoI question the legality of this post: I'm pretty sure the Intel microcode specification is proprietary. While it's hard to say with certainty since Intel makes their website as hard to navigate as humanly possible, I doubt they'd hand over their secret sauce to competitors. On one hand, the subject of microcode would benefit from more transparency. Indeed, there are papers describing microcode behavior (Citadel's gpu papers come to mind). With that said, I'm concerned that the authors are more interested in exploits, given they have a disassembler repo. While a disassembler alone doesn't warrant concern (microcode is very specific to hardware), it is concerning if their presentation's claim is true; that is, the whole Atom line has similar microcode. I hope I'm wrong. I'm by no means an expert, but the sanctions leave me uneasy lol.
- kbenson 5y agoI'm not sure what you think is illegal about this. I suspect I'm either I'm coming at it from the wrong context, or I'm lacking in some info to fill in the gaps to make me think the same, as otherwise reverse engineering a processor is well tread (and legally supported) ground to my knowledge
- deleted 5y ago[deleted]
- kevin_thibedeau 5y agoThe problem is that they attained this by decrypting the microcode. That runs afoul of DMCA circumvention rules unless it can fall under an exempt activity.
- CogitoCogito 5y agoDoes Russia fall under the DMCA? That's where the developers seem to be located.
- kevin_thibedeau 5y agoGithub's servers aren't in Russia.
- deleted 5y ago[deleted]