Re: Sandboxing and NSTask
Re: Sandboxing and NSTask
- Subject: Re: Sandboxing and NSTask
- From: Kyle Sluder <email@hidden>
- Date: Sun, 14 Aug 2011 15:18:58 -0700
I believe the recommended advice would be to move to XPC services, which can be separately entitled.
But all of your apps should automatically receive permission for ~/Library/Application Support/$COMPANY_NAME. We recently had to update OmniGraffle to look in ~/Library/Application Support/The Omni Group/OmniGraffle for its stencils for the same reason.
--Kyle Sluder
On Aug 14, 2011, at 1:59 PM, Andrew Satori <email@hidden> wrote:
> Having spent the weekend trying to migrate to supporting sandboxing, I think I have hit a snag that may well be terminal.
>
> The situation:
>
> My application contains a bundle that embeds a set of programs (a local instance of the PostgreSQL RDMS). Outside of the sandbox, it properly creates the database and does the work using NSTask. All of the file IO is safely inside the users home directory in the ~/Libray/Application Support/ folder.
>
> When I enable the sandboxing it all goes into the toilet. As far as I can tell, the NSTask calls are not inheriting the sandbox entitlements and are there fore failing to be able to have any file IO against the container.
>
> The question:
>
> Has anyone else had to deal with this that can offer any insight? I am feeling very lost.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden