News for hackers. Stuff that matters.
Re:Apple's Great GPL Purge (2014) by oneplane on Monday November 07, 2016 @03:58PM (#12895005)
It's that that big of a deal actually. You can still disable SIP, you can still override kernel extension signing (and signing on pretty much anything else), and you can sill install any GPLv3 software you want. It's just the default base install that has changed, and everyone knows there is no one-size fits all. While there are plenty of commercial reasons to not go beyond GPLv3 from the vendor point of view, it doesn't really change anything for "us". Even if we had a stable bash from 2015, we'd still want the 2016 version and install it anyway...
Re:Apple's Great GPL Purge (2014) by paws on Monday November 07, 2016 @04:49PM (#12895504)
You can still disable SIP

Even if only an academic exercise, it would be cool to actually strip out SIP and mandatory kernel extension signing.

At the time of writing, Apple still hasn't open sourced Sierra's XNU[1].

[1] 10.11.6 source: https://opensource.apple.com/source/xnu/xnu-3248.60.10/

Re:Apple's Great GPL Purge (2014) by belorn on Monday November 07, 2016 @04:35PM (#12895383)
Wonder what is holding them back from going full lockdown on all apple devices. Is it because PR and trying to keep a good image with the developer crowd, is it because they can't demand that every third-party application goes through them or they loose business customers, or some other thing I just don't see?
Re:Apple's Great GPL Purge (2014) by threeseed on Monday November 07, 2016 @04:43PM (#12895452)
You make it sound like locking down the platform is a goal. It isn't. It's a side effect of hardening the platform from a security perspective.

And Apple has quite a few developers as well. I don't think they would want to make the platform impossible to use.

Re:Apple's Great GPL Purge (2014) by mikeash on Monday November 07, 2016 @05:11PM (#12895690)
Requiring every commercial app to go through Apple's review process and give Apple a 30% cut of revenues doesn't do anything to harden the platform from a security perspective.
Re:Apple's Great GPL Purge (2014) by jeffcox on Monday November 07, 2016 @05:21PM (#12895764)
You don't need to be in the App Store, you just need a signed developer certificate (99 USD/year).
Re:Apple's Great GPL Purge (2014) by mikeash on Monday November 07, 2016 @05:57PM (#12896021)
Not sufficient on iOS.
Re:Apple's Great GPL Purge (2014) by WayneBro on Monday November 07, 2016 @05:06PM (#12895654)
Locking you into Apple hardware and software is most certainly their stated goal. You can read it directly from the horse's mouth:

`In 2010, a year before his death, Steve Jobs outlined Apple’s strategy in an email to the company’s 100 most senior employees. He heralded the “Post PC era,” vowed “Holy War with Google,” promised to “further lock customers into our ecosystem,”...` - http://qz.com/196005/the-steve-jobs-email-that-outlined-appl...

Discussed recently here on HN - https://news.ycombinator.com/item?id=12864727

Security wasn't mentioned once in that email.

Re:Apple's Great GPL Purge (2014) by forgettableuser on Monday November 07, 2016 @06:32PM (#12896264)
You are using a disingenuous interpretation of what he said. His quote is: "tie all of our products together, so we further lock customers into our ecosystem"

Yes, he uses the word "lock", but not in the same context we are talking about here.

He is talking about leveraging the connection between their products so say that a person with an iPhone may not want to leave the Mac for a PC because the customer may miss the interoperability/integration features available.

For example, Apple provides their "Continuity" APIs for things like Handoff between iOS and Mac. This is something that Apple can do to make their ecosystem more attractive to customers and discourage them from leaving because it is less likely developers are going to write apps that go to this level of coordination between say your Windows desktop, your Android phone, Pebble watch, and Roku TV.

This strategy does not automatically imply that Mac must be locked down so nobody is allowed to distribute apps outside the Mac App Store.

