Basically it boils down to: they could have just used iBoot without changing it at all to keep it as a brick like the iPhone/iPad/Watch, but instead they invested plenty of resources to allow it.
With all that work done to allow it, I'm sure there'll be plenty of people inside of Apple who'd protest if someone changes their mind and decides all this has to go away.
You don't own a mac. You can only do on it what it is profitable for Apple to let you do, today.
As much as I respect the incredible RE skills required for this task, I feel like this is shaky foundation unless an unpatchable bootrom exploit is discovered. Even then new models would be patched leaving existing users with an insecure platform that they can't replace when it breaks.
Everyone likes to point at Apple, because that's easy, but it's neither new nor big nor special. There are practically three things at play:
- root-of-trust, if you have a better solution than CA-based signing, by all means, let the world know
- NDA/IP/Lawyerisms
- Apple and many others aren't selling hardware, they are trying to sell experiences or ecosystems, and that is the only reason they exist at all and also the reason a lot of the beige box hardware companies are either less visible, less profitable or both
Is it fun? No. But it's not some sort of automatic malice or 'haha you don't own things but you thought you did' all the time either.
Except that Intel and AMD don't care what you run on your machine, they don't lose money if you don't run their software.
When you run Linux on a MAC, Apple isn't getting money from their iCloud subscriptions and from the store so they have a motive to stop you from escaping the walled garden.
So at one point they could decide that they don't want people to use Linux on their Macs and there's nothing you could do.
Look at what happened to CentOS.
I mean, if they prevent Linux you probably won't buy a mac at all, you won't prioritise using an M1 macbook over using Linux if you're a hardcore Linux nerd.
Bottomline is that yes they are greedy, but they are not trying to stop people from installing Linux on macs just to perhaps earn some extra dollars.
Apple is motivated to do this as soon as they feel they can get away with it and keep profits as high or higher.
For phones, basically nobody wants to run android on an iphone, so it makes no sense to make it possible.
Keep in mind that they don’t lock down iOS because they hate our freedoms, it’s because it is much harder to make it safe and secure if it’s also very open. And since the market of people wanting to run other OSs is so small, they don’t want to take the additional cost.
As to owning you device. Unless you buy real hand stitched shoes with leather soles, your shoes are most likely completely impossible to repair, they’re basically molded rubber. It’s not because Nike hates freedom or even because they want you to buy new shoes more often, it’s because it’s so much cheaper to make shoes that way. But would you argue that you “don’t own your sneakers”?
My gut feeling would say: a bunch of hackers would be happy if they can hack on their code on Apple hardware but run plain FreeBSD or Linux while doing it. But that is not something you run a multi-billion business on...
But in general, running Windows or Linux on macs is not uncommon, it’s definitely not just for hackers.
I don’t have any numbers at all but I’m sure nobody would doubt that it is orders of magnitude more common than people wanting to run homemade OSs on iphones.
Agreed with the underlying point you're making though. They allow this because it aligns with their current strategic objectives, and changes to those objectives can be arbitrary and capricious, at least from the viewpoint of the consumer.
But I could be wrong.
the timeline was something like this:
- Sony released the original PS3 with Linux running under a hypervisor that locked certain things (e.g. 3D rendering and their DRM)
- Sony released the PS3 slim without Linux. They claimed they didn't have the resources to make Linux run on it. (We later figured out all that was required were a few incredibly simple kernel patches)
- geohot found a somewhat unstable hardware glitch that, with some luck and a few tries, could escalate to hypervisor mode and enable e.g. 3D rendering from Linux. Their DRM was still untouched at this point and no one really cared.
- Sony released an update for the old PS3 models to disable Linux as well citing "security concerns"
After that more people started looking into the PS3 and marcan, me and others at fail0verflow eventually figured out their security wasn't all that great. It was actually so bad that we could calculate their private keys. Then they sued us for that but that's another story.
We talked about how you could compute private keys but didn't release any keys for obvious reasons.
Essentially Sony had N different sets of keys protecting different levels of their system (e.g. one keyset for the hypervisor and another one for the kernel). What we found allowed to compute the private signing key given two public signatures.
Due to some technicality this meant that you needed another bug which allowed to extract these plaintext signatures. (The best comparison today would be that we found a universal code execution bug but you still needed to find your own info leak to defeat ASLR which we either didn't share or didn't have for all keysets).
What happened then was that geohot used this flaw we found together with a simple bug that leaked two plaintext signatures to extract one of the most important keys and published that one on his website.
Sony responded by suing him and us as well - probably because they assumed that we worked together. After a few month they reached a settlement with geohot where he promised to never hack any Sony product ever again. At the same time they simply dropped the lawsuit against marcan, me and a few other friends from fail0verflow without having ever served us. Those months resulted in quite some stress for me and personal and legal issues for another friend.
They may have wanted to make it harder to jailbreak. Another argument is that they weren't profitable to sell as computers but largely become profitable via the money they made off games sold for the platform including money paid by game developers.
But you cannot expect that Apple should give you a legally enforceable contract (or whatever) pertaining to a product you haven't bought yet and they haven't even made yet.
The fact that the boot process on the M1 chip is explicitly not locked down on release is at least showing a modicum of goodwill.
...I don't think this is going to happen, and Apple probably doesn't either.
Wether Apple would develop Bootcamp for ARM or not is purely theoretical discourse until then.
Apple is now the vendor of at least the GPU. I don't think they're going to write a Windows driver for that - the incentives are just not there.
And you can actually download Windows on ARM from Microsoft Insider Preview for Free. And run it on top of Parallels Desktop 16.
What you were possibly remembering was that Windows on ARM when it was first introduced only supported emulating x86 apps. Although x64 emulation is currently in preview.
https://docs.microsoft.com/en-us/windows/uwp/porting/apps-on...
I'd still call it something we hope to see in the future, instead of a working proof of concept.
They do have the chops for it since they have done Xbox and Hololens and various other devices in-house.
> They do have the chops for it since they have done Xbox and Hololens and various other devices in-house.
Not sure about the Hololens, but the XBox contains an x86 AMD processor.
But even if they are, it would make sense to release Windows 10 for the M1 and getting Win-developers to start porting their applications to ARM, so they could leap-frog Apple on ARM if they manage to build a 'better' ARM SoC
There are rumors.
As for “why are there so few ARM versions of apps”, that’s purely the vertical integration piece again. Apple makes it very clear the old tech line is dead so developers have a clear thing to explain to their management. Microsoft tries to keep everyone happy which means devs are like “I’ll wait until this actually has industry buy in” which then Microsoft uses as “well there’s no interest here and maybe the tech won’t work out/vendors won’t materialize” and “we can’t ask our customers to pay this transition cost”.
I'd think linux/BSD drivers would be the concern here!
It's a whole pile of code that Apple doesn't need, and could've just removed or never written in the first place, that was written explicitly and only so people could run unsigned kernels on Apple Silicon macs.
Yup, the wiki is almost empty - I was hard at working getting the site/IRC/branding/etc worked out. Expect things to pick up steam on that front starting tomorrow, as I will now focus on hardware documentation and getting things through low-level boot bring-up.
I would point out that Apple has permitted booting alternative operating systems throughout their m68k (at least the m68ks that could meaningfully boot Linux or a BSD derivative) [1], PowerPC [2], and Intel [3] phases. It's only on Intel they actively made this a feature, because Windows Bootcamp probably allowed to sell them a certain percentage more Macs.
The only reason to believe they would change this is that the Apple Silicon architecture changes would have Apple be interested in the Mac being some sort of equivalent to an iPod Touch. I don't really see Apple being interested in that, and Apple reps have gone on record to argue similar points as well.
[1]: e.g. https://wiki.netbsd.org/ports/mac68k/ [2]: e.g. https://wiki.netbsd.org/ports/macppc/ [3]: Uh, anything that boots on x86 EFI will probably boot.
I don't see any great difference/reasons why the iPad pro is locked, and a MacBook isn't.
I hope Apple "computers" will remain unlocked, but I'm not sure I see a real business case for Apple to keep them open.
Apple gives the chance to disable these limitations to power users: "they should be disabled by default!"
Apple disables limitations: "temporary convenient oversight?"
...
Mind you, not all bad faith arguments are unwarranted. I kind of get where it comes from. But it's important to recognize that's that what it is, and there's no reason to actually believe it.
What is the difference between an iPad pro and a MacBook? If Apple can get away with a 30% tax on all commercial software, and arbitrarily manage which applications are "allowed" - why would they not want to extend that to their laptops? If they still get people to buy and developers to develop?
Well they won't get away with that at all, especially not in the long run as people abandon ship to platforms that do allow free development and tinkering. Apple is still a hardware company with hardware sales making up the overwhelming majority of their profits (over 75%). It would be beyond stupid to risk that just so they can live out a control fantasy, especially because they don't need to live out that control fantasy to make good money from the Mac App Store.
Before the M1 Macs shipped, Apple's Mac revenue hit an all-time high of a smidge over $9 billion [1]. During a global pandemic and economic crisis.
The Mac will be 37 years old on January 24, 2021 and yet, it continues to gain momentum, not lose it. Between 1984 and now, not a year has gone by without the same narrative: Apple is doomed if they don't change their ways…
The M1 Macs are probably selling like proverbial hotcakes—we'll find out on January 27th [2].
People seem to forget that the Mac mini, the MacBook Air and the 13-inch MacBook Pro are the entry-level, consumer oriented computers in Apple's lineup. These machines are the opening act.
And even as stunningly fast as these machines are, especially on a performance per watt basis, we haven't even seen the take-no-prisoners, kick-ass professional Apple Silicon Macs yet.
We’ll probably see Macs from Apple that don't have the space and power constraints of the current lineup. If they cranked the current SoC beyond the current 3.2 GHz, added more cores and started at 16 GB of RAM… they would capture another huge chunk of the market, including a significant number of Linux users…
[1] https://www.apple.com/newsroom/2020/10/apple-reports-fourth-...
If Apple truly had this strategy they're doing a horrible job at it. Mostly since you are free to boot (or work on doing so at least) NetBSD and countless other things on practically every Mac they've ever released, including the latest ones. They're doing a horrible job at communicating this strategy too, because they're communicating the opposite. For this Apple Silicon phase, it seems they've also missed a huge opportunity to finally execute on this strategy by spending a little time and money to develop the tools to do the opposite of that strategy and give users a way to boot unsigned kernels.
I just don't buy it, sorry. I don't even get why Apple would want to do this outside of sheer malice.
Goes in both directions.
> Mostly since you are free to boot (or work on doing so at least) NetBSD and countless other things on practically every Mac they've ever released, including the latest ones.
Gatekeeper wasn't a thing either, until it was, indeed, a thing.
> They're doing a horrible job at communicating this strategy too, because they're communicating the opposite.
Surely that's the whole point of a trap?
> For this Apple Silicon phase, it seems they've also missed a huge opportunity to finally execute on this strategy by spending a little time and money to develop the tools to do the opposite of that strategy and give users a way to boot unsigned kernels.
Sure, because right now they're trying to sell the idea of M1 Macs.
> I just don't buy it, sorry. I don't even get why Apple would want to do this outside of sheer malice.
App Store, censorship, ... You could turn that around and ask why they would want to lock down their iOS devices, and why you think that those reasons wouldn't apply to Macs.
I've been hearing about this supposed secret Apple plot to lock down the Mac and take away third party software distribution and operating systems for a decade now. If this is indeed Apple's plot, then they're really slow at implementing it. Maybe they'll sort it out in another decade.
They could do it on mobile thanks to the vastly superior user experience.
When steve jobs announced itunes on windows he said "hell froze over". That should tell you how much they take openeness into consideration.
I'm still waiting for iMessage to be an open protocol, or for my iphone to be able to use a standard charging cable...
I mean, this is exactly the bad faith argument I was talking about right here. If you want to view this as smoke and mirrors until they "trap" you by all means go ahead, but it does shut this conversation right down.
This is not theoretical.
There is also no way to turn off the persistent, hardware-serial-number-based APNS connection to Apple, tracking the system from IP to IP whenever it's on, even when no apps are running.
You also can't wipe and restore a mac with filevault without an online reactivation from Apple, even if you have local bootable install media.
There are several concrete, technical advances toward the thing they are claiming not to be doing. macOS is indeed becoming more like iOS every release. It's not just unfounded paranoia.
And if you don't like it, just switch it off.
How could activation lock possibly work otherwise? Once wiped, it doesn't know if it's activation locked anymore.
Or rather, maybe you'd like to explain what you think Apple would have to gain from doing something like that?
"Apple checks which macOS applications I run in order to verify that the developers credentials are still valid and not expired/revoked, but only for macOS apps and not executables in general, and you can still open apps that are not signed with a Developer ID using a manual bypass" (which is certainly not ideal but seems like a reasonable security compromise. There's no evidence they're keeping a list of this information anywhere.)
to:
"Apple will lock down macOS and make it utterly impossible to run any executable or even scripting code that hasn't gone through a strict review process"
Since you're unwilling (or unable?) to explain that leap without just spouting pithy 3-word comebacks, I guess we're done :)
1) cannot be called "fully unlocked",
2) more locked than what people used to have, even on Apple devices.
It might be fine for you, but it certainly is potentially bad for privacy and freedom. Look up keyword "tor" in the thread if genuinely want to understand and not trolling.
You can disagree with the tradeoffs Apple decided to make in the name of security/privacy, fair enough. And you can certainly blame them for their mistakes (like not thinking to handle a case where their Developer ID verification servers were offline). But practically, these tradeoffs don't really hamper almost anyone's usage of the OS, and the few people for whom it does can disable them.
Of course not, because they need to differentiate. This doesn't mean they renounce their plans to further lock down macOS. Running non-appstore apps is getting harder and harder each year.
For a company that seems sometimes to go out of its way to not give any information on anything it doesn't make sense to clearly and concisely make that statement.
There’s not a single piece of access I’ve lost. It’s a couple of dialog boxes.
i wonder how much of this is thanks to peoples "gnashing of teeth" about mac getting an iphone lockdown
in the end its speculation, but id wager a guess apple wouldnt have a big problem locking down macos if people didnt make a big deal out of it
Just a note - it's often very easy to measure the validity of your ideas by considering the economics of the ideas. Apple effectively neutering development on their premier general purpose computer would obviously reduce the amount they sold. The same isn't true for the iPhone, which effectively no one develops on.
Considering the level of GUI work that outright supports this feature in recovery mode on an M1, I'm inclined to think it's not an oversight.
Basically nothing can be known to be indefinite. But Apple has signaled that they'd be open for ARM Boot Camp if Microsoft was to sell non-OEM Windows for ARM licenses. So it seems like Apple might consider multi-booting a feature.
The fact that Apple documented it.
If you get Linux developers onto your platform, you unlock the server market, I assume. I don't get why Apple would not open that possibility for their silicon future.
I think a downside to have Macs running Linux would be extended hardware support and evasion of their obsolescence strategies.
Overall, I think they could win a lot, so there is a desperate hope they change their minds on that. At least, I would be completely lost on them, if AMD manages to match their performance and there gonna be well-screened AMD laptops.
Apple, you got this current advantage to win people like me over. Once the others catch up, this opportunity will probably not arise again, as I will never ever settle on MacOS or Windows, especially with the current course of increasingly restricting how I could use a >1.5k€ device.
If the M1 Air had proper Linux support (at least committed), I would buy right now in an instant. I naively believe, if you don't get Linux people like me, Apple's silicon endeavour will not get a hold in the larger CPU/GPU market.
Could not the same be said for any computer manufacturer? How do we know for sure Dell won't start locking down future XPS models?
One should be naive to think that the conversion to M-series wasn't done with the intention to lock the macOS platform akin to iOS.
I wouldn't be even surprised if doing so didn't attract anti-trust issues as they got away with iPhone, iPad which are not lesser computer than a PC especially since several applications are becoming 'mobile first' or even 'mobile only'; So it's ridiculous to compare smartphones, tablets to game consoles whenever this topic is brought to the discussion.
Apple could take most of the speculation/hostility away by simply giving their word for it. But they don't ...
> Apple allows booting unsigned/custom kernels on Apple Silicon macs without a jailbreak! This isn’t a hack or an omission, but an actual feature that Apple built into these devices.
Indefinitely? How do we know it's a feature vs a temporarily convenient oversight?
> Our goal is not just to make Linux run on these machines, but to polish it to the point where it can be used as a daily OS. Doing this requires a huge amount of work to be done, as Apple Silicon is a completely undocumented platform. In particular, we will be reverse engineering the Apple GPU architecture and developing an open source driver for it.
This looks like the major bullet point. The wiki is currently empty, but while it's WIP, it would be nice to see some of the major milestones or breakdown of the goal mentioned above.
Best of luck to Hector and the contributors!