• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Sandboxing die.die.die
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sandboxing die.die.die


  • Subject: Re: Sandboxing die.die.die
  • From: Greg Parker <email@hidden>
  • Date: Wed, 29 Aug 2012 16:59:51 -0700

On Aug 29, 2012, at 3:34 PM, Alex Zavatone <email@hidden> wrote:
> But before anyone reads too far, I am making certain assumptions that may indeed be false.  That iOS and Mac OS app Sandboxing is absolutely required and you can't make apps without it enabled, whether the apps are destined for the App store or not.
>
> If my assumption is incorrect and Sandboxing is not required for non App Store apps, (Mac OS or iOS) please let me know.  If that is the case, then the trick is finding the documentation for file access without the Sandboxing restrictions.

App signing and app sandboxing are two different things.

A signed app includes a cryptographic claim of its author's identity.

A sandboxed app has additional restrictions enforced by the OS.

Sandboxed apps are signed, but signed apps are not necessarily sandboxed.

The App Stores require sandboxing. iOS also requires sandboxing for all apps, whether or not they are distributed by an App Store.

OS X does not require sandboxing. For apps that are not sandboxed, traditional file access is unchanged. Mountain Lion's Gatekeeper can be configured to require signed apps, but it does not enforce sandboxing.


--
Greg Parker     email@hidden     Runtime Wrangler



_______________________________________________

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

  • Follow-Ups:
    • Re: Sandboxing die.die.die
      • From: Stephane Sudre <email@hidden>
References: 
 >Sandboxing die.die.die (From: Graham Cox <email@hidden>)
 >Re: Sandboxing die.die.die (From: Jens Alfke <email@hidden>)
 >Re: Sandboxing die.die.die (From: Kyle Sluder <email@hidden>)
 >Re: Sandboxing die.die.die (From: Alex Zavatone <email@hidden>)
 >Re: Sandboxing die.die.die (From: Graham Cox <email@hidden>)
 >Re: Sandboxing die.die.die (From: Graham Cox <email@hidden>)
 >Re: Sandboxing die.die.die (From: Greg Parker <email@hidden>)
 >Re: Sandboxing die.die.die (From: Graham Cox <email@hidden>)
 >Re: Sandboxing die.die.die (From: Mike Abdullah <email@hidden>)
 >Re: Sandboxing die.die.die (From: Graham Cox <email@hidden>)
 >Re: Sandboxing die.die.die (From: Mike Abdullah <email@hidden>)
 >Re: Sandboxing die.die.die (From: Graham Cox <email@hidden>)
 >Re: Sandboxing die.die.die (From: Mike Abdullah <email@hidden>)
 >Re: Sandboxing die.die.die (From: Alex Zavatone <email@hidden>)

  • Prev by Date: A digression (was Re: Sandboxing die.die.die)
  • Next by Date: Re: On handling those lovely unrecognized selector sent to instance SIGABRTs
  • Previous by thread: Re: Sandboxing die.die.die
  • Next by thread: Re: Sandboxing die.die.die
  • Index(es):
    • Date
    • Thread