2 ms·
Yes, it is. Try and read GPS data without asking the operating system for that capability. Even if you call to native code there is no way to trick the operatin
by charcircuit 4y ago
Yes, it is. Try and read GPS data without asking the operating system for that capability. Even if you call to native code there is no way to trick the operating system into giving you that data. Malware can't get it either because the security IS on the OS level.
>Otherwise Android wouldn't have a malware issue and iPhones wouldn't need to be locked up against third party apps.
Android malware is not as bad as what is possible with Windows malware. Over the years Google has been cracking down and working to remove permissions that apps can use without the user knowing. Unless the app has an exploit for the operating system it can't do much harm to you. iPhones have allowed for third party apps since the very first iphone a decade and a half ago.
- tonyg 4y ago> Try and read GPS data without asking the operating system for that capability. That's not capability-based security: you have to do that whichever model is in use. The ocaps come in when you use dependency injection (aka "function call") everywhere to pass in rights to make use of resources. Neither Android nor iOS are meaningfully object-capability based.
- charcircuit 4y agoYes, it is. Capability based security by definition just requires that apps have a list of a capabilities and those capabilities govern what APIs / resources it has access to. There is no requirement of dependency injection. That is an implementation choice.
- still_grokking 4y ago> just requires that apps have a list of a capabilities and those capabilities govern what APIs / resources it has access to No, that would be mandatory access control. Completely different concept.
- charcircuit 4y agoYou seem to be getting caught up with the implementation details. The whole point is that programs shouldn't be given overly broad access to the system. Access can be granted to programs by giving them capabilities. Whether that be from tokens or something else it doesn't matter. Please remember from the first commented: >Alas, we're in the timeline without capability based security. where users can't just give a file to a program at runtime using a (powerbox) dialog. This is literally how Android already works today. An app can not read a random file from the system. It has to open a file selector and you have to select a file before an app is able to read it.
- still_grokking 4y ago> This is literally how Android already works today. An app can not read a random file from the system. It has to open a file selector and you have to select a file before an app is able to read it. That's not implemented on the OS level.
- charcircuit 4y ago>That's not implemented on the OS level. Yes, it is. The Storage Access Framework is a part of the operating system.
- chriswarbo 4y ago> Try and read GPS data without asking the operating system for that capability Generally speaking, capabilities are not asked for; that would be a permission. Capabilities can be used to implement permissions, but that's not what is usually meant by 'capability-based security'. Capabilities are essentially just inputs; a GPS-reading capability would be anything we can read GPS data from (e.g. a callback; or a pseudo-file handle; etc.).
- charcircuit 4y agoCapabilities and permissions are the same thing. The app needs a capability or permission for it to use an API. The whole point is that an app should have permission or the capabilities to the minimum amount of things in order for it to work.
- chriswarbo 4y agoCapabilities are needed to "do" things; e.g. the URL of a document is a capability to GET it (via HTTP, or whatever). Without a URL (capability), performing a GET doesn't even make sense. Security is enforced by choosing who is given a capability (like a URL); we can get extra security by minting new capabilities, and revoking those which should no longer have access. Permissions are not required to "do" things; they are enforced elsewhere, to determine whether that thing should succeed or fail. For example, giving out URLs to search engines, then trying to have the server reject requests that we don't want (AKA 'closing the barn door after the horse has bolted')
- charcircuit 4y agoAndroid's binder seems to be exactly what you are talking about. A binder object represents a token for something you can send and receive transactions. You use binder to talk to LocationManagerService which lets you get the location. Android has a service manager and lets any app get the LocationManagerService. LocationManagerService itself does do the permission checks. The operating system uses both capabilities and permissions. Regardless, this is all implementation details and for the user it is equivalent. There is the same principle of least privilege where apps are limited in what they can do.
- anthk 4y agoYou can fake GPS data. Also, capabilities are far beyond the Android and iOS model.
- charcircuit 4y agoI don't understand your point. In capability based security nothing prevents people from making up fake data if they don't have the capability for something.
- still_grokking 4y ago> In capability based security nothing prevents people from making up fake data if they don't have the capability for something. That's completely wrong. The whole point of capabilities is that they're unforgeable. You can't mint a capability! You need to get it passed "form above". Nobody can create capabilities from thin air (not even the OS kernel).
- charcircuit 4y agoI do not follow your logic. Anyone can define a data type { latitude: 100. longitude: 100 }. The operating system is not going to stop you from creating this object.
- still_grokking 4y agoSuch a made up object would not be accepted by other parts of a capability secure system as it would lack the actual capability (which is unforgeable). But I'm coming to the conclusion that you're only trolling. You refuse to look at the facts and definitions, and just repeat the same nonsense over and over. I'm done here as I obviously can't help you understand this topic.