6 ms·
Headline says "sighed with Apple ID" as if that's a bad thing, but it's actually a good thing, as it means Apple has already revoked the Apple ID (and presumabl
by eridius 14y ago
Headline says "sighed with Apple ID" as if that's a bad thing, but it's actually a good thing, as it means Apple has already revoked the Apple ID (and presumably the associated certificate), so as soon as your computer updates its certificate revocation list, it will refuse to run the application (even if you try to bypass gatekeeper).
- smackfu 14y agoGood and bad. Actually, bad right up until Apple revokes the cert.
- recoiledsnake 14y agoSpear fishing seems to a big problem these days. Not sure if there is any other way to stop it except to educate people not to click on links in email or to sandbox and totally lock up the system like the iOS App Store and Windows Store do. If you can install Firefox, you can install malware.
- pflats 14y agoGatekeeper really can't do much against a spear phishing attack. If someone's running a scam specifically to target a single person or a small group of people, and has spent the time and energy figuring out how to get them to open a malicious file, having an Apple ID is a $100 speed bump. Gatekeeper is meant to prevent a wide-ranging attack. If you've got someone custom crafting an attack vector for you specifically, you've got some serious problems. I don't think Gatekeeper adds any more false security than an antivirus app would, and I don't know of any software that'd prevent an attack like this. At best, it adds a small amount of information for authorities to try to track the attack. I doubt it'll be fruitful, but it's better than nothing.
- cooldeal 14y ago>I don't think Gatekeeper adds any more false security than an antivirus app would, and I don't know of any software that'd prevent an attack like this. It helps if you're using a non-rooted Chromebook, iDevice or WindowsRT device. Then the attackers have to look for exploits in the mail client/OS instead of just sending a link to a .dmg or .exe.
- awakeasleep 14y agoI'd go as far as to say, if someone is spending the money to hire a competent foe to attack a specific person who isn't a paranoid security expert, there isn't much chance they'll escape uncompromised.
- duaneb 14y agoExactly. We're all lazy because we only expect general attacks, we expect that we won't be the first person attacked.
- pi18n 14y agoWhat I don't like about Gatekeeper is that there is no way to revoke Apple's cert and replace it with another. Not that that would protect the activist in question, but it would certainly make a company machine secure against this kind of attack.
- eridius 14y agoIf I understand you correctly, it would also prevent you from launching any codesigned application, including the OS-provided ones, since they would all be considered to have an invalid code signature. So yeah, I guess in a certain light, a machine that can't launch apps is definitely secure.
- pi18n 14y agoGood point. I think you half misunderstood; their certificate should be replaceable so that you disallow third-party software from developers in their developer program and allow it from your company only or vendor A only. Obviously one would need to implicitly allow certain OS processes and Finder for the system to work, but my point is basically that we should not be beholden to Apple beyond that, the CA should be something we can choose.
- defap 14y agoThis doesn't make sense. The effectiveness of the spear-fishing attack had nothing to do with Gatekeeper. Signing the app with an Apple ID provided for a straight-forward way to disable the attack, which made Gatekeeper a pure win.
- throwaway125 14y agoYou can hardly call that good. It's like saying that Diginotar being compromised was good because then we could untrust their CA. It's true that we could do that, but their original purpose was to protect us in the first place. The same is true for code signing certificates, to a certain extent.
- glhaynes 14y agoThe purpose of requiring code signing certificates for default trusted execution on OS X was to make Apple able to blacklist IDs used for malicious purpose (and perhaps to create at least some financial/identification trail). What more would you have wanted code signing to do here?
- wyager 14y ago>it will refuse to run the application (even if you try to bypass gatekeeper). That sounds kind of shitty to me... Is there any simple way around that?
- glhaynes 14y agoI don't know if there's a way around it but my first thought is that if you're hardcore enough to be needing to run code that's signed with a blacklisted ID, you're way more than hardcore enough to be able to easily make an unsigned (so can't be blacklisted) version of the binary. So if I were Apple I wouldn't waste much time or UI space on it.
- wyager 14y agoThat's a very valid point. I'm just worried about Apple's blacklisting mechanism being subverted, but I suppose stripping signatures isn't hard.
- eridius 14y agoYou can bypass Gatekeeper for unsigned apps. And you can run signed apps. However, Gatekeeper refuses to let you bypass it for an app whose code signature is damaged or otherwise invalid. This is a feature. If you really truly want to run the app anyway, you can always strip off the code signature.
- orbital303 14y agoIt is a bad thing. If that developer was responsible, he can be held liable. Likely, he wasn't and someone signed the app with his key. This single point of failure (assuming that all developer keys will be guarded, never lost, stolen) for the whole system turns into hundreds of thousands of single points of failure (or however many developers currently have the ability to sign for apps, including internal Apple employees and contractors) and can come from any developer, even the well intentioned ones. The whole gatekeeper system is a way to get more money out of customers while seeming to provide more security. It obviously doesn't. I would be my life's fortune there are apps with malware in the app store right now. This walled garden concept may be working for mobile phones now, while they are still in their infancy, but is a surefire way to turn away knowledgeable users and make a ton of money off the ignorant ones (which make up 99.9999999% of Apple's user base ... either that or they're all millionaires). The reason people who can truly use the full power of a Mac buy them is because of OS X and slightly better (for now) hardware (on laptops only). If OS X licensing allowed it to be run legally on non-mac hardware (ie-> not osx86), no one would pay the inflated prices for a Mac. And now they want to pretend to add security while adding a feature used to tie one in to one's proprietary and quite terrible app ecosystem. How about fixing FileValut2 so it doesn't corrupt my drive every time I run it, leaving it in an unrecoverable state? Yup going on well over a year and still not fixed: https://discussions.apple.com/thread/3197792?start=60&tstart=0 https://discussions.apple.com/thread/3197792?start=60&ts...