Mac App Store apps must implement sandboxing as of March 2012
developer.apple.com
Mac App Store apps must implement sandboxing as of March 2012
1–10 of 71 posts
Re: Mac App Store apps must implement sandboxing as of March 2012
#2Apple's developer relations with anyone who doesn't want to fork over $100 just to read the docs are really poor.
Re: Mac App Store apps must implement sandboxing as of March 2012
#3I guess my "membership level" can't see the tech docs.
Re: Mac App Store apps must implement sandboxing as of March 2012
#4I wish I could find better documentation for this. I'm curious how their sandboxing implementation will work. I guess my "membership level" can't see the tech docs.
https://developer.apple.com/library/mac/#documentation/Secur...
Re: Mac App Store apps must implement sandboxing as of March 2012
#5Apparently, I am not authorized to view any information on sandboxing besides "[a]s of March 1, 2012 all apps submitted to the Mac App Store must implement sandboxing" and that it "is a great way to protect systems and users by limiting the resources apps can access and making it more difficult for malicious software to compromise users' systems." Apple's developer relations with anyone who doesn't want to fork over…
Re: Mac App Store apps must implement sandboxing as of March 2012
#6I wish I could find better documentation for this. I'm curious how their sandboxing implementation will work. I guess my "membership level" can't see the tech docs.
Did you even look? It's publicly available: https://developer.apple.com/library/mac/#documentation/Secur...
Thanks, that's what I was looking for.
Re: Mac App Store apps must implement sandboxing as of March 2012
#7I wish I could find better documentation for this. I'm curious how their sandboxing implementation will work. I guess my "membership level" can't see the tech docs.
Did you even look? It's publicly available: https://developer.apple.com/library/mac/#documentation/Secur...
Re: Mac App Store apps must implement sandboxing as of March 2012
#8Apparently, I am not authorized to view any information on sandboxing besides "[a]s of March 1, 2012 all apps submitted to the Mac App Store must implement sandboxing" and that it "is a great way to protect systems and users by limiting the resources apps can access and making it more difficult for malicious software to compromise users' systems." Apple's developer relations with anyone who doesn't want to fork over…
http://developer.apple.com/programs/register/
Though to your point, I'm not sure why Apple requires someone to login just to read the docs.
Re: Mac App Store apps must implement sandboxing as of March 2012
#9AppleScript (beast that it is) was innovative when it was created, and still has not been replaced. Automator is built on AppleEvents, and with sandboxing will come a sharp decline in the number of applications that can receive AppleEvents and the extinction of apps that send them.
Re: Mac App Store apps must implement sandboxing as of March 2012
#10https://developer.apple.com/library/mac/#documentation/Secur...
The vast majority of apps on the App store can be sandboxed without effecting their functionality in any way.
Sandboxing on OS X is not like Sandboxing on iOS. You can still access all your files. Your app just can't do it without asking. You can still send Apple events to other apps - you just can't send them to whatever apps you feel like. They must be defined, and permission granted via entitlements. True, you cannot access another applications preferences. However, an application can present an API that other applications can access.
In other words, this change forces apps to be designed much more securely. It reminds me of the Android permissions model.