Capability-Based Security
The cluster focuses on capability-based security models for operating systems, advocating for sandboxing, least privilege, and explicit resource access to protect users from untrusted applications, in contrast to traditional Unix-style ambient authority.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Probably Capability based securityhttps://en.wikipedia.org/wiki/Capability-based_security
Capability based systems offer better options.All access to anything important (network, files, other commands, etc) have to happen through opaque handles called capabilities. Think of them as objects that you can't look for.When you call code, you pass it a set of capabilities that are available. That is all it can ever access.But the whole language and environment needs to be defined from the bottom up to enable this.
The phrase you're looking for to poke into a search engine is "capability-based security": https://en.wikipedia.org/wiki/Capability-based_securityIt's a long, kinda story, which I'm not intimately familiar with, but seems to boil down to, it's more effort than we're willing to spend on rebooting our entire computing infrastructure. (Lo
Isn't the first part of your suggestion handled on OS level anyways? Aka. restricted user access, SELinux, AppArmor etc.
Unpopular opinion: Secure general purpose computing isn't available for the masses. In fact, most people here on HN don't have access to it either. Our current crop of widely used operating systems all share the same flaw, the ambient authority granted to any program that is run to access anything that the user account is permitted to access.This causes a host of problems, and almost nobody is aware of them, or incorrectly assigns them to other causes. This results in a patchwork of
I'd like to make my life's principle one generally shared by everyone.No human should ever have to blindly trust a program to do the right thing. That is the job of the operating system.The OS should make it easy to select the resources that a program is allowed to access. It should be as easy as taking a dollar bill from a wallet.The OS should make NO other access possible for the program to be run.This, ladies and gentlemen, is Capability Based Security... something we&#x
You seem to be unaware of the existence of capability based security. https://en.wikipedia.org/wiki/Capability-based_security
isn’t the current linux security mindset that all access is potentially privileged?
You want a capability based OS where by default processes are sandboxed.
This is a failure of the security model underlying the operating system design.Operating Systems exist to securely multiplex the resources of a system and make them fairly and reliably available to the user of that system. In order to do so, the first order of business is that the system should observe the principle of least privilege. That is, it should grant no privileges by default, and only grant access to the resources required for a task to complete.iOS, Android, Linux, Unix, Windows