Hacker News Reader

Comment by notafraudster | Hacker News Reader

No, that's not what it means. Currently there are three security tiers for applications on macOS: App Store, not App Store but cryptographically signed, and not cryptographically signed. All three can be run.

That sentence means that in the future, the second category (applications which are not on the App Store but are cryptographically signed) will need you to generate a certificate with Apple. Nothing about the app store's sandboxing rules, and nothing about all applications -- you can run unsigned applications to your heart's content.

View on HN

Weren't most developers already generating a certificate with Apple for the second category? I was paying apple 99/yr when I was actively developing a non-app-store app largely just so I could get the app signed with my developer id. I tried reading into alternatives it seemed like a risky process. Ideally I'd like to pay a bit less if I'm not using the benefits of app-review, but the notarization process seems like a decent compromise.

Even on windows my experience is that signed-non-windows-store apps can get flagged as malicious upon download if they're fairly niche/aren't used by many people, supposedly using an EV Cert helps with that. The user experience is actually worse from my experience (windows will show something red, then you have to click some non-obvious buttons to successfully run the app).

Yeah, Gatekeeper has always had Apple as the sole root of trust. What’s changing is that each app will now have to be uploaded to Apple to be ‘notarized’, rather than signing being a purely offline process with a previously obtained certificate.

> Even on windows my experience is that signed-non-windows-store apps can get flagged as malicious upon download

But I’m Windows, any approved CA can issue a certificate, not just a Microsoft.

Apple’s new regime is not only restricted to Apple being the only CA, but that Apple is the only one who can sign the apps.

That’s immensely restrictive.

It is still a writing on the wall. It makes no sense to tighten the security on signed apps if it is not to prevent unsigned app from running at one point. Which is clearly the direction of travel (and what Microsoft also did with WinRT and Windows 10 S). I don't have to wait until the final destination to not like the direction.

How do you run unsigned code on iOS. e.g. How can I build an XCode project and have it run on my iPhone?

This article is about "Mac Apps", as the title states. I figure—unless posted elsewhere—that iOS hasn't changed and is still as restrictive as ever.

You cannot run unsigned code on ios. However you can, for free, generate codesigning certs (that expire after 7 days).

C’mon, apple will never allow you to run your own code without their say so.

On macOS? You totally can. You can also do the same on iOS, but in a much more limited way.

You can now, but this is clearly a step in the direction of locking down the platform.

It's another slow gradual step toward total lockdown.

I feel like eventually I'll have to abandon Mac, but for what? Linux is still flaky and Windows adware unless you spring for Enterprise.

I would pay for a commercial Linux as polished as MacOS, but there may not be enough of me. (It could also have a list of officially supported hardware to at least approach the stability benefits of Apple's vertically integrated HW/SW stack.)

I mean RHEL Workstation is a very polished Linux environment. It might not be up to date enough for your needs but it's very stable and we'll documentated. Not the best for a laptop though.

I would spring for Fedora or Ubuntu and deal with the lack of paid support for my own personal use but then again I've been using Linux for a while.

Both options are perfectly stable desktops, it's really the commerical software support that will get you.

Ubuntu has Ubuntu Advantage paid support.

Elementary OS is quite polished and takes many cues from OSX.

Not debating Apple's overall trajectory, but I think it's cynical to call this a step towards lockdown. Mitigating certificate forgery attacks ultimately increases trust in software distributed outside Apple's walled garden.

* Assuming Apple never decides to flip certain switches, after the OS infrastructure and hardware support are in place

Turns out that even compiled software can be modified to suit the user’s intent, thankfully.

(Note: Not talking about Apple now, hypothetically...) How would one do this on a fully trust-chained system with processor support?

Barring software bugs that allow for arbitrary code exec as the binary?

Signed package + necessary keys embedded in silicon -> processor verfies signature at memory load -> processor disallows user privilege escalation to write to arbitrary memory

How is this not lock-down? If Apple doesn't like VLC or whatever software competes with their interests they can simply not renew their membership.

Are you talking about the old policy?

You can run unsigned apps. The new policy affects the process for signing apps.

But things like gdb just don’t work unless they’ve been signed. So, if Apple starts blocking unnotarized aogned apps, whether or not these programs will run will depend on whether Apple considers them malicious

You can still self-sign your apps.

I'm in the same spot as you and am eyeing Elementary OS.

What is adware about windows 10? I work on windows 10 pro and it seems fine.

The enterprise Linux distributions have lists with compatible hardware:

https://access.redhat.com/ecosystem/search/#/category/Laptop... https://www.suse.com/yessearch/ https://certification.ubuntu.com/desktop/

Reply on news.ycombinator.com