Re:Apple's Great GPL Purge (2014) by WayneBro on Monday November 07, 2016 @07:17PM (#12896524)
I am not being disingenuous at all. Let's examine the quote a little closer, shall we?

It says "further lock customers into our ecosystem". Obviously, "locking customers into their ecosystem" is a primary goal here and "tying all of our products together" is just one way of achieving that.

It is a way to do it "further" than what they've done already.

> This strategy does not automatically imply that Mac must be locked down...

OK, but we already established that the goal here is to "lock customers into our ecosystem". In light of that statement, do you really think Apple wouldn't jump at the chance to make the Mac OS just like iOS? Odds are that they would love to do such a thing, but they can't for one of the reasons that `belorn` stated above.

Why do you think they didn't make iOS so that anybody could deploy apps to it? Do you really, truly think it was for the purpose of security?

EDIT: I guess my main question for you is, what reason do you have to think that Apple wouldn't want to lock down the Mac OS? That's essentially what `belorn` was asking above.

Re:Apple's Great GPL Purge (2014) by forgettableuser on Monday November 07, 2016 @09:50PM (#12897208)
I personally think they go overboard in the name of security on iOS, for example the banning of JIT and (formerly) dynamic libraries combined with the App review process is overkill. You don't need both.

BUT...context of where this all stems from is important to remember. On the Mac side before the iPhone, the Windows world was getting hammered with security problems and the perception of this was having negative repercussions throughout the PC world. Average users were scared to touch their PCs and especially afraid to try installing new applications. Mac users were the complete opposite of this and their market was dominated by consumers who loved getting (buying) the latest OS updates and buying the latest, coolest apps. Money flowed in the Mac world. But as Mac started getting more attention, lots of different press coverage wondered if Mac could be vulnerable to the same kind of vulnerabilities Windows users were constantly dealing with now that it is a bigger target. So keeping Mac secure for the benefit of their users became a profit incentive for Apple.

On the iPhone side, remember, Apple was walking a tightrope with the phone carrier (AT&T) when they first got started. They didn't have the leverage they have now. Remember that mobile carriers have been obstinate about updates in the name of (their own) "security". They didn't want a bad update, that they couldn't test, somehow bring down the entire cellphone network. Nor did the carriers want nefarious apps that would secretly make expensive phone calls to pay-per-minute numbers. It's no surprise that when Jobs finally was convinced to open the platform to 3rd party native apps, there was some kind of vetting system introduced to appease the mobile carriers from saying 'no'. This is not to say that security was the only thing on their mind and there are other reasons they would like the model they have, but it was a factor. (Consistent user experience is another factor, which is something the App Review process could help enforce since the iPhone was new. Mac has less of this problem because there had been many years of conventions laid down which developers were very good about following in the eco-system already, which is another key difference between the iPhone and Mac ecosystems.)

As for why Apple doesn't lock down the Mac as they do now, the simple answer is that it doesn't help their bottom line in any way. Mac and iOS have very different use cases and heritages. And Apple has been successful with their current Mac carrot/stick trade-off. Most Mac developers I've talked with say that while dealing with the Mac App Store is annoying, they do get a lot more visibility and sales than by not being on the store. Users are no longer confused about how to "install" their apps which saves them customer support costs. (Yes, the open DMG, drag-and-drop to Applications thing is confusing for people.) For indie developers, building a store front and dealing with a payment processor doesn't save them a huge amount of money for what Apple provides for their 30% cut. And remember, sales seem to be better on MAS for most developers so this ends up paying for itself. (And if you are a game developer, you see basically the same arrangement with Steam/Value.)

For those who can't get on the Mac App Store, perhaps due to the technical restrictions, Developer ID for GateKeeper is one option. Apple still gets $99/year for this. And it is worth pointing out, if Apple was truly only obsessed about their 30% cut for MAS, they wouldn't have these technical restrictions and would let anybody do anything on MAS so they could get their cut.

So if Apple decided to lock down the Mac entirely, what does it get them? Most developers are already voluntarily using Mac App Store and Developer ID. Those developers who are not already participating in those systems and not giving Apple money, locking down the system isn't likely going to get any of these developers to hand over any more money.

A lot of these developers are probably making software for their own in-house purposes, developing web sites, or developing for Android. Apple locking down these use cases would only result in people moving back to the PC. And internally, this would probably break all of Apple engineering as they all work on operating system components which don't fit the lock down model either.

And most importantly, remember that Apple's gross margins on hardware is like 40%. If we're talking about chasing customers away, that's a lot of money to lose. Who cares about the cut on a freebie flashlight app, website, or command line tool, which isn't going to make any money, compared to the profit on selling all those $2000 Macs.

Re:Apple's Great GPL Purge (2014) by WayneBro on Tuesday November 08, 2016 @11:54AM (#12901800)
It's obvious to me that Apple won't lock down the Mac OS at this time for the reasons that you and `belorn` mentioned.

That doesn't mean that Apple wouldn't jump at the chance if things changed though. They most certainly would. That's because the primary goal is to lock customers into their ecosystem.

Some Apple fans won't acknowledge that goal and they seem to take offense at that very notion or they start telling you that you're "being disingenuous" for even suggesting it.

Re:Apple's Great GPL Purge (2014) by st3v3r on Monday November 07, 2016 @05:18PM (#12895751)
That's the same for every company, including Google. But that has nothing to do with what we're discussing, which are the improvements to security.
Re:Apple's Great GPL Purge (2014) by belorn on Monday November 07, 2016 @05:03PM (#12895633)
The goal of locking down a platform has been the same on practically every consumer product ever produced that is locked down: To be able to take a cut whenever a third-party product is sold. Been true from everything between a gaming consoles, phones, e-book readers, espresso machines and printers.

Enabling developers and internal business software is nice for PR and market share, while 30% cut on all sold third-party products is a strong incentive to lock down. My guess would be that its the market share towards business that prevents the lockdown, not security or developers, mainly because I suspect it is easier to run the numbers on that and determine what bring most revenue.

Re:Apple's Great GPL Purge (2014) by BoorishBears on Monday November 07, 2016 @08:45PM (#12896951)
That's needlessly painting it as black and white.

It's also not nearly as commonly used as a way to profit off third parties as it is to keep out third parties. The 10NES being a great example, or K-Cups, or proprietary e-book formats or phones locked to carriers.

Re:Apple's Great GPL Purge (2014) by tobltobs on Monday November 07, 2016 @04:03PM (#12895053)
Just out of curiosity (never used a Mac), how to you install all those versions you need? Via a package manager or from source?
Re:Apple's Great GPL Purge (2014) by bearand on Monday November 07, 2016 @04:13PM (#12895169)
There are lots of options, but Homebrew (http://brew.sh/) is the most popular package manager for macOS.
Re:Apple's Great GPL Purge (2014) by panglott on Monday November 07, 2016 @04:16PM (#12895202)
I used the nix package manager for a while, but it's arcane, so I went to MacPorts. Homebrew is obviously the main one, though.

It's always been better to install more up-to-date software, since the system default unix software has been ancient for a long time. It seems like default system Python was python 2.3 or 2.4 forever, although they've upgraded to python 2.7.

Re:Apple's Great GPL Purge (2014) by rhinoceraptor on Monday November 07, 2016 @04:30PM (#12895334)
I've been using NetBSD pkgsrc: https://pkgsrc.joyent.com/install-on-osx/
Re:Apple's Great GPL Purge (2014) by pauloday on Monday November 07, 2016 @04:13PM (#12895170)
Personally I use a package manager called Homebrew. It's pretty good, I'd recommend it.
Re:Apple's Great GPL Purge (2014) by protomyth on Monday November 07, 2016 @05:41PM (#12895907)
macports works fine https://www.macports.org