5 ms·
> but you pay for the distribution / tools / OS etc is a common sentiment I see here. No, the yearly fee should pay for that, and the user for the OS. And anywa
by heavyset_go 6y ago
> but you pay for the distribution / tools / OS etc is a common sentiment I see here. No, the yearly fee should pay for that, and the user for the OS. And anyways, what if I don't want to, why cant I distribute it myself?
And if you choose to distribute your apps yourself? Apple still requires you to pay the $100 a year Apple tax, otherwise macOS will treat your app as if it is radioactive[1], leaving users to think that your app is either broken or malicious.
Apple has gone one step further, and now macOS on ARM Macs requires signed binaries, and it will not run unsigned ones[1][2].
[1] https://lapcatsoftware.com/articles/unsigned.html https://lapcatsoftware.com/articles/unsigned.html
[2] https://news.ycombinator.com/item?id=25134352 https://news.ycombinator.com/item?id=25134352
- Wowfunhappy 6y ago> Apple has gone one step further, and now macOS on ARM Macs requires signed binaries, and it will not run unsigned ones. Apple Silicon Macs will not run unsigned binaries, but the binaries can have any signature, so you can just generate one yourself and add it. There's no need for a developer account, or any other external party. And there are no issues with legacy support either, because ARM Mac binaries didn't exist until now (and the requirement does not apply to Intel apps being run via Rosetta). This really isn't a big deal. I was initially worried that mandatory code signing would prevent me from hex editing binaries (which is a thing I do sometimes), but I recently learned that codesign can replace a binary's existing signature. So even that shouldn't be a problem.
- StavrosK 6y agoRight but you understand that this is just raising the temperature of the pot the frog is in.
- simonh 6y agoYour just assuming it’s a pot and want to persuade me to jump into the freezing river instead. But Apple may have no intention to completely lock down the Mac. It may well be just a hot tub, and right now it’s quite comfortable. If it gets too hot, I’ll just get out.
- nunodonato 6y agoNo... you dont understand the analogy. Once its too hot, you don't jump out, you are already cooked. Thats the whole point.
- simonh 6y agoI understand the analogy. You are asserting that it's a pot, but that's just an opinion. Anyway the analogy just doesn't work. Why can't I get out of the Apple ecosystem if it gets too hot, what's stopping me?
- ric2b 6y ago"The boiling frog is a fable describing a frog being slowly boiled alive. The premise is that if a frog is put suddenly into boiling water, it will jump out, but if the frog is put in tepid water which is then brought to a boil slowly, it will not perceive the danger and will be cooked to death. The story is often used as a metaphor for the inability or unwillingness of people to react to or be aware of sinister threats that arise gradually rather than suddenly." In the case of Apple, at some point when they do something you really dislike you might be too invested into the ecosystem and it will be easier to just accept it instead of leaving. But if you were not on their ecosystem already and were thinking of switching to Apple you would just think "Yeah, I really dislike that new move, I'm not buying into it".
- user-the-name 6y agoI mean, if you try this with a real frog, the frog will actually just jump out when it gets too hot. It's just a metaphor. It's not a law of nature, nor is it even a GOOD metaphor.
- Wowfunhappy 6y agoWow, today I learned. I really did think it was real, but looks like it's not: https://www.theatlantic.com/technology/archive/2006/09/the-boiled-frog-myth-stop-the-lying-now/7446/ https://www.theatlantic.com/technology/archive/2006/09/the-b...
- heavyset_go 6y ago> They will not run unsigned binaries, but the binaries can have any signature, so you can just generate one yourself and add it. No need for a developer account, or any other external server or party. And there's no issues with legacy support because ARM Mac binaries didn't exist before now (and the requirement does not apply to Intel apps being run via Rosetta). Self-signed applications are treated as if they're radioactive by macOS, too. > This really isn't a big deal. They've been turning the screws slowly over the last two years. It only takes another turn for them to switch off support for self-signed apps for security reasons. Browsers already do this for self-signed certificates. It's just not something I'm willing to base my purchasing decisions on, nor the decisions about what desktop platforms I target with my applications.
- Wowfunhappy 6y ago> Self-signed applications are treated as if they're radioactive by macOS, too. But not if you turn off Gatekeeper! I can understand how this is annoying if you're creating apps for other people, but in terms of my own personal experience with my computer, the only time I think about Gatekeeper is when I'm talking about it on HN. It gets turned off as part of a bash script I run after installing macOS, at which point it's gone for good. On my list of annoyances with macOS, Gatekeeper is somewhere below the Library folder being hidden by default. I can't say what Apple will decide to do in the future, but I have a very clear line in the sand, and Apple has absolutely not crossed it.
- pushrax 6y agoGatekeeper-by-default is sensible IMO. I've seen how some people interact with these devices, and how easily malware gets on a computer. As long as the walled garden can be easily circumvented, advanced users can do what they wish. "Able to learn about Gatekeeper and decide if they should turn it off" is probably an okay heuristic for "can tell a fake Flash installer site apart from a real one" or even "knows that Flash is pretty much abandoned, do everything you can to avoid it". That said, it absolutely changes the incentive structures, and Apple is also doing it for profit. Will they cross the line in the future, with this goal? I expect they will conclude losing the advanced users would be a net loss.
- benhurmarcel 6y ago> the binaries can have any signature What's the security benefit to this?
- IshKebab 6y agoThere isn't really any - it's just a smaller change than banning unsigned apps completely. Their strategy for forcing people to use the app store is to very gradually make it more and more inconvenient not to. This is one of those gradual changes. Imagine the next ones: 1. You have to enable an option in settings to allow running self-signed apps. 2. You have to disable SIP to allow running self-signed apps. 3. Apps can only be self-signed via Apple's website. etc.
- mmastrac 6y ago#2 is a showstopper for me. Can you at least disable it?
- dcchambers 6y agoI found some more info: https://eclecticlight.co/2020/08/22/apple-silicon-macs-will-require-signed-code/ https://eclecticlight.co/2020/08/22/apple-silicon-macs-will-... Seems like only binaries compiles to run natively on ARM will require signatures. Still seems like its going to introduce some inconvenience for developers/power-users.
- winkeltripel 6y agoSigning bins as part of your build chain seems easy to me.
- onion2k 6y agoDon't self-signed apps expire after a week? You'd need to distribute a new build every week for people to continue to use your app. That's not a major hassle if you're just using your own code, but if you want to distribute something to other people it quickly becomes very problematic.
- saagarjha 6y agoYou can "sign" your binary without any identity associated with it and macOS will let it run. There is no time limit on those.
- dcchambers 6y agoI agree - for commercial development its a trivial step. But it's yet another barrier to entry for students and people that just want to hack on their own computer at will. It's also a potentially dangerous first step towards forcing new versions of MacOS to only run code from verified developers - those that pay Apple. Again, trivial for commericial development, but a major issue for non-commercial use.
- dcchambers 6y agoThe second link seems like a massive problem for developers - but the tweet in that link has been deleted. What's actually happening? If that were true, I couldn't just write some C, Rust, or Go code on my mac, compile it myself, and run the executable file because it's not signed? There's got to be a way (developer mode?) to disable this, right? Edit: Found some more info - only binaries that are compiled to run natively on ARM are affected (for now). Still seems like this will introduce some major inconvenience for developers/power-users. https://eclecticlight.co/2020/08/22/apple-silicon-macs-will-require-signed-code/ https://eclecticlight.co/2020/08/22/apple-silicon-macs-will-...
- dcormier 6y agoBut at some point you'll _only_ be able to run ARM binaries. Rosetta2 will go away. Like how Rosetta went away for non-ARM Mac's, and now they can only run x86 binaries. This is bad.
- Wowfunhappy 6y agoI seriously can't overstate how easy it is to sign a binary. You don't need an Apple Developer account, or an internet connection, or anything other than macOS and a working development environment. Just go into the Terminal and type: > codesign -f -s - [path to binary] Unless something has changed on Apple Silicon, that's it, you're done, the binary has a signature. It does not have a trusted signature, but you don't need one. I think it was just simpler to write the OS assuming all executables would have a signature.
- canarypilot 6y agoDo you know whether this applies to everything which executes? If my build scripts create a build script and run it I guess that will be ok, but if my build scripts build a specialised parser (say, from C source) I need to add a step after linking to code sign the generated parser binary before using it? Is that about right?
- 6y ago
- goodluckchuck 6y agoThe first link is very interesting. The author talks about the alert in terms of a dark pattern, but the notification directly lies to the user stating "cannot be opened." In fact, the app can be opened by simply command-clicking and selecting open. However Apple lies to users in an effort to prevent them from using these applications. Sounds like a possible tortuous interference claim, or possibly fraud. Surely this "warning" serves to prevent users from using apps where Apple doesn't get a cut, and cases them to use apps that Apple does profit from.