4 ms·
I think adding on to POSIX is not the way to do it though. My model would be: For a program to access the internet, it must be given a capability (possibly in
by zzo38computer 1y ago
I think adding on to POSIX is not the way to do it though.
My model would be: For a program to access the internet, it must be given a capability (possibly in the initial message, but could also be in a different message), which it can communicate with in order to access the internet. The receiver can't know what capability it is (although it can request a specific capability in the type signature), so it might connect directly or it might use a proxy or simulate slow speeds or error conditions.
- AlienRobot 1y agoA problem is that you describe "access the internet," which is simply too low level for most real applications. The permission should be "communicate with www.example.com" and if the app needs more than that, you come up with a different permission that is broader. You want common use cases to have clear permissions so that users can make an informed decision when an app requires much broader access than other apps needed.