55 minutes agoCreated a post • 70 points @ingve • 1 comments
The other peril is not being able to run a docker machine because it’s not available for M1. Which is disappointing because, you know, because you can’t tell customers that your software wasn’t tested in Oracle, and we invented VMs to be able to run any VM on any other machine…Reply
This isn’t the right solution, but I’d be curious to know if these problems disappear in Permissive Security mode (aka Secure Boot off).Reply
In other news, edge case use encounters edge case issues.Reply
It’s almost as if Apple is building their Macs to be rogue nation-state resistant or something. Because otherwise is this almost actually security overkill? (Which does exist, we don’t want TSA Security to enter a grocery store, for example.)Reply
One question: can I finish the setup of an M1 Mac without giving it an internet connection? As in, could I get it from unboxing to desktop without it sending a single network packet to Apple?Reply
Trying to ship software for OSX *in general* drives me crazy, and this seems like more.
This quote: "I’ve been unable to find any information provided by Apple (or anyone else) which explains what’s going on, what the errors mean, or how to address them."
That's my experience constantly.
My development build had weird behavior when I explicitly launch it? Oops, Apple launched a cached version of the app inside a private temp directory (thanks Gatekeeper!) associated with the protocol handler.
But no way to tell until I casually check the process working directory. No documentation indicating how to troubleshoot this.
Countless issues like this.
It seems like these changes have good intentions (i.e. improved security), but introduce a lot of complexity that can have unintended consequences for end-users. This reminds me somewhat of my process setting up UEFI Secure Boot on my Windows PC that wasn't originally configured for it. Not in the exact steps, but in that there is a ton going on behind the scenes and the UX is horrendously bad.
Unfortunately, vendors haven't really thought about how to explain these changes to end-users. They are trying to make them fairly transparent, which probably works at least 95% of the time, but for a small percentage of people, becomes a big PITA.Reply
You don't buy a Mac (M1 or otherwise) to live an adventurous life. You get it because it has really well executed take on an opinionated computing platform that just works for normal people.Reply
Well, this just about confirms the worst nightmares I've had about hardware-based TPM. This "Owner" concept in particular rubs me the wrong way, it just seems antithetical to the idea of general computing.Reply
Fringe use case of using multiple operating systems != peril.Reply