8 ms·
> I also likely bypassed the Gatekeeper warning without even thinking about it, because I run a handful of apps that are still not signed by their developers.
by ianlevesque 9y ago
> I also likely bypassed the Gatekeeper warning without even thinking about it, because I run a handful of apps that are still not signed by their developers.
Apple really needs to fix this. In particular open source applications don't sign for whatever reason and it's clear that barring some change they aren't going to start now.
- valleyer 9y agoWhat do you suggest?
- plorkyeran 9y agoNot having to pay $99/year to sign builds of your open-source application would help.
- Gaelan 9y agoWhich means it is cheap to sign your malware.
- marksomnian 9y agoAnd have your cheap malware signature revoked by Apple.
- desdiv 9y agoMandatory two-factor-confirmation-by-email in order to push software updates on the app store would have been helpful in this case.
- ianlevesque 9y agoYeah I think if it were like many SaaS where open source projects can trivially qualify for a license that might be a start.
- st3fan 9y agoFix what? Remove the option to bypass? Remove the warning? Lock it all down to just app store apps?
- ianlevesque 9y agoNo if enough of them were signed then people wouldn't be in the habit of bypassing the warnings, there's no need to force it to be all locked down.
- theparanoid 9y agoUsers click-through any and every kind of dialog box without reading. It's one of the principles of UI design. Users don't read. Requiring the user to type in "Install dangerous program" would work.
- bjpbakker 9y ago> In particular open source applications don't sign for whatever reason Most open source applications are signed, just not by Apple's Appstore. Instead, most OSS downloads provide a GPG signature. You should not execute downloaded code before checking signatures - either by the Appstore or package manager, or manually.
- strictfp 9y agoA big problem I find with signatures is that I'm not sure what extra security they provide in cases such as this. If the binary can be changed, how can I be sure that the attacker hasn't been able to change the sha1 file or has been able to re-sign with the developer private key?
- bjpbakker 9y agoLeaked keys must be revoked. Whether it's the appstore developer key of a key to sign website packages with. The main difference is that Apple provides a management tool for revoking a developer key, and that OSS projects must have their own trusted server where they publish their public keys (and issue a revocation in case of GPG). I realize that this often is not the /easy/ way. But IMO /no/ software is worth running without verifying its integrity. The good news: the more you verify your downloads, the easier it'll get :)
- clarry 9y agoYou can't be sure. There is no silver bullet anywhere in security. The better approach is to turn that question around and ask what extra security can you gain by not checking the signatures? None? Then it's best to check. Worst case, it doesn't help you at all. Best case, it saves your ass. A win on average, I'd say.