Live data from Hacker News

The Gates to Hell: Apple’s Notarizing

cdfinder.de

161–170 of 214 posts

Re: The Gates to Hell: Apple’s Notarizing

#161

Earlier quoted context omitted.

I'm assuming it doesn't work well with nested bundle signing. As per my other thread it also seems to be picky about which subdirectories it signs, and there are lots of weird paths (LaunchDaemons, XPCServices, LoginItems, etc) you can put stuff in that needs signed. Not to mention if you put anything needing a sig in Resources.

Hmmm, well I'm willing to believe it then, yeah (although I definitely have a nested bundle setup in a project where --deep works fine... odd). This is good to know though, and hopefully this exchange helps someone in the future too (actually, this would make for a good blog post - this kind of nuance is lost in most of the docs/existing posts).

If you're curious, Quinn (the Eskimo) has more details: https://developer.apple.com/forums/thread/129980

Re: The Gates to Hell: Apple’s Notarizing

#162
The notarization process is super painful, no doubt. I had originally written shell scripts to automate the process for my company, but recently switched to the excellent command line tool 'xcnotary' (https://github.com/akeru-inc/xcnotary). it's available through Homebrew.

Re: The Gates to Hell: Apple’s Notarizing

#163
post #66
post #7

Notarization has been a nightmare of a solution to a problem that isn't effective. You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution. This is just Apple's overreach extended to the desktop. Excessive control that makes developer's lives hell while adding barely…

>You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution. Apple do this too, it's called XProtect: https://support.apple.com/guide/security/protecting-against-... They also have a built-in malware remediation tool, which is presumably what was used when they killed t…

> Notarization is clearly part of a defense in depth strategy for macOS.

The issues being called out here is that it comes at too high of a cost to both develops and users compared to the benefits it provides.

Re: The Gates to Hell: Apple’s Notarizing

#164

The notarization process is super painful, no doubt. I had originally written shell scripts to automate the process for my company, but recently switched to the excellent command line tool 'xcnotary' ( https://github.com/akeru-inc/xcnotary ). it's available through Homebrew.

Thanks for sharing this, I've also got a fairly stable shell script to do the same but I'll strongly consider moving to this next time I have some work to do on the related build since some of its features seem nice.

Re: The Gates to Hell: Apple’s Notarizing

#165
post #66
post #7

Notarization has been a nightmare of a solution to a problem that isn't effective. You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution. This is just Apple's overreach extended to the desktop. Excessive control that makes developer's lives hell while adding barely…

>You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution. Apple do this too, it's called XProtect: https://support.apple.com/guide/security/protecting-against-... They also have a built-in malware remediation tool, which is presumably what was used when they killed t…

A defense in depth would be to have layers of trust for applications, identifying and preventing bad behaviours, rather than trying to lock developers in.

Re: The Gates to Hell: Apple’s Notarizing

#166

The administration around code signing and notarization for both Apple and Windows was huge (1.5 developer months from start to kinks-worked-out for an electron app). Startup lessons learned: don't build desktop apps.

Then again, as a user I’m not sure that I want to trust an organization that can’t afford 50k of overhead to execute unchecked code on my personal machine.

Re: The Gates to Hell: Apple’s Notarizing

#167
post #66
post #7

Notarization has been a nightmare of a solution to a problem that isn't effective. You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution. This is just Apple's overreach extended to the desktop. Excessive control that makes developer's lives hell while adding barely…

>You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution. Apple do this too, it's called XProtect: https://support.apple.com/guide/security/protecting-against-... They also have a built-in malware remediation tool, which is presumably what was used when they killed t…

"defense in depth" should really be shortened to, and called, what it really is: "paranoia".

Re: The Gates to Hell: Apple’s Notarizing

#168
post #66

Earlier quoted context omitted.

>You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution. Apple do this too, it's called XProtect: https://support.apple.com/guide/security/protecting-against-... They also have a built-in malware remediation tool, which is presumably what was used when they killed t…

A defense in depth would be to have layers of trust for applications, identifying and preventing bad behaviours, rather than trying to lock developers in.

>A defense in depth would be to have layers of trust for applications

They do, it’s called…code signing and notarization?

Re: The Gates to Hell: Apple’s Notarizing

#169
post #163
post #66

Earlier quoted context omitted.

>You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution. Apple do this too, it's called XProtect: https://support.apple.com/guide/security/protecting-against-... They also have a built-in malware remediation tool, which is presumably what was used when they killed t…

> Notarization is clearly part of a defense in depth strategy for macOS. The issues being called out here is that it comes at too high of a cost to both develops and users compared to the benefits it provides.

I hardly notice the cost as a user. Sometimes I have to right-click and application to open it the first time, same as it’s been since Gatekeeper was introduced as far as I know.

As for developers, well. Apple clearly do not treat their developers right.

Re: The Gates to Hell: Apple’s Notarizing

#170

Is Apple hostile towards developers? Probably not, but it sometimes feels like it. This is weird.

They put up a ton of artificial barriers and leave them out to fend for themselves often.

I'd say they're probably one of the most developer hostile companies. The only way the look friendly is in comparison with Nintendo.

Post reply on HN