3 ms·
never did trust a processor or IDE component, from the day i learned how to use them. Whitepapers made me suspicious, the reserved words or bit values that whe
by rolph 7y ago
never did trust a processor or IDE component, from the day i learned how to use them.
Whitepapers made me suspicious, the reserved words or bit values that where mentioned but not documented despite the parent function being extensively documented was one of the reasons.
the results of bit walking hardware instruction sets and trapping the resulting output states gave me cause to suspect things.
the long and short of it is digital hardware is not open source, and is not an operationaly secure platform.
The advent of microcode, was a major turning point, as processors were effectively wiretapped at that point.
It was heralded as a way of fixing mistakes, post-production, so you could reprogram the microcode to do things differently. This puts the user in a very compromised situation, and is getting to be quite extensive as industry has gone beyond simple browser manipulations, and is actually reaching into the firmware that drives the hardware components, and manipulating systems out of band with the processor. The result is a compromised network of digital processors hosted on your mother board.
So what can we do when we design hardware? How about trap and dump?
if a word shows up on a bus, a home rolled bus controller/hard wired analogue device could quench that word, [trap-dump] so any and all compromised digital components would not hear evil instructions, and would be muffled from issuing evil bus words.
The microcode is something that is usually an encrypted proprietary firmware, unless the firmware can be opened, understood, and manipulated, by the actual owner/user then evil commands and evil actions, must be censored from reaching in or out. a massive undertaking but well worth it.
ya all can start following the breadcrumbs here:
https://en.wikipedia.org/wiki/Microcode https://en.wikipedia.org/wiki/Microcode
https://en.wikipedia.org/wiki/Microarchitecture https://en.wikipedia.org/wiki/Microarchitecture
https://people.cs.clemson.edu/~mark/uprog.html https://people.cs.clemson.edu/~mark/uprog.html
https://securiteam.com/securityreviews/5FP0M1PDFO/ https://securiteam.com/securityreviews/5FP0M1PDFO/
- peter_d_sherman 7y agoHi Rolph, great links! You might want to check out this old HN article: "MyCPU – Homebrew Computer from Discrete Logic Gates": https://news.ycombinator.com/item?id=19926765 https://news.ycombinator.com/item?id=19926765 ...and not just the link, the comments in that article are information-rich as well. (There are several others in the same vein on HN, but I don't have them right now...) Those CPU's typically don't use microcode, and are generally interesting from a hardware enthusiast's standpoint. Hey, based on your previous HN comments and posts (Synchrotrons, Electromagnetic Propulsion, Plasma Physics, etc.), you seem like a pretty interesting guy! If you want to have a longer conversation, why not email me at peter.d.sherman@gmail.com ?
- rolph 7y agothanks P373 !