4 ms·
they get a scary security warning that prevents them from running it. The huge difference is that's only a warning, and not a cryptographically locked-down sys
by userbinator 4y ago
they get a scary security warning that prevents them from running it.
The huge difference is that's only a warning, and not a cryptographically locked-down system unlike Apple's.
- gary_0 4y agoCall me paranoid, but I see it as a slippery slope. And for most users that security warning is as good as a cryptographic lockdown anyways.
- userbinator 4y agoThey are certainly boiling the frog slowly. And for most users that security warning is as good as a cryptographic lockdown anyways. On the other hand, I find it ironic how a lot of "security professionals" will complain constantly about users accepting security warnings with no thought anyway (and they usually use this argument to justify their increasingly authoritarian measures of controlling them.)
- charleslmunger 4y agoIt can be simultaneously true that a warning can be a barrier to adoption of your software product versus a competitor, and that a warning is not an effective barrier for a user who thinks they're installing an unreleased video game or going to receive millions of dollars of crypto from foreign royalty.
- heavyset_go 4y agoActually, in a way, it is. All Microsoft has to do is revoke your application's signing certificate and Windows Defender will prevent it from running on Windows computers. Apple does the same thing with Notarization and Gatekeeper on macOS. If they choose to revoke your signing certificate, Gatekeeper will prevent your software from running on macOS. That means if you do, say or compete with something that Microsoft or Apple doesn't like, they can prevent your apps from running on their platforms.
- cyberpunk 4y agoHow come I can run so much software compiled from source then?
- heavyset_go 4y agoI don't know what platform you're using, what app distribution method you used, where the code was compiled, if the code was signed, where it was signed and by who, etc. A generic answer to your question is that the software was signed by whoever compiled or distributed the software, which can include your own machine. Your own key might be in your trust store or your app distribution method might put their key in your trust store. Both macOS and Windows will treat software compiled on the same system it is run on as blessed to run without strict signing checks. On macOS, ad-hoc certificates can be used, but the OS will treat those binaries as if they're radioactive. If you compiled code on macOS, the system will treat that software specially on that specific system and allow you to run it[1]. On Windows, certificates can be added to trust stores. Chocolatey, for example, has their own signing certificate for all of the compiled open source software they have in their repositories, so Windows allows their software to run. The biggest issue is what comes with software distribution itself, where your code isn't blessed by default by the system it was compiled on, or doesn't have signing certificates in the users' trust stores, and Gatekeeper and Windows Defender go out of their way to stop your users from running software with signing certificates they don't like. [1] https://apple.stackexchange.com/a/426854 https://apple.stackexchange.com/a/426854
- cyberpunk 4y agoI compiled it myself. It’s not signed as far as I know. I didn’t disable anything…
- heavyset_go 4y agomacOS and Windows treat binaries compiled on the machine they're run on specially. Checkout out the StackOverflow link in my OP, it gives details on how binaries compiled on the same machine they're run on don't have the 'quarantine' bit set on macOS.