13 ms·
Why the Mac App Sandbox makes me sad
- dubya 15y agoI'm a bit wary of this, but it really does seem like a decent model for most things in the App store. It's pretty clear there needs to be some exception mechanism, since Xcode and Lion won't run in a sandbox, but there were already restrictions. TextWrangler in particular removed some functionality in its App store version. And things like TeXLive and the Haskell Platform and most other developer tools never appeared in the app store.
- podperson 15y agoI don't think he mentions that every app has full access to its own "container". Plugins, per we, are already not possible via the app store, but it's early days yet, and I think the author needs to understand that apple will adapt to user requirements. Comparing a software security model's trade offs between flexibility, user safety, and developer convenience with being a sharecropper is just another example of hysterical Godwinism.
- nhaehnle 15y agoIn general, this type of sandbox is a Good Thing. I would love to live in a world where the default environment for any program is a very limited sandbox that can only interact with the outside world via standardized UI elements. That is, outside a data store specific to the application, it can only access files via the standard dialogs, and so forth. The potential for malware distribution would be significantly reduced in such a world, because yes, there will always be stupid users, but you cannot blame all the stupidity on the user. Even I as a power user would like to try out little programs that I find on the internet - and that includes small games and screensavers, which are cliche carriers of malware. Yet I simply cannot safely try them out without an exorbitant amount of work. Having a proper sandbox environment as de facto standard outside of web browsers would be awesome. That said, it absolutely sucks that Apple combines an idea that is a Good Thing in principle with idiotic policies - if it is indeed true what the article claims.
- dlikhten 15y agoSandboxing is great since less and less control is in the hands of the app. I am sure apple will keep rolling out features expanding sandboxing, this is just the default impl. This also means that basically it will be harder and harder for apps to be malware in an already hostile system. I wish android had this. Android needs this much more than iOS.
- shareme 15y agoandroid does have it.. each Dlavik VM instance is its own sandbox
- Karunamon 15y agoWhy is this gettting downvoted? It's good security practice, and the fact that Android needs better sandboxing was a foregone conclusion.
- bad_user 15y agoBecause all Android apps are sandboxed and have to request explicit permissions for connecting to the Internet, reading or writing the user's contacts, accessing the user's pictures and so on and so forth.
- mcherm 15y agoWhat is foregone about that conclusion? My impression is that Android's sandboxing is quite nice, thank you. In fact, I think the biggest failing is that there need to be stronger ways to ESCAPE the sandbox (eg: to build a virus-checker or a backup program).
- arron61 15y agoAndroid does have sandboxing and its much better in than iOS. Each app runs in its own VM instance and requests for permissions. Additionally each app can also call other apps via intents. This allows for great sandboxing and reutilization.
- voxmatt 15y ago
- statictype 15y agoThis would worry me if there weren't at least two other major Operating Systems available to choose from. The Mac is moving more towards simplicity and safety - targeting normal consumers. That's fine. Ironically, now Linux and Windows (and anything else that comes up down the line) will have to serve as the 'Computer for the rest of us'
- robterrell 15y agoIronically, you got it backwards. You're "us". Whereas "the rest of us" = non-computer experts, anyone who prefers simplicity and safety. That crowd has always been the Mac's bread and butter. When we see signs that Apple will block software installation outside the App Store, then I'll grab a pitchfork. Until then, I think this is good for most users.
- jarek 15y agoI'm sure you will be able to reason it away, just like you did on iOS. "I can still jailbreak" might be the mantra.
- masklinn 15y ago> That's fine. Ironically, now Linux and Windows (and anything else that comes up down the line) will have to serve as the 'Computer for the rest of us' I'm expecting Windows to move towards a more sandboxed experience as well, at least for Metro/WinRT. I know Miguel de Icaza also hopes for broad sandboxing support by default. Regarding TFA, he does not make much of a case against sandboxing (applications not being able to write wherever the hell they want without warning the user counts as a positive in my book), and his final quote (of Tim Bray) is relevant to appstores, but it has no relevance whatsoever to sandboxing. Not impressed. Even the plugins stuff has limited relevance in the grand scheme of things, it will affect some applications for non-technical users (more technically oriented ones will likely be able to put their plugins where they know they should be).
- buro9 15y ago> I'm expecting Windows to move towards a more sandboxed experience as well It already does to some extent. Internet Explorer was the first to introduce it (to my now out of date understanding), and it's since expanded to other products including shipped Windows apps, Office, etc. It happens invisibly for the developer, if you think the registry that you access is THE registry then you're wrong. It's a proxy that you access, and the proxy has a view on what you will see or not. An example mention of this is here (one of the first Google hits): http://office.microsoft.com/en-us/access-help/enable-or-disable-sandbox-mode-HP001050432.aspx http://office.microsoft.com/en-us/access-help/enable-or-disa... Basically, you the user get the choice, but by default your apps, the things they open, are all sandboxed and protected. For compatibility reasons you can currently choose to override this, but as you might expect group policy can be used to disable someone's ability to lower their security.
- deleted 15y ago[deleted]
- tjogin 15y agoWe don't know that much about the Mac App Store sandboxing yet, it could be perfectly benign. This is mostly a bunch of conjuring of ominous fantasies.
- pavlov 15y agoAll the details are available on the Mac Dev Center. (I didn't just make up that list of entitlements.)
- natesm 15y agoIt's been available since Lion, my app uses it. We know everything about it technically. However, we know nothing about how Apple is going to handle exceptions and what will get you rejected. An app that I'm sort of working on right now absolutely needs read access to the entire filesystem, and possible write access in the future, unless Apple makes technical changes in sandboxing (unlikely until 10.8, effectively unusable until 10.7 customers are a tiny minority). Judging by Apple's actions in the past, we probably never will get any sort of official information, and when we try to piece it together by community observation, it'll be inconsistent anyways.
- tjogin 15y agoWe know nothing of its future capabilities and limitations.
- nknight 15y agoI can think of only two GUI apps I semi-regularly use that can't fit within those restrictions: VMware Fusion, and Steam. Plugins are a red herring. Some poorly-designed plugin infrastructures will not be workable, boo-hoo. Valid use cases can be accommodated with proper message passing. Maybe we'll finally get applications that don't crash horribly because of buggy plug-ins?
- pavlov 15y agoWhat kind of plugin architecture do you propose that doesn't use dynamic loading or standard IPC mechanisms? Your "message passing" is much too vague. Remember, this needs to be fast enough to accomodate FCP video processing plugins - hundreds of megabytes of data may need to be passed between the host and plugin each second.
- natesm 15y agoIs it possible to install the plugins to `~/Library/Containers/...` instead of the usual location? Not that loading code is allowed on the App Store anyways, unless you're Apple, of course.
- ryannielsen 15y agoPlugins can exist anywhere. They can be placed into the app's bundle without necessarily breaking its signing seal, they can exist within the app's container if the app has a way of copying them in (e.g. it advertises a file type, like Aperture's ".ApertureExport" bundle, so the user can double click to load the plugin, or it provides an "Install Plugin" feature somewhere), and they can exist anywhere in the user's home dir or system volume (if the app requests an exception to read files from those known locations). No code loading restrictions are placed on signed and sandboxed apps. Any signed and sandboxed process is free to map in any code, though that code is bound by the parent process's sandbox restrictions.
- natesm 15y agoThis is the one I am referring to: 2.16 Apps that download or install additional code or resources to add functionality or change their primary purpose will be rejected So I guess that you can have a plugin system as long as you don't provide an in-app way to download and install them, like Adium does?
- mevodig 15y agoUltimately, for me, this is about creating a reasonable user experience for the majority of users. While it's easy to forget this when spending a lot of time in forums such as HN, _we_ are not that majority. This constant expectation that platforms used everyday by millions of people should be tailored to us is untenable.
- keeperofdakeys 15y agoYou know what, you are a user too. The platform should perform well for everybody, not just the majority. This is what makes me feel Unity and Gnome Shell aren't the best way to go, not just simplifying, but totally removing configurability. There is a central ground, where an interface can be learn-able by a normal user, and not inhibit power users. The thing with OSX appstore sandbox isn't that it hurts power users, it hurts the majority. It limits what developers can make applications do, preventing many types of applications that users would expect to be possible. Sandboxing itself isn't bad, it is just this implementation that is bad.
- iaskwhy 15y agoThat can be a really dangerous way of thinking if you apply it to everything else. It reminds me of when people define democracy as the will of the majority when in reality it should be the voice of the minority. Sure, we should aim to simplify everything but whenever someone makes a call to silence the minority it's not going to be a good thing.
- jiggy2011 15y agoI don't know.. I think allot of people here underestimate the average user. I see allot of comments on this site of people basically saying "everyone else just uses the computer for facebook". That's not really true, although there are users like that. I know allot of people who are not technical or CS people in the HN sense but who use their computers for allot of stuff including some pretty sophisticated creative or business tasks and are actually quite capable of doing technical stuff assuming it is explained properly to them. Also people on HN have probably spent more time using computers and seeing lots of different users use computers that we probably have more of a long term feel of what would work well and what wouldn't, and if we are all developing the next generation of apps etc for the masses then our opinions and requirements are actually pretty important. If you have an over restrictive platform that does not allow developers to innovate in ways that they want then whilst end users may appreciate the simplicity, they will become frustrated if this platform fails to deliver the flexible applications that they really want. For example I know many non tech users who use literally hundreds of firefox plugins. Of course there are a few people I know who are of the opinion that all hardware & software for everything should just be developed by Apple end of story.
- CHsurfer 15y agoOne possible strategy may be to offer a 'limited' version of your app that is compatible with the Sandbox constraints for a low price. When a user tries to do something that is not possible due to the constraints, you can inform them that the pro-version (not installed through the app-store) can eliminate this and other inconveniences. If you are worried about destroying the market value of your app, then just charge full price on the app store and allow customer's to 'upgrade' to the unconstrained version. This is far from ideal as it incurs lot's of overhead by maintaining two versions and extra work for the customer, but it will probably be worth it to stay on the App store.
- natesm 15y agoActually, you can't (within the app, at least) - App Store apps can't make references to the existence of software that is outside the App Store.
- RyanMcGreal 15y agoUgh, it's like the GPL in reverse.
- CamperBob 15y agoI can imagine the GPL-inspired first line of the AMI license. "Most software is designed to let you do various things with your computer. Software licensed under the terms of the AMI (Apple May I) license is different. It is designed to make sure you can't do anything useful with your computer at all, at least not without asking first."
- deleted 15y ago[deleted]
- sirn 15y agoI thought 1Password 3.9 (the MAS version) was already using App Sandboxing and I don't feel limited at all. Dropbox syncing works fine like before and browser extensions works better than before (without all the ugly InputManager hacks). Basing on this one app I often use, I'm overall happy with sandboxing so far.
- feralchimp 15y ago+1 The article makes some strong assertions about what is/is not allowable under the currently available set of entitlements. I expected more discussion here about whether all of those assertions are accurate. If there's a primary source that I can take a shot at interpreting independently, can someone point me toward it? UPDATE: Looks like the best doc is the "App Sandbox Design Guide". Film at 11. :P
- duncanwilcox 15y agoThe Sandbox makes me sad. Remove exploits of a single poorly written app spreading to the rest of my Mac and taking over make me sadder.
- darren_ 15y agoIt's not even 'poorly written', it's nearly every non-trivial C/C++ app, over a long enough time, turns out to have _something_ exploitable in it.
- dogfu 15y agosigh Does that include the sandbox itself, which was written in C?
- darren_ 15y agoYes? But it presents a much smaller attack surface (as compared to the attack surface presented by the set of applications you might otherwise run under a sandbox). And it's maintained/secured by one vendor instead of the set of vendors that distribute the applications you might otherwise run under the sandbox.
- kenferry 15y agoAh, but the sandbox profile are written in scheme! So clearly all good.
- makira 15y agoThe problem with the current sandboxing is the missing entitlements, for simple things like: - Using the burning framework (cd & dvd burning) - Interfacing with Apple Remotes - Having a shared container between a main app and a helper app Also, many utilities will have to be removed from the App Store because of sandboxing, and that will likely cut revenues dramatically for those developers.
- jemeshsu 15y agoSeems like the current implementation can not take care of a lot of common scenario. It is not as ready. It is hard to be safe in an open world. I guess that's the reason why Apple postpone the requirement for sandboxing to March next year.
- bengl3rt 15y agoYep, looks like whatever version of my app (DubPlate) that's up on the store in March '12 is the version that's going to be there in perpetuity, because it can't be updated for the sandbox on account of its using the CD burner pretty much as a core feature.
- fpgeek 15y agoWouldn't Apple remove it from the App Store for non-compliance at some point? That's what they do on the iOS side.
- shinratdr 15y ago> Using the burning framework (cd & dvd burning) I wouldn't be surprised if this was intentional. I'm sort of picturing Apple killing off the 17 inch Pro, 13 inch Pro, Mac Pro, and then slimming down the iMac and 15 inch Pro by removing the optical drive. They are done with optical media. It wouldn't shock me at all to see DVD Player removed from 10.8. > Interfacing with Apple Remotes Correct me if I'm wrong but I'm pretty sure this ability was removed with 10.6. I can't control anything besides built in Apple apps on my Mac with my Apple Remote unless I install Remote Buddy + Candleair, which restores 3rd party access to the Apple Remote by using an alternate driver.
- super_mario 15y agoAs a die hard Mac user, fuck Apple and the Mac. Honestly. After the rumor they are killing off Mac Pro, and this insane gestapo shit already under way in Lion (which I don't use), I really don't want to be associated with Apple in any way.
- bonch 15y agoYou are seriously comparing a security sandbox to the gestapo? If killing off products that aren't profitable is insane to you, and implementing a security sandbox model that every other platform either already has or is going to have (Windows 8 included), I don't think you'll be a die hard fan of any company for very long.
- guywithabike 15y agoCalm down. You may want to go for a walk outside. Or talk to an anger management counselor.
- schiptsov 15y agoJeez! How do I run my Java crap?! but, considering it is a little bit more, I think Apple gives to developers too much freedom. To write a successful and profitable iPhone app you all you need is just the ability to play a sound file. ^_^
- dmbaggett 15y agoThis is all so well-played by Apple: evolve ever more locked down systems in seemingly consumer-friendly ways. Once consumers forget they can even install their own applications (except through the app store), OS X distribution will be just as heavily moderated by Apple as iOS distribution. Expect Apple, Microsoft, and Google to exert ever more control over distribution. The software industry is evolving into the "studio model" just as the movie industry did decades before: 5-7 huge players controlling absolutely everything that sees the light of day. Everything else is small-time "indie" stuff that hits big every once in a while, but is otherwise irrelevant. (It took Apple to make Microsoft realize this was something they could actually get away with -- thanks, Apple!) Nintendo's been doing this for years with their consoles. It's not good for developers, and not good for innovation. But it's very good for the studios, because it gives them complete control, and makes a new player emerging out of nowhere (as Google themselves did circa 2000, or Facebook did circa 2009) much less likely. The cartel stays nicely entrenched. How long 'til websites are similarly locked down? Will users forget they can just type a URL in, and instead install everything through their friendly neighborhood web app store? (Don't laugh.) Who will approve websites? Oh right, the 5-7 huge players. Got it. I don't want to sound like a tin-foil hat here, but having spent my youth in the console game business (Naughty Dog), this seems all too familiar...
- ootachi 15y ago"Will users forget they can just type a URL in, and instead install everything through their friendly neighborhood web app store? (Don't laugh.)" Who's laughing? All but two of the Web browser manufacturers (Opera and Mozilla, both of which are losing market share) seem to have vested interests in doing exactly this.
- dmbaggett 15y agoYes, and add to that the fact that typing on a mobile device is painful, and you have a strong usability argument for doing away with the URL bar entirely.
- artursapek 15y agoThis reminds me of Steve demoing the first iPhone, when he pulled out the numpad in the Phone app and called dialing a number "real last-century." I think soon we will all have the bookmarked websites we regularly visit as browser-apps (contacts, if you will) with most of the rest being taken care of by hyperlinks, and once in a while one will have to pull out the URL bar to actually type an address in manually.
- saturdaysaint 15y agoThis article mostly seems to ignore the fact that you can still distribute apps outside of the App Store. In fact, considering the falling costs of hosting and easy access to marketing tools (look at the quality of the website for any Mac App), it's probably never been easier. For pro apps with dedicated audiences (see: Adobe, Ableton, Avid, Nuance) which is just about anything with a plugin architecture, the App Store's distribution is unnecessary. These are established companies with deep links into creative communities. As a consumer, when you're looking at spending hundreds of dollars on, say, music software, you don't care what's in the "Top 25" or on Apple's "Featured" list (if you're smart) - you care about what the people you're working with are using and the opinions of specialized professionals.
- brudgers 15y ago>"For pro apps with dedicated audiences (see: Adobe, Ableton, Avid, Nuance) which is just about anything with a plugin architecture, the App Store's distribution is unnecessary." It is true that inn terms of dedicated (aka existing) audiences or customers, access to is probably still unnecessary, however it is clearly a disadvantage when it comes to generating new users or providing upgrades to existing users.
- saturdaysaint 15y agoThe economics for pro apps are completely different than anything an app store customer can reference. A lot of the market leaders (Pro Tools, Adobe Suite, Avid) have succeeded despite being orders of magnitude more expensive than competitors and erecting barriers for the average user accessing them (byzantine copyright protection, proprietary hardware requirements). There are always lots of cheap and even reputable alternatives, but the leaders usually capitalize by being early to market and basically owning the leaders in the field. Once you have a community of the best and brightest using/evangelizing your software, distribution is a pretty secondary concern.
- nimrody 15y agoApple may eventually disable loading of executables which are not cryptographically signed. At this point, you'll have to resort to kernel patches to bypass that mechanism and load non-authorized applications. Hopefully, Apple will leave a way to disable code verification. At least for advanced users.
- shampoo 15y agoDoes anyone know what the adoption rate is for the App Store for Mac ? How many apps in the App Store cannot be downloaded outside of the App Store ? How many apps converted from being downloaded outside the App Store to inside. My question is, can Apple put the Genie back in the bottle ?
- guard-of-terra 15y agoDon't they distribute xcode via appstore? it obviously dould not fit in the sandbox. If they make it an exception, can't they be hammered for monopolizing the development tools in the app store for themself?
- glassx 15y agoYeah, they also use it to sell OS X now...
- gcv 15y agoApple distributes the Xcode installer through the App Store. Normal App Store restrictions don't apply.
- guard-of-terra 15y agoCan anybody else distribute a foo installer, so normal restrictions would not apply?
- ryannielsen 15y agoNope. Xcode is special.
- phoboslab 15y agoHow exactly does an installer that can write to any location on your disk fit into a restricted AppStore? Also, does this mean I'm free to distribute my malware installer through the AppStore? After all, it's just an installer.
- c1sc0 15y agoCool! Does this mean I will be allowed to distribute App Install scripts through the AppStore? The best of both worlds: free distribution & full control!
- feralchimp 15y ago"If you choose not to sandbox your app now or to use a temporary exception entitlement, use Apple’s bug reporting system to let Apple know about the issue you are encountering. Apple considers feature requests as it develops the Mac OS X platform." So everyone with grave concerns about sandboxing is filing Radars, right?
- kstenerud 15y agoOne problem with sandboxing is that it stifles innovation. Many of the innovations in computers (dynamic libraries, drivers, plugins, screen grabbing, password managers, etc) came from being able to do anything on your computer. Once the sandbox lockdown is complete, you won't be able to invent new techniques that require entitlements the gatekeeper hasn't thought of already. The sandbox marks the end of the open system. Protecting users from malware is a noble goal, but I don't see sandboxing as an effective enough tool to justify the loss of freedom. iOS is still to this day being compromised with ease despite its massively locked-down design, and I don't see the cat-and-mouse game ending any time soon. In fact, the malware danger from email and web pages is FAR higher than that from shady apps. The motivation for the app store is purely financial, of course, which means that over the coming years it's in their interests to command as much control as possible, even to the point of eliminating unsigned apps altogether once the app store ecosystem is mature enough (plus it will allow them to finally kill Flash off all Apple platforms for good, as well as hobble all competing browsers, and, well, pretty much any software they decide to compete with). I don't see this scenario playing out well.
- deleted 15y ago[deleted]
- wanorris 15y ago> The sandbox marks the end of the open system. The existence of the sandbox doesn't. Not yet. As long as there's sideloading, it's still an open system. I'm very happy with my ability to sideload apps on Android, and it keeps the platform from being too locked down. I can install a whole alternate app store from Amazon that way if I want -- in fact, it would be great if Cydia or someone released an open app store for OS X apps that don't meet Apple's criteria. You wouldn't have to jailbreak your computer to use that app store or any of its apps. That's the barometer for when Apple goes to far. It's possible that day will come -- when they've gotten this far, it would no longer be shocking to see them go the rest of the way. But until they take that final step, OS X is still an open system.
- tomlin 15y ago> plus it will allow them to finally kill Flash off all Apple platforms for good... You can't declare that sandboxing will destroy innovation, but also actively persist that killing Flash is a good idea. Not saying you are, but you know others will. Flash is often used as a petri dish - a way to create new experiences and test them with a real audience. YouTube, Blog.tv, many experimental video / social integration and many other innovative (today or yesterday) ideas have lived and died because of Flash. If you've never coded a Flash experience (outside of restaurant websites) and did it well (ie, bother to code it properly), you might find it hard to see this point - again, I point you to the many examples available. When we talk about the "open web" without Flash, you're really talking about a more closed web, because the average designer / programmer can no longer contribute to the core functionality of the browser - unless, of course, you work alongside W3C. Unless Adobe begins releasing in longer cycles, by that I mean slower than W3C's snail crawl, the idea that HTML/JS will eventually catch up to Flash is a logical fallacy given history of technology.
- neanderdog 15y agoWell I've been considering a linux on my macbook pro for sometime as os x has (e|de)volved. This pretty much clinches it for me.
- vasi 15y agoWhile it's possible that Apple could ban non-App Store programs, I don't see this as the likely threat. More plausible to me is that new APIs in OS X will, like iCloud, become available only to App Store apps. Eventually anything that's not in the App Store will feel like the most ancient Carbon apps feel now. Why prompt an exodus of users over a mass ban of apps, when you can just slowly and surely take over the market instead?
- fpgeek 15y agoIndeed. Apple's become very, very good at boiling frogs slowly. And I believe there are already at least a few APIs that are only for App Store apps.
- andymoe 15y agoI understand that people are worried that Apple will abuse their power and be unreasonable about granting exceptions but honestly after building many apps on the outside and seeing how things work from the inside for a year (during Lion dev) I don't think that will necessarily be the case. Sandboxing will make OS X more secure, and that's a good thing, especially as the OS X install base pushes towards the 15% range and beyond providing a juicy target for our friends on the dark side. Let's hope I'm right and Apple plays fair because I would like the two App Stores to keep paying my bills while there are still people who are wrong on the Internet.
- amartya916 15y agoIt seems that the sandbox may allow for easier iCloud syncing. Since even Apple's apps like Pages, Keynote etc. cannot sync data to iCloud, it seems like an obvious feature to implement. I hope they allow App store curated 3rd party apps iCloud access as well.
- bonch 15y agoI don't understand the sudden news coverage over the App Store's sandbox requirement. This impending requirement has been known to developers since at least the last WWDC.
- atwhn 15y agoI am altering the deal. Pray I don't alter it any further.
- lallysingh 15y agoI just bought a new laptop. The last 3 were powerbooks/macbook pros. I saw the app store on os x and decided on a lenovo this time, running linux (xmonad helped tip that scale). I'm really glad I went that way. I'm sure that this is a good thing (tm) for most users, and will help avoid all sorts of problems. But the Mac's becoming more of an appliance, and while it's safer, easier, and more convenient for most users, it makes it a substantially less desirable machine for me to hack on. There's a tradeoff between making the developer environment and user environment closer together -- to make the machine more amenable for hacking, to reduce the wall for development, and to make the platform a good place to learn how to write code -- vs farther, to make it a simpler, safer environment for users. So far, the bias has been on the former, but it's changing. What's interesting is that this may, for the time being, push app development server-side (to the web) as the client environments become more hack-inhospitable.
- dextorious 15y ago"""But the Mac's becoming more of an appliance, and while it's safer, easier, and more convenient for most users, it makes it a substantially less desirable machine for me to hack on.""" You do understand that in Lion, say, nothing, absolutely nothing has been taken away from you that you could do back in 10.1 or even NeXT. So, this "the Mac's becoming more of an appliance" is just bullshit, just blindly following the latest trend in "hacker" circles (and probably a hacker's desire to buy a new, different system to tinker with).
- fennecfoxen 15y agoDude. We know how the iPhone works. It's easy to see Apple starting to bring the same sort of model to the MacBook. We're not blind. We can see where this is going, even if it's not there yet, and make reasonably informed guesses about what it's going to be like.
- ldar15 15y agoIf the App store becomes the only way to install applications, then its back to linux for me. I don't really see that as a horrible dystopian future. Even if Windows 8 hardware gets locked down, there will always be a market for linux boxes. Unless the government mandates otherwise, in which case we've got bigger problems.
- egsmith 15y agoIs that really the complete list of privledges? It says a child process can inherit the sandbox but not that a child process can be created. I mention it because I think the plug-in issue could be solved with child processes and sockets, or something similar. Also, a typical program now can't access a generic thunderbolt device directly (it would be done via the file system which is a possible privilege). Thunderbolt devices are in PCI address space and this needs to be done via the kernel even now. But it does raise a question: What about 3rd party device drivers? All in all, I think most of these sandbox arguments underestimate developer creativity.
- Limes102 15y agoThe only time I'm going to feel concerned about the sandboxing on Mac OS apps is if it's forced onto all applications. If that happens, I shall leave Mac just like I did Windows and be forced to use Linux... I can't say I particularly like the new layout of Ubuntu so maybe I should just quite computing completely :'(
- deleted 15y ago[deleted]
- tikhonj 15y agoThe nice thing about Linux is that you are never tied to the whims of a single company like Canonical--if you don't like Ubuntu, you could always use Fedora with KDE or Gnome, for example.
- Wowwhatisthe 15y agoClearly, to most intelligent humans, Apple is trying to push certain software off of the App Store. Like Anti-virus programs, or programs that require plugins. That's their choice. If you want to sell those apps, you can't use the App Store. There is no problem... quit whining kids!
- ryannielsen 15y agoSome points of clarification to eliminate some FUD, especially around plugins: - Signed and sandboxed applications are not prevented from using plugins. No code loading restrictions are placed upon such processes. Furthermore, Lion-only apps could employ an XPC based plugin architecture and entirely avoid loading code into their address space. - Plugins do not need to exist within the app's bundle. Plugins don't even necessarily need to exist within a sandboxed app's container, if that app requests an exception to read its plugin directory (e.g. ~/L/Application Support/MyApp/Plug-ins). - Plugins can be signed and distributed independently from their host app. - Calling out restricted Thunderbolt access is a misnomer. AFAIK, there is no public Thunderbolt API now and as Thunderbolt is largely PCI Express + DisplayPort, any kind of access would have required kexts anyway. As kernel extensions already aren't allowed on the App Store, this isn't (just) a sandbox restriction. - Bluetooth devices can likely be accessed via AppleBluetoothUSBHCIController, which provides a USB HCI interface to any compatible BT devices. - You can read/write files in a known location on a network disk (or any disk) if you simply ask for permission once per launch. In fact, if you opt-in to auto termination, that user-granted entitlement will persist across most app relaunches, as long as the app's serialized state is preserved[1]. (And if you filed a radar requesting such a feature, it's very possible Apple would find a way to persist that user-granted entitlement across all app relaunches.) Regarding other points, it is true that Firewire access is restricted, as is general filesystem access and frame buffer access. Likewise, a sandboxed app is prevented from sending Apple Events to arbitrary applications, breaking a good bit of IPC. It's fair to complain about these restrictions (some of them affect my apps, and working around them will not be simple and may require removing popular features), but please don't cloud the issue with misinformation. [1] http://www.cocoabuilder.com/archive/cocoa/308884-sandboxing-and-file-references.html#308916 http://www.cocoabuilder.com/archive/cocoa/308884-sandboxing-...
- pavlov 15y ago- Signed and sandboxed applications are not prevented from using plugins. No code loading restrictions are placed upon such processes. Really? That's good news if true. Got a reference for that? In any case, since loading plugins would be subject to the same restrictions as other file access, the app can't maintain persistently accessible references to the plugin files. The app would have to ask the user to manually pick each plugin using a file dialog, each time the app is run. This kind of "manually-aided binary loading" isn't really a plugin API anymore. Furthermore, Lion-only apps could employ an XPC based plugin architecture and entirely avoid loading code into their address space. Please elaborate. I still don't see how XPC can be used to implement a plugin architecture, assuming the Apple documentation is correct in stating that XPC services need to be located inside the main application bundle in order to be loaded. Re: Thunderbolt -- the problem here is that even if a kernel extension driver is already installed, a sandboxed app can't access it. (The example case in my mind would be my own video capture app: it's got direct support for devices by Blackmagic Design, including their new Thunderbolt-based units. I'm using the vendor's API for this. If I were to sandbox this app, it would have to lose this functionality.) [Edited this reply to add more details.]
- heyrhett 15y agoI think that it demonstrates that we've passed the era where people want "a computer" to do things. People want a smartphones, tablets, notebooks, etc. People are not buying these devices for their raw computing power, and they don't want the freedom to access all of it. People want these devices to "work" at their respective tasks. Apple is becoming the sole gatekeeper of apps to their devices. For example, after begrudgingly allowing 22 or so "fart" apps into the app store, they said, "ok, we gave you some fart apps, now you have enough fart apps, we aren't going to allow any more fart apps into the store". If some developer comes up with the best fart app ever, there is no practical way for him to distribute it any more. I see this as an insane amount of power for one company to have. Imagine if MS did the same thing with windows. If they did it 10 years ago, they would have been sued for monopolistic practices, but now that Apple's doing it, and Apple is a viable competitor to MS, can't MS do the same thing, and now we are stuck with basically 2 companies deciding all of the software that can be installed on 99% of the computers that people use? This is a sad future to me.
- fpgeek 15y agoImagine if MS did the same thing with windows. If Microsoft had done the same thing with Windows, Apple as we know it today wouldn't exist, if they even existed at all. To me, it is mind-blowing that, nevertheless, (most) Apple fans are perfectly happy with the shoe on the other foot.
- ZipCordManiac 15y agoAs a longtime Mac user (since the 80s) , it pains me to think my next purchase won't be a Macintosh, but I can't ignore the writing on the wall any longer. Apple used to be about freedom and creativity - now they just want to give the best user experience while keeping users safe and maximizing profits. Not an all-together horrible goal, but also not the kind of computer I want to use. I want a computer, not a toaster or a microwave. People have for years called mac kid computers, and I never really agreed with them before now. This kind of development really puts the final nail in the coffin though. These computers are made for people who simply want a locked down boring experience. It's a sign of the times, just look at the TSA.
- rayiner 15y agoPeople are forgetting that as consumption apps move to the iPad/iPhone, more of the people left on the Mac will need the extra power of a non-locked-down environment. Apple's goal is still to sell hardware. As long as they can create a newbie-safe experience on the Mac without locking out people who need to tinker, it buys them nothing to do so.
- iuguy 15y agoI'm concerned about this move. As long as you can continue to install things outside of the sandbox and Mac App Store, I'm happy, but there's a massive flag going up in my head over this, I'm really not sure Apple would be able to resist the urge to integrate the locked down nature of iOS into OSX. This concerns me to the point where I'm now rethinking 3 MBP purchases as I'll be stuck with them for 4 years at work, and I don't know what OSX will be like in 4 years time.