6 ms·
Use macOS Recovery on a Mac with Apple silicon
- ezluckyfree 6y agoHas anyone tried booting linux natively?
- sys_64738 6y agoDrivers?
- wtallis 6y agoI suspect the easiest route would probably be to get USB (or full Thunderbolt) working first, then connect well-supported peripherals through a hub until the built-in stuff can be supported. If Apple's USB host controller uses standard XHCI, then the bootloader is probably a bigger challenge than getting enough drivers to start productively hacking on the system.
- sigjuice 6y agoCool. Now all we need is for someone to make such a non-macOS system and actually boot it.
- lathiat 6y agoSeems unfortunate that to boot something unsigned you have to disable SIP, e.g. once we have a working linux port (I'm sure it won't be long) to enable booting it will reduce my OSX security at runtime [and not just from the boot chain].
- sedatk 6y agoBooting something unsigned would remove the security anyway, wouldn't it?
- pabs3 6y agoSome of the Linux distros have signed bootloaders/kernels for SecureBoot on PCs, so it would be good if that same model could be allowed on macs.
- judge2020 6y agoGiven the state of signed firmware, I think Apple is in the right - https://arstechnica.com/information-technology/2020/07/new-flaw-neuters-secure-boot-but-theres-no-reason-to-panic-heres-why/ https://arstechnica.com/information-technology/2020/07/new-f...
- silly-silly 6y agoI think that the two are at best tangentially related.
- lathiat 6y agoIt removes some specific types of security, but System Integrity Protection is a "runtime" protection on OSX. It disables access to various files/etc even as root unless in the right context. So it seems unfortunate to have to lower the level of runtime security for OSX, in order to enable booting unsigned software. As they shouldn't be strictly related.
- sedatk 6y agoMy understanding is that if boot security cannot be established, it's impossible to assert runtime security either. Otherwise, a compromised code in the boot process can also alter how SIP behaves, essentially invalidating its security function.
- zabardasth 6y agoI was paranoid for a long time about things like SIP and SecureBoot but think of it this way. What is the likelihood that you are infected by a bootkit versus some 0day that affects your browser? My main beef w/ rootless/SIP/Gatekeeper and these types of technology is that you no longer own your hardware, you are a slave to the HW manufacturer.
- gjsman-1000 6y agoYou know you can disable SIP and Gatekeeper, right? It's just two terminal commands.
- jbverschoor 6y agoYet at the same time you get roasted on here if you run things as root. It’s pure bs.. Apple has top notch engineering and architecture. Others always follow.. in terms of hardware, but also software
- kevinlou 6y agoWould be hilarious to see Surface RT natively boot on an M1 system
- Zenst 6y agoHoliday season is upon us, can bet somebody will port Android for the heck of it.
- oneplane 6y agoThat's been done already; Pongo OS and Sandcastle were running on the devkits, unless some huge change is made to the M1 it should run all the same. Problems so far were lack of device drivers; there isn't even disk access right now because there is no NVME Controller driver made yet (well, except the one in macOS and iOS of course).
- mariopt 6y agoNot sure if this is apple opening the doors for linux/windows or just a way to install enterprise boot loaders. Bootcamp is not migrated yet but it wouldn't require disabling boot security since it's done by apple itself.
- Technically 6y agoWhat exactly is bootcamp if you don't install windows? I know I need it to dual-boot my mac with linux but it's not clear why.
- nijaru 6y agoI don’t think bootcamp has ever been a requirement to boot into linux on a mac, and I never have used it to do so on various macbook pros over the last ~10 years
- wtallis 6y agoInitially, Bootcamp for Intel Macs consisted of three things: 1. a BIOS compatibility support module (CSM) for Apple's EFI firmware, allowing legacy bootloaders and option ROMs to be used. (Macs released after the first version of Bootcamp came with a CSM out of the box, while earlier Intel Macs needed a firmware update to provide the CSM.) 2. a collection of Windows drivers for the peripherals shipped in Intel Macs 3. a graphical tool to assist with the process of installing Windows (partitioning, etc.) Linux never needed (2), and (3) was always more of a convenience than a necessity. The need for (1) lessened over the years as both Linux and Windows gained full support for booting from UEFI without a BIOS CSM, and as Apple's firmware evolved to more closely resemble UEFI 2.x than EFI 1.10.
- deleted 6y ago[deleted]
- Zenst 6y agoDrivers will be the hurdle and how open source friendly the SOC is will be down to Apple.
- api 6y agoI personally think it would be in Apple's interest to publish the information required for FOSS drivers or even assist with them. It would help them sell more Macs, but more importantly cement their dominance among developers.
- webmobdev 6y agoThat is wishful thinking - Apple is not known to do anything that can open up their system and breach their walled garden. ARM Macs are designed to turn even the desktops to iPad / iPhones where you have no control or choice.
- threeseed 6y agoThis is not remotely true. Apple has had plenty of opportunities over the years to take down the Hackintosh community and they never have. In fact Craig even said they fully supported it. And whilst their Mac devices are secure by default they have always made it possible to weaken the security when needed.
- webmobdev 6y ago> Apple has had plenty of opportunities over the years to take down the Hackintosh community and they never have. Why would they bother with it when it doesn't effect their bottom line at all? In fact, it benefits them as these users may like the platform and migrate to it.
- chaosharmonic 6y agoHonestly? Strong agree. A huge part of my general distaste for them as a user is rooted in their resistance to standards. (See: Lightning, AirPlay, their fucking keyboard layout that's so shuffled it also breaks default app-level shortcuts that work on every other device and operating system I use...) But to that exact point, if I could get my hands on an ARM Mac Mini, stick Linux onto it, and throw any of a variety of use cases at it? At that power envelope, with Thunderbolt 4, and my own input devices? I would genuinely consider switching away from DIY builds for a while. (...even more so next year, when WiFi 6E and BT5.2 have also trickled out.)
- blinkingled 6y agoThis is absolutely the right thing to do and it's quite assuring to see they put out a clear cut support article for this so quick. However without the specifications for the security chip, GPU, SoC - running an alternative OS on the M1 Macs is very much a no-go. Apple could work closely with Microsoft to get Windows/ARM working on their ARM implementation but I am sure that's way more work than was Bootcamp. (Apple proprietary firmware is a big question and so are the various drivers obviously). This is why ARM is a mess that isn't worth dealing with even with better performance per watt. What would be really great is if Apple did what Dell does - Make a downloadable Ubuntu ISO with drivers and firmware integration available that works as a fully functional alternative OS. Or make the h/w specs available so people can do the work themselves. I am well aware none of it will actually happen but nonetheless it would get more people to buy into what seems to be an excellent hardware platform.
- rektide 6y agoThis system seems to only have an "Apple secure mode" of sorts, & a gradient of less secure modes. In contrast, in the regular PC ecosystem, there's what seems like a reasonably effective user-empowering situation, SO FAR, where computers have been coming with UEFI Secure Boot[1] for over half a decade. I don't fully understand what is required to generate secure boot images & possible foibles or potential confounding factors, but it's seemed like the base requirements[2] include the system advertising it's core "platform key" & allowing users to create their own securing keys based off this, to upload those keys, & there-by allow user-signed images to boot, securely. One of the best guides to this all is the NSA's[3]. The contrast is that Apple seemingly let's one disarm the boot security system, where-as Secure Boot, so far, has allowed users to put the security system to work as they please. Worth mentioning Chromebooks. I'm even less familiar with the particulars of their boot system, but they most-often have a "developer mode"[4], which disarms the OS protection mechanisms allowing one to install whatever onto the system. Fun fact, on Chromebox systems, this either is or was often achieved by opening the case & removing a specific screw. Once developer mode is enabled, the system will at boot-up show an image notifying the user that the system is insecure, & will boot unsigned code & allow modification to the drive. And worth mentioning Android! You the user almost never have power over your system. Once your device is no longer maintained, throw it away, because there's nothing you can do to it & in an unmaintained state it is almost certainly insecure. Maybe some intrepid hackers will have found some exploit to bypass the protection mechanisms, and maybe, maybe, you bought one of the probably <1% of devices that still has an unlocked bootloader, and in these exceptional cases you can probably get your own well maintained OS like LineageOS on your device, but for most people, you have no control & can do nothing to your device that is not approved, and the security system is very much designed to keep you out of your own device. > However without the specifications for the security chip, GPU, SoC - running anything on it is practically meaningless I'm having similar thoughts about Microsoft's recent announcement, that they have partnered with Intel, AMD, and Qualcomm to get their custom Pluton security chip[5] embedded in seemingly most major cpus going forward. Where-as Google begot an "open source root of trust" system based around the open hardware RISC-V chip[6]- something that can be inspected, checked out, & deployed in new designs gratis- Microsoft seems to be relying on a high degree of trust in their systems & engineering & how that will ultimately empower and/or exclude the user. This new silicon we expect almost literally everywhere comes at a time when Microsoft is about to make a critical requirement of many of the Secure Boot technologies that have been building[7], with a January 1st deadline for Secure Boot support. Also worth pointing out some of the secure-boot related "whoopsies" that have happened[8][9], recently, & further back. Overall, all this flurry of activity around securing that's happened so quickly has made me prsonally a little nervous, a bit on edge. Thusfar UEFI Secure Boot has seemed to continue to give the user respect, power over their system, & been quite ahead of the pack in doing so. But it's intimidating how much we are taking on faith, hoping that we continue to retain access. The glossy media-blitz PR of Pluton was ultra-light on technical details; that was intimidating. I want to believe the PC platform continues to be a place for open innovation & where users have the power to maintain their systems & keep control over them, if they want to do so, and in all likelihood Secure Boot and whatever Pluton ends up being probably will continue to help us in that. But it always feels like the keys could be snatched away, that someone could make some decision, & PCs could close off, like so vary many other platforms. Notably also, to my understanding, UEFI Secure Boot does not require users to be able to remove the systems signing keys, so Microsoft & the manufacturer will retain access to the boot layer of your system no matter what. (I'm not sure about this.) [1] https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Secure_boot https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_In... [2] https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-secure-boot https://docs.microsoft.com/en-us/windows-hardware/design/dev... [3] https://media.defense.gov/2020/Sep/15/2002497594/-1/-1/0/CTR-UEFI-Secure-Boot-Customization-UOO168873-20.PDF https://media.defense.gov/2020/Sep/15/2002497594/-1/-1/0/CTR... [4] https://chromium.googlesource.com/chromiumos/docs/+/master/developer_mode.md https://chromium.googlesource.com/chromiumos/docs/+/master/d... [5] https://www.microsoft.com/security/blog/2020/11/17/meet-the-microsoft-pluton-processor-the-security-chip-designed-for-the-future-of-windows-pcs/ https://www.microsoft.com/security/blog/2020/11/17/meet-the-... [6] https://techcrunch.com/2019/11/05/google-opentitan-secure-chip/ https://techcrunch.com/2019/11/05/google-opentitan-secure-ch... [7] https://redmondmag.com/articles/2020/06/11/windows-server-hardware-security-requirements.aspx https://redmondmag.com/articles/2020/06/11/windows-server-ha... [8] https://www.computerworld.com/article/3528302/the-mess-behind-microsoft-s-yanked-uefi-patch-kb-4524244.html https://www.computerworld.com/article/3528302/the-mess-behin... [9] https://www.zdnet.com/article/microsoft-secure-boot-key-debacle-causes-security-panic/ https://www.zdnet.com/article/microsoft-secure-boot-key-deba...
- thought_alarm 6y agoThis is pretty old news; it was all covered at WWDC in the summer. It's still nice to see a thorough official writeup, and it will be interesting to see what the hobbyist hacker community comes up with.
- gjsman-1000 6y agoTrue, but there is a widespread misbelief because of the misquoted Craig Federighi that only macOS would be allowed. Craig was saying that they wouldn't "support" booting other operating systems and wanted people to use VMs, but this was widely misunderstood as him saying that Apple would actively not support instead of passively not supporting other OSs.
- webmobdev 6y agoI mean, if Apple doesn't release any drivers for its hardwares, then it is effectively true - you won't be able to run anything other than macOS on it and will have to depend on VMs for other OSes. Let's not forget that Apple moved to ARM Macs not only for increased profit but also to exert even more control over Mac desktops and turn them into ios like spying client terminals where you can't run anything on it not approved by Apple or without their knowledge.
- gjsman-1000 6y agoYes, but the misunderstanding was that an option like "Permissive Security" wouldn't exist - that you would have no possibility of anything but MacOS. It does exist, but Apple's just not going to help you with that. Also, to unlock your Mac: 1. `csrutil disable` to disable SIP 2. `sudo spctl --master-disable` to disable Gatekeeper and allow apps from anywhere And finally, the whole thing about MacOS Spying on every app you opened and bypassing VPNs - turns out, both stories had some fake news to them. It was actually the developer certificate (not the actual app), and Apple has announced they are building a new protocol with more failsafes to prevent a repeat of the previous incidents. As for the "bypassing VPNs," that's actually not true at all. System-wide VPNs still do work in Big Sur, it's just that the API that Little Snitch used for app-specific traffic redirects doesn't work on system apps (although system apps still respect system-wide VPN settings).
- ctpide 6y agoDoes this actually mean that LittleSnitch could continue to function as is - with the same kernel extensions used until now? > To allow installation of software that uses kernel extensions, select the “Allow user management of kernel extensions from identified developers” checkbox.
- Jdjdjdjjdhebe 6y agoI'm a big ape hardware fan, I mean it's the best there is. As soon as I can run Linux properly on one of these I'm buying. So good to see it may happen
- ogre_codes 6y agoMy big concern with my Mac isn't that I want to run Linux (or ack! Windows) on it. If I was buying a PC for Windows or Linux, I'd buy something else. My big concern is that in 10 years+ or so, it's likely my Mac won't be supported by Apple any more and there is a good chance it'll still be running. Right now I'm pretty sure I can still bodge together a Linux distro to run on my old iMac G4 sitting in my garage. IMO that is where Apple supporting booting alternative OSs is the most important bit. In 10 years (heck maybe 5 years), it's likely many of the drivers and whatnot will have been reverse engineered and we'll be able to boot up Linux and get another 10+ years out of it.
- Wowfunhappy 6y ago> If I was buying a PC for Windows or Linux, I'd buy something else. Sure, but the ability to occasionally boot Windows or Linux is nice. I've used both on my Macbook Air for various reasons—mostly games on the Windows side, but also some technical Linux stuff that wouldn't have worked in a VM.
- ogre_codes 6y agoOh don't get me wrong, I am very happy Apple is leaving this open enough you can cross boot. But for me personally, it's more about the long term than next month. I suspect it's going to be at least a couple years before someone gets a Linux or Darwin/ BSD build going on this guy regardless.
- jeppesen-io 6y agoAre there any non-Apple OSs that run on iPhones?