There are two main ways that permissions work on android - the android way and the unix way.
The unix way applies in a few cases, where the kernel checks the GID before allowing access to a file (such as application private storage) or capability (INET sockets). More commonly, when your process makes a call through an android framework stub, the other end of that interprocess communication figures out which application the calling process belongs to, and checks if that application has the required android permission to perform that operation. On Apr 25, 7:16 pm, Jimmyz500 <[email protected]> wrote: > I have a follow up question on Android permission checking. > Can someone shed some light on how sensor data is protected by the > permissions? > For example, take GPS location, if I grant the "ACCESS_FINE_LOCATION" > permission, how does that work in the location manager to grant > or deny an application to the GPS location info. I know that the > ACCESS_FINE_LOCATION permission is not associated with a GID, so > permission > checking should not be done by a GID checking on a file for GPS info. > So how exactly is that done? > I have read somewhere that the GPS location is written to /data/ > local/ > dev/smd27, I can't find this file, maybe because I am using the > emulator and there is not a real GPS chip which stores the data > there? > Thanks very much, > -J -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-security-discuss?hl=en.
