6 ms·
We are gettig an increasing amount of interesting Rust operating system for different uses. - Hubris for deep embedded - Redox OS for Desktop/Server (https://
by panick21_ 5y ago
We are gettig an increasing amount of interesting Rust operating system for different uses.
- Hubris for deep embedded
- Redox OS for Desktop/Server (https://www.redox-os.org/ https://www.redox-os.org/)
- Tock for embedded (https://www.tockos.org/ https://www.tockos.org/)
- Xous for trusted devices (https://xobs.io/announcing-xous-the-betrusted-operating-system/ https://xobs.io/announcing-xous-the-betrusted-operating-syst...)
I assume there are more.
- amitpm 5y agoRust is the language of choice for dApps on Solana as well (which I thought was an interesting choice.)
- rvz 5y agoThat is completely true. Rust is where it is going for cryptocurrencies that need to have very secure smart-contracts and scale up to millions of users with tens of thousands of transactions per second. Even if it is completely unrelated, it is 'at least' production ready and will be used more than these projects would ever be used in terms of Rust projects.
- securitypunk 5y agoRust won't protect smart contracts from logic bugs.
- elteto 5y agoI don’t think anyone said it would.
- jazzyjackson 5y ago> Rust is where it is going for cryptocurrencies that need to have very secure smart-contracts There is an implication here that Rust will help make smart contracts "secure", but AFAIK the vulnerabilities in smart contracts have been in their logic, not in their memory/type safety or whathaveyou.
- im_down_w_otp 5y agoIt depends on how much logic and/or arithmetic you can get away with encoding into the type system. We abuse the heck out of it to restrict things like register & field access, state-machine transitions, and also track resource allocation/consumption. That said, it's incredibly painful to develop anything that way, and it also doesn't ultimately prevent a different problem of the "model" you've written down in the types being wrong. So, it's not a panacea, and it's incredibly difficult, but it can winnow down the surface area of potential problems and bugs... or at least move them to compile-time.
- oxidethrowaway 5y agoRust in Cryptocurrency is mostly a marketing play (and I say this as someone who does a lot of Rust). Are there even any cryptocurrencies that allowed less-safe languages like C in the first place? In my opinion (as a Rust dev), Rust is weirdly over complicated for what they’re trying to do. Common types scripting languages are basically more than sufficient (and safe)for these applications. It’s only a matter of time before a crypto project overplays the safety of Rust and them has a huge heist due to a logic bug, which will further contribute to jokes about Rust programmers. Most of the Rust devs I know are wary of Rust crypto projects.
- delta1 5y agoIf that includes C++ then basically every cryptocurrency that’s not written in Rust (Bitcoin, Ethereum, Monero…)
- silasdavis 5y agoWe need to distinguish nodes written in Rust vs smart contracts. Given the context assuming smart contracts you may have a point. Often consensus will be much slower and a limiting factor in execution. Solana may be a bit different here in their efforts to parallelise independent transactions. High level provable languages always seemed like a good idea to me for smart contracts. As you say Rust doesn't necessarily seem like the sweetspot for this. The Ethereum EVM assmebly is wildly unsafe but regularly used for the sake of gas and other things that would be impossible (most hilariously string manipulation). Solidity is unsafe with respect to things like overflow. It doesn't have memory unsafety in the traditional sense. Partly because it is allocate only and you don't have to deal with bounds checking yourself.
- pjmlp 5y agoMicrosoft is a bit schizophrenic in Rust's adoption. In one side of the fence you have Azure IoT Edge, done in a mix of .NET and Rust. https://msrc-blog.microsoft.com/2019/09/30/building-the-azure-iot-edge-security-daemon-in-rust/ https://msrc-blog.microsoft.com/2019/09/30/building-the-azur... On the other side you have the Azure Sphere OS with a marketing story about secure IoT, yet the SDK is C only, https://docs.microsoft.com/en-us/azure-sphere/app-development/development-environment https://docs.microsoft.com/en-us/azure-sphere/app-developmen... To the point they did a blog post trying to defend their use of C, https://techcommunity.microsoft.com/t5/internet-of-things-blog/developing-secure-coding-in-azure-sphere/ba-p/1796510 https://techcommunity.microsoft.com/t5/internet-of-things-bl...
- munificent 5y ago> Microsoft is a bit schizophrenic in Rust's adoption. It's only "schizophrenic" to the degree that you expect an organization of thousands of individuals to behave like a single human mind.
- pjmlp 5y agoI expect the business unit that sells "secure" IoT devices, to follow the guidelines from Microsoft Security Response Center, but that is expecting too much I guess.
- ncmncm 5y agoExpecting a Profit Center to follow instructions from a Cost Center is akin to expecting the US Congress to act on advice from the General Accounting Office.
- pitterpatter 5y agoGenerally when MSRC files security issues, they tend to get fixed quickly and across not just the current release but previous ones too.
- 5y ago
- im_down_w_otp 5y agoWe also built a Rust framework called FerrOS (https://github.com/auxoncorp/ferros https://github.com/auxoncorp/ferros) atop the formally-verified seL4 microkernel. It has a similar set of usage idioms to Hubris it looks like in terms of trying to setup as much as possible ahead of time to assemble what's kind of an application specific operating system where everything your use case needs is assembled at build-time as a bunch of communicating tasks running on seL4. We recently added a concise little persistence interface that pulls in TicKV (https://docs.tockos.org/tickv/index.html https://docs.tockos.org/tickv/index.html) from the Tock project you referenced above, and some provisions are being added for some more dynamic task handling based on some asks from an automotive OEM. Also, sincerest h/t to the Tock folks.
- panick21_ 5y agoLooks like a really cool idea to build on the formally verified C code and building everything else in Rust on top. I defiantly think all the embedded Rust and even others will end up sharing lots of code. I would like to spend some time working Datomic style on a more powerful immutable DB that could run on different KV interfaces. Lots of configuration should more immutable.
- pjmlp 5y agoIf you can talk about it, how does that play out with standards like AUTOSAR and its C++ requirements?
- im_down_w_otp 5y agoI'm not sure I understand the question exactly. I'm familiar with AUTOSAR (both "classic" and Adaptive) as well as with ISO 26262. Happy to answer, just not quite sure I fully understand the question.
- pjmlp 5y agoIt requires C++17 and has been merged with MISRA. So how does a car manufacturer uses Rust and eventually be compliant with AUTOSAR/MISRA certification? It would be interesting to know if there is some movement in that front.
- simion314 5y ago>Redox OS What is interesting about this OS except it is made with Rust? I mean some interesting architecture , new exiting features that are not in Windows/Unix world? My question is if Redox OS is more similar to other hobby Oses we see here or is something more well thought like Plan9, Fuschia, Singularity ? Is there a link where someone that is not a Rust fanoboy (but maybe an OS fanboy) reviewed/described it in more detail?
- dralley 5y agoRedox is Plan9-inspired except it goes a little further with some of the core concepts. Instead of everything being a file, everything is a scheme (basically a URL).
- throwaway894345 5y agoI thought Unix was “everything is a file” and Plan9 was “everything is a filesystem”?
- dralley 5y agoMaybe so. I guess the point is, the concept that different types of resources need different protocols is baked in, rather than picking one type of abstraction and applying it to every type of resource. https://doc.redox-os.org/book/ch04-10-everything-is-a-url.html https://doc.redox-os.org/book/ch04-10-everything-is-a-url.ht... There are some filesystem-like usage patterns built on top of that which are universal, but they're more limited. https://doc.redox-os.org/book/ch04-06-schemes.html https://doc.redox-os.org/book/ch04-06-schemes.html
- pjmlp 5y agoOn Unix "everything is a file" until sockets came into the party.