Of course, Apple could have done this before. They could push out an OS update that wiped an app from everyone's computers. But that was a huge undertaking and now they have a process that is generally accepted from the App Store, and I wouldn't be surprised if we start to see it more regularly.
Edit: Apple wouldn't even have to be against Bittorrent clients. They could just get sued by record labels and lose, and then a judge would say "You built the capability to remotely disable apps, so use it to disable this one."
If it's about the first, I think the users who can get a Bittorrent client up and running (and have an interest in it, in the first place) are also able to read reviews and ask friends who may have recommended them this application.
Only those from Trusted Sources
Only those from Trusted Sources or which are signed by a developer ID
Any app, whether signed or unsigned
Where "trusted sources" is something that future Gatekeeper would give you control over.Enterprises spend a ridiculous amount of effort in locking down and pushing out software to workstations, so allowing them to maintain their own code-signed internal "app store" could be game changing. Apple has almost no enterprise presence, and this could be an opportunity for them to steal market share from Microsoft, who lately appears directionless and out of touch.
But it's not going to slow down developers, or even kids who like to explore.
> This is a preference in system preferences that is pretty easy to change.
That doesn't matter. It means that if I want people to use my software, I will now have no choice but to join Apple's $99/year Mac Developer program.
Time to port to Linux/Windows.
Here's Apple's own page on the matter: http://www.apple.com/macosx/mountain-lion/security.html
> Apple wants to help you steer clear of malware even when you download applications from places other than the Mac App Store. That’s why Apple created the Developer ID. As part of the Mac Developer Program, Apple gives developers a unique Developer ID for signing their apps.
This seems strongly to imply that a Mac Developer Program membership is required for code signing.
I very much hope that their phrasing is merely imprecise, and if not, that they will change their minds and provide free signing. I love OS X as a development program, but I will leave it behind if they start down this path.
Why waste time being outraged about something unimportant when you could be BUILDING SHIT?
FOSS and freeware developers, I imagine.
>You're building apps on a $1700 laptop while sipping a $6 coffee in your $2000/month apartment, for fuck's sake.
Sorry, no I'm not. I'm scraping by on a laptop that cost $1100 when I bought it six years ago. My living situation is... let's just say that you're just a tad north of reality. I was making an OK living off of some shareware I wrote until Apple pulled the rug out from under its smaller developers with last year's App Store transition. $100 is not a hardship, but it is a significant chunk of change.
Now, with that all out of the way, that's not actually the point. The point is what this does to people just starting out. Consider how much free/cheap software there is out there because somebody took their little weekend project and decided to pop it up on the web. Now consider what proportion of those people are going to take that leap if they have to pay a hundred bucks for practically anyone to be able to use it. Do you think any of them will be willing to put it out there for free under those conditions?
If I were a Mac developer with a skepticism about Apple's increasingly tight grip on their platform, I'd be much more concerned about the widening circle of APIs that are unavailable to non-App Store apps.
That being said, it isn't like the switch (and its parameters) and the development of Mac App Store-only APIs can't be trends that reinforce each other, of course.
I have the third option, but I will also have to explain this option to the users of my software. Plus, the option is not granular -- it seems like you cannot disallow all unsigned software, but make exceptions.
Here, let's try just one response and you just (safely) assume that it stands in for a myriad of other similarly horrible issues:
Likelihood that Apple will sell its CA root key to an unnamed Fortune 500 company under NDA to make some kind of software rollout problem simpler for them at the expense of the security of every Mac computer in the world? Zero.
Likelihood that an SSL CA will, after sucking the intestines out of a freshly killed puppy dog using its razor sharp SSL CA proboscis, sell its CA root key to an unnamed Fortune 500 company under NDA to make some kind of software rollout problem simpler for them at the expense of the security of every Mac computer in the world? Not zero. Not close to zero.
2. Will the code signing scheme be more vulnerable to malware because of the third-party CA? _____ (fill in)
2. ___ YES ___How many security breaches has Verisign had? Allowing 3rd party authorities to issue certificates would simply weaken the security that the feature provides. Moreover, it would mean that Apple cannot revoke the certificates, defeating the entire point of the feature.
> it seems like you cannot disallow all unsigned software, but make exceptions.
That would be a pretty broken feature. The only ways for OS X to handle that would be for it to say "screw it, I don't care what's in this specific directory, you can run it", which means that the directory becomes a vector for malware, or to disallow updating the directory once you exclude it, so that the OS can be sure that what you allowed is actually what's running. Both of these are pretty terrible options.
All in all, of the two ways it was likely to go (allowing only App Store apps by default, or allowing only signed Apps that meeting certain criteria), I think this is the much more palatable one.
Forgive me for being naive, but what does "app" mean in this context? Is a shell script an app? What about a python script with GUI elements?
The way code signing is implemented today, for another.
"It's also been designed to let you manually override the protection measures and install something that hasn't been signed, even if your settings are turned all the way up to App Store only."
Can we please stop repeating BS?
People like to make it sound like some kind of slippery slope, but including Mountain Lion, NOTHING has been taken away from users re: freedom, from OS X 10.0.1 to 10.8.
In addition to running whatever from whatever, 10.7 gave you the option to use an App repository. You know, like the one, say, Debian had from decades, only not restricted to OSS.
In addition to running whatever from whatever AND from the App Store, 10.8 adds the ability to only run signed apps. You, know, like the security solution that is considered one of most effective ones by security boffins.
Well, no, that's not quite true. See also: PTRACE_DENY_ATTACH in random binaries (e.g. iTunes) and the gimped DTrace implementation.
Are these showstoppers or the end of freedom as we know it? Not be a long, long way. Are they (fairly small) limitations on the freedom of users? Yes.
http://www.apple.com/macosx/mountain-lion/features.html#gate...
I know a lot of people won't like it, it's the equivalent of locking up the box with proprietary screwdrivers, but these restrictions do make life a lot easier for regular users and the people who have to support them.
Also, it's nice to have a choice of operating systems. This kind of thing fits in with the siloed approach Apple takes across the board, so for dedicated Apple users it's not evil, it's just an improvement on what they're already used to.
The "No unsigned code default" has been coming for a while in mainstream computing, thanks to most users ability to blindly click anything attached to a random e-mail or downloaded from their favourite wallpaper site. Out of the options ("App Store Only" or some other signature system), I think they chose the right one. As long as the opt out is there, not only do I not have a problem with this, I'd suggest it's a positive step forward. The only change I'd want is to remove or massively reduce the cost of getting a developer certificate.
Not at all, for several reasons. First, defaults are powerful things. The vast majority of users never change them, or even become aware that they can be changed. This remains true even if you throw an unskippable dialog box right up in their face -- lots of people will just blindly click "OK" to accept whatever the default in the dialog box is, without stopping to consider the alternatives. The result is that default settings tend to become "the new normal," even when they're sub-optimal.
(Example: why did IE6 rule the Web for a decade, despite being demonstrably inferior to the alternatives for most of that time? Because for nearly all users, it was the default.)
This seems especially true in the case of this particular preference, for two reasons. First, it's a technical question ("what's 'unsigned code?'"), which means many users will avoid changing it for fear that they don't fully understand the consequences of doing so. Second, it involves security, and users have been trained that in questions of security departing from "standard operating procedure" puts them at risk, so others will avoid changing it for fear that doing so will expose them to new vulnerabilities.
In other words, it's not unreasonable to expect that offering unsigned code will quickly become an infeasible strategy for OS X developers, even if users still have the option to accept such code. The option may be there, but those developers will find themselves marginalized simply for being something other than the default.
Apple is probably making the right decision for its users, but I still feel there is something we're losing here.
Calm down.
Overnight they'd lose many thousands evangelists and unpaid tech support staff (ever help a family member with their Mac?).
Like with iOS? Hackers will be annoyed, but Apple doesn't care about them when there are more than enough developers who are either in it for the money or who agree with Apple's position.
However, from Apple's perspective, if there are "enough" developers who can't or won't leave (because they develop Mac software or iOS software or both), Apple might not care if you do.
And it's not like the signing process is particularly onerous -- it won't represent even the slightest barrier or inconvenience to shareware, freeware or open source app distribution.
Sir, please click on About this Mac: if there is an icon of a signed page, we are good, but if it has a circle-and-slash around it, well, your Mac is running some unsigned software. Your warranty is void. Please go to the application list in Finder to see which apps you must uninstall...