6 ms·
Virtualization, then Containers, and now WASM are all stages in completing the implementation of capability based security started long ago with the separation
by mikewarot 5y ago
Virtualization, then Containers, and now WASM are all stages in completing the implementation of capability based security started long ago with the separation of root and users back in Unix.
While it is reasonable to trust users with their own files, it is unreasonable that the only model of computing offered to those users requires that they then give all of their privileges to every piece of code they run.
It is possible to run code from anywhere without having to trust it, thanks to this new model of computing.
- naasking 5y ago> It is possible to run code from anywhere without having to trust it, thanks to this new model of computing. Capability security is almost as old as access control lists. That's the only quibble I have with your post.
- mikewarot 5y ago>Capability security is almost as old as access control lists. Yes, but it's never been fully implemented. Separating superuser/root from normal users was a good first approximation. However, in the modern era of persistent internet and mobile code, we need to finish the job. Theoretically, you could start a new process having previously created a new UID and having turned off access to all files in the ACL on the root, but can a user do that? Easily? Can you explain it to someone's mom? Money in a wallet is capability based, and people have managed that model since the beginning. I'm fine with ACLs for managing overall access to file structures on a per account basis, they don't work for a per execution instance basis.
- zozbot234 5y agoAren't UID's namespaced in modern Linux? It should be quite possible.
- naasking 5y ago> Yes, but it's never been fully implemented. Separating superuser/root from normal users was a good first approximation It sure has, in at least 6 different operating systems that have actually seen real world use, and 3 programming languages since the mid 70s.
- infogulch 5y ago> Can you explain it to someone's mom?
- speed_spread 5y ago"Don't click the Incredimail links in your email"
- naasking 5y agoActually, under capability security it should be pretty safe to click links in emails, because all programs that run with least possible privilege. https://en.wikipedia.org/wiki/Capability-based_security https://en.wikipedia.org/wiki/Capability-based_security
- RodgerTheGreat 5y agoIt's a good thing there aren't any known classes of architectural attacks exploiting the interaction of speculative execution and caches to exfiltrate sensitive data, nor are there classes of attacks which exploit the physical properties of DRAM to evade memory protection. Yes indeed; running untrusted code blobs on my home computers and cloud servers alike is truly and finally solved by running them in a VM.
- abtinf 5y agoMalicious attacks aren't always the vector of concern. There are many software packages that confine themselves to what is legal. They often want to ingest and upload everything they can about the user. But if they are locked down to a narrow set of user data, they won't risk the liability of attacking the protections themselves.
- thfuran 5y agoIt's also rather harder to exfiltrate data via rowhammer or meltdown than via, say, unrestricted filesystem access so even if it's technically possible, it will be less prevalent.
- mikewarot 5y agoI agree that we have big problem with defective CPUs and DRAM in the industry. Those chips and modules shouldn't have made it out the factory door, nor should they have passed quality control at the receiving desk. We also seem to have the same issue with SSD modules and SYNC commands. You can't fix broken hardware in software without taking a huge performance it, if it is possible at all. Yes, we all like to point out corner cases here, don't we?
- deleted 5y ago[deleted]
- gumby 5y ago> all stages in completing the implementation of capability based security started long ago with the separation of root and users back in Unix. Ahem, such distinction predates Unix, and in fact Unix has a watered down regime compared to Multics, which implemented a multiple ring approach. In other words, computing existed before Unix.
- pjmlp 5y agoBurroughs was one of the first computing systems usign bytecode as executable format and capability based security, it is 10 years older than UNIX. Its security capabilities are one of the reasons why Unisys keeps updating and selling it to customers that want security above everything else. Virtualization and containers have existed in IBM mainframes for a decade before making their way into UNIX.