Policykit at best would be used for the request to access the area- the actual permissions on disk to enforce this (and seperation/proxying of access to the content) are outside policykit however. It's best to think of policykit as the dbus equivalent to sudo, basically.
The key thing to note about policykit is that you're basically poking it for an action- rpc like. Passing back an fd for example, or allowing an existing process to start poking in a directory isn't really viable- asking another process to do so on your behalf is more up it's alley. ~brian ________________________________ From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Clark, Joel Sent: Wednesday, October 27, 2010 6:57 PM To: meego-dev@meego.com Subject: [MeeGo-dev] Policy Kit Does the Policy Kit in MeeGo provide the capability such that content stored on the local storage device (HDD, SSD, or USB Drive) is only readable by the applications explicitly granted access by the owning application? regards Joel BMC 7867
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
