7 ms·
The best start you can get at a system that you fully understand and know isn't subverted. Then, once you know HW design, you can take the next step by putting
by nickpsecurity 11y ago
The best start you can get at a system that you fully understand and know isn't subverted. Then, once you know HW design, you can take the next step by putting it on your own ASIC. Matter of fact, Wirth's early systems ran well on old tech. Can use a pretty old process node. :)
- agumonkey 11y agoI would be very very happy for him to do talks about his way of working.
- nickpsecurity 11y agoWirth wrote a lot of papers on it. I look some important ones up, from OS's to HW, then post them for you if you want.
- agumonkey 11y agoI was lazy, that's why I mentioned talks. But I'd be happy to have a list of books too. Thanks.
- nickpsecurity 11y agoI got a few for you that show his way of doing things. The Lilith system was a start. Its approach of simplicity, layering, and consistency will help if you're lazy. Only a few here because I'm lazy after the huge posts I've been writing. ;) Lilith System http://www.cfbsoftware.com/modula2/Lilith.pdf http://www.cfbsoftware.com/modula2/Lilith.pdf Main project page http://www.projectoberon.com/ http://www.projectoberon.com/ Old system with links and ports (HW diversity or learning) http://www.oberon.ethz.ch/archives/systemsarchive/sys_genealogy_new http://www.oberon.ethz.ch/archives/systemsarchive/sys_geneal... How he compiles it https://www.inf.ethz.ch/personal/wirth/CompilerConstruction/CompilerConstruction1.pdf https://www.inf.ethz.ch/personal/wirth/CompilerConstruction/... Turning programs into circuits https://www.inf.ethz.ch/personal/wirth/Oberon/286.pdf https://www.inf.ethz.ch/personal/wirth/Oberon/286.pdf His hardware description language https://www.inf.ethz.ch/personal/wirth/Lola/LolaCompiler.pdf https://www.inf.ethz.ch/personal/wirth/Lola/LolaCompiler.pdf A guy who inspired his approach & did safe languages + OS's, including bullet-proof concurrency in 80's ;) http://brinch-hansen.net/ http://brinch-hansen.net/ There you go.
- agumonkey 11y agoI didn't know half of this, thanks a lot.
- nickpsecurity 11y agoSure thing. I always laugh when I hear "full stack developer" in its main use. I'd think the title shouldve been reserved for people like Wirth who develop apps, OS's, firmware, compilers, assemblers, and the hardware they run on. That's literally every part of the computing stack. Oh yeah, look up Juice project. Will need to use Wayback Machine. It replaced JavaScript in browsers with Oberon so you get safety plus native speed. Sent as compressed, abstract, syntax trees so used little bandwith without losing typing info. Faded like the rest but would've been awesome compared to the JS that bogs down even a Core Duo.
- agumonkey 11y agoHa... I'm sighing so hard reading about Juice. Never even heard about it and I'm into 'esoteric'. Mainstream is as boring as inevitable. http://web.archive.org/web/20000831045133/http://caesar.ics.uci.edu/juice/ http://web.archive.org/web/20000831045133/http://caesar.ics.... http://web.archive.org/web/20000610021840/http://caesar.ics.uci.edu/juice/ClockComparison/JuiceClock.html http://web.archive.org/web/20000610021840/http://caesar.ics....
- nickpsecurity 11y agoThought you'd like it. Came to mind again in a recent conversation on Ethereum with their "new" idea of distributed, smart contracts with programming languages. Reminded me of agent-oriented programming we did in the 1990's with products like Telescript running whole stores and stuff: http://www.sce.carleton.ca/netmanage/docs/AgentsOverview/ao.html http://www.sce.carleton.ca/netmanage/docs/AgentsOverview/ao.... Impractical really, but fun concept. You created a bot that programmatically represented your goals, limits, heuristics for analysis, and so on. It could, with 1-2 commands, pack its code & data into a file that moved to another "place." It could move to Amazon's store over slow WAN, analyse certain products for you, commit to the right one, notify you, record the receipt, pack that up, and come back with a report for you. Used interpeters with safe programming languages and sandboxes plus A.I. for some of them. Imagine how easy, efficient, and secure Juice applets would be for that, today's smart contracts, or Facebook. Now you can sigh again as you realize how much faster and safer things could be if a handful of companies merely learned from the past and made it an option. Btw, back then, we foresaw problems coming from untrusted or runaway code on machines in these agent marketplaces. So, platforms like Telescript had interpreters that isolated execution on a per-agent (per-user) basis. The platforms set in then-small datacenters on servers that spun up interpreters on demand in response to API requests. They measured CPU, memory, storage, and network usage for billing purposes. Any of that sound familiar? Like some "new" invention we hear about on HN, etc all the time? ;)
- amenghra 11y agoHow do you know the thing which takes your design and "builds" (i.e. machine which places physical components) or "compiles" (i.e. the thing which moves bits into an fpga) things isn't subverted?
- nickpsecurity 11y agoThere's ways to be reasonably sure. I can't publish it as it would only aid opponents. Here's the base requirements, though: https://news.ycombinator.com/item?id=10468624 https://news.ycombinator.com/item?id=10468624
- sinrostro 11y agoYou really should publish, as security through obscurity only hurts us! Out in the open, there is a chance that some measures will be taken. Concealment is a guarantee that bad guys will be doing bad things quietly.
- nickpsecurity 11y agoThat's a mainstream mantra but not true at all against High Strength Attackers (HSA's). They always have more resources than you do. They more they know, the more they can focus. That's why obfuscation on top of proven security techniques is the best strategy for use against HSA's. Gotta give them nothing (or false things) to aim at then have good detection or recovery measures. Proven strategy. Alternatively, I can publish my model. They can immediately move to counter the very specific things I do. Before you know it, they have a turn-key solution for compromising my devices individually or in bulk. Anyone using it is suddenly less safe. Knowing specifics will also benefit their stealth: less detection capability. Rather not publish that at least until I've developed something better. ;)
- AnthonyMouse 11y ago> That's a mainstream mantra but not true at all against High Strength Attackers (HSA's). They always have more resources than you do. That's why obscurity doesn't work. An attacker with many resources can reverse engineer whatever concealment you've concocted but the concealment is enough to deter other researchers who would have published their results from analyzing your system. So then the HSA knows of the attack and can take advantage of it but you don't so you can't counter it.