Michael TsaiVerified account

@mjtsai @drewthaler That's exactly how sandboxing works today on Mac OS X.

@rosyna @drewthaler And it doesn’t, AFAIK, address APIs that area available but behave differently when the app is sandboxed.

@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 …

@rosyna @drewthaler For example, -[NSWorkspace openFile:]. The rules have changed several times w/ OS versions and are not documented.

@mjtsai @drewthaler What rules for openFile:? You just need to call startAccessingSecurityScopedResource: first to punch a hole in sandbox

@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.

@mjtsai @drewthaler Do you have an example of that? Because LaunchServices handles openFile.

@mjtsai @rosyna @drewthaler If such entitlements existed, a lot of Developer ID apps would be on the store.

@ameaijou @rosyna @drewthaler No, I mean the entitlements should go beyond what Apple would accept in the store.

@mjtsai @ameaijou @drewthaler There are entitlements non-MAS apps can use that MAS apps can't.

@rosyna @ameaijou @drewthaler Yes, I’m saying there should be more. I don’t want to run into a road block *after* adopting sandboxing.

@mjtsai @ameaijou @drewthaler But which ones are missing that you'd run into?