@rosyna @drewthaler Even for things that would never be approved in the Mac App Store, so that every Developer ID app can be sandboxed.
-
-
@mjtsai@drewthaler That's exactly how sandboxing works today on Mac OS X.0 replies 0 retweets 0 likes -
@rosyna@drewthaler And it doesn’t, AFAIK, address APIs that area available but behave differently when the app is sandboxed.0 replies 0 retweets 0 likes -
@mjtsai@drewthaler Which such APIs do that? There is a list of "temporary extensions" that are only temp for MAS https://developer.apple.com/library/mac/documentation/Miscellaneous/Reference/EntitlementKeyReference/Chapters/AppSandboxTemporaryExceptionEntitlements.html#//apple_ref/doc/uid/TP40011195-CH5-SW1 …0 replies 0 retweets 0 likes -
@rosyna@drewthaler For example, -[NSWorkspace openFile:]. The rules have changed several times w/ OS versions and are not documented.0 replies 0 retweets 0 likes -
@mjtsai@drewthaler What rules for openFile:? You just need to call startAccessingSecurityScopedResource: first to punch a hole in sandbox0 replies 0 retweets 0 likes -
@rosyna@drewthaler No, there are cases where the document can't be opened if the app for it isn’t sandboxed, even if you punch a hole.0 replies 0 retweets 0 likes -
@mjtsai@drewthaler Do you have an example of that? Because LaunchServices handles openFile.0 replies 0 retweets 0 likes -
@rosyna@drewthaler Not handy. DTS eventually explained it to me; they were initially unaware, too. I fear more undocumented cases like this0 replies 0 retweets 0 likes -
@mjtsai@drewthaler Because restrictions on openFile: are mostly handled by Gatekeeper, not the sandbox.0 replies 0 retweets 0 likes
@rosyna @drewthaler If it’s a Gatekeeper issue, it’s one that only applies when the launching process is sandboxed.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Michael Tsai
Rosyna Keller