4 ms·
Also the fact that macOS doesn't actually block unnotarized software...Many programs are un-notarized and just need to give the user the 1 step instruction to b
by ezfe 4y ago
Also the fact that macOS doesn't actually block unnotarized software...Many programs are un-notarized and just need to give the user the 1 step instruction to bypass it
- pmarreck 4y agoYes, and I also never felt the macOS warning about it "strongly suggested it was a virus." That was pretty much hyperbole. And I could also argue that Apple expecting devs to pay a nominal fee to get their app officially code-signed creates a barrier to entry for bad actors who are likely to not want (or be unable to afford) to pay such a fee, especially when that simultaneously gives control to Apple to block the malicious code en-masse once it is discovered.
- richrichardsson 4y agoAlso the fact that you only need to pay the £99 fee once; after the executable is signed, notarised and stapled, that's it. I think there might be a network request if the executable hasn't been stapled, but it's only to check that it has been notarised in the past, it doesn't check for an active Developer Subscription. At least this is my understanding of the situation, I would be happy to be corrected if any of that is wrong.
- mike_hearn 4y agoAlso - you have to sign code on Windows too! If you don't then Edge will try as hard as possible to stop the user opening it, and AV scanners can get very curious about what you're doing. Maybe Steam doesn't care if your game is signed? I didn't quite follow the logic around notarization either. Steam imposes more requirements and takes a slice of revenue! Notarization is a lot cheaper and faster than that. But I guess the idea is that Steam gives you features, whereas notarization is just a tax.