4 ms·
Apple makes claims that they're "secure" but is that really true? Is their fundamental design really different from anyone else's? No word in this article abou
by fortran77 6y ago
Apple makes claims that they're "secure" but is that really true? Is their fundamental design really different from anyone else's?
No word in this article about the infection vector.
- Sebb767 6y agoAs long as you can execute anything you want on your Mac, you can execute malicious code. Without the infection vector (which is probably not known yet), it is impossible to say whether it is user error or a security vulnerability.
- 13415 6y agoMost of Apple's security is theater and instead used to bind developers to their infrastructure and make it harder to use software outside their tightly controlled app stores. You used to be able to get the password of encrypted home directories from the page file with a simple grep command for many years without any attempts by Apple to fix it, that alone should tell you how secure Macs are.
- zepto 6y ago> You used to be able to get the password of encrypted home directories from the page file with a simple grep command You already have to be root to do this. This tells you nothing about Mac security.
- smoldesu 6y agoYou're thinking of the shadow file, which I don't believe OP is referring to.
- 13415 6y agoRight, no need to encrypt anything, just don't set any read permissions. Problem solved!
- zepto 6y agoNobody is saying this other than you.
- 13415 6y agoYou insinuated it, though, by claiming that it wasn't a security problem as it required root. If you think failure to encrypt (leaking the passphrase) is not a problem because the exploit requires root, then you understand absolutely nothing about security. By the way, the reason why I mentioned this particular example is that it almost certainly proves malicious intent. It is not credible that a team of security engineers at Apple developed file vault without thinking at all about locking memory for the passphrase and then continued not to think about it for years. They basically only fixed it (and first even in the wrong way) after it became folklore on every second Mac fan site. (Lost your file vault password? Don't despair: Just copy & paste this in the terminal.) There is 0 reason to trust Apple on security.
- zepto 6y ago> You insinuated it, though by claiming that it wasn't a security problem as it required root I did make any such claim. You are seeing things where they aren’t. Encryption at rest is very important. However, it’s worth putting different risks into perspective. What you can do if you have root, simply is a different category of risk than what you can do without. Pointing that out insinuates nothing. > By the way, the reason why I mentioned this particular example is that it almost certainly proves malicious intent. Obviously not, because otherwise they wouldn’t have fixed it. That you can find a security problem from the past that has now been fixed, is the precise opposite of evidence that a company doesn’t care about security.
- 13415 6y agoOkay, okay. You insinuated nothing. I stand corrected. Just a little side note: You didn't need root for the exploit, it was also trivial to boot from a CD or another OS to get the passphrase from the page file. Basically it meant that file vault was useless for many years. Anyway, you're kind of missing my point. There are plenty of other examples of Apple not addressing security issues in time. Be that as it may, if you feel secure about your Mac, who am I to argue with that...
- netsec_burn 6y agoI'm a different security guy from the one above. I have a root exploit in macOS that Apple has refused to discuss with me for half a year. I told them it affected Big Sur (even since the betas) and they were unfazed. I have reached out to everyone I know at Apple to schedule a demo or even a phone call and they've been met with silence from their product security team. How is that for some perspective on Apple's security?
- edoceo 6y agoPublish your research
- netsec_burn 6y agoCan't do it if there is no way to keep my lights on and food on my table.
- zepto 6y agoApple routinely interacts with security researchers, and pays bug bounties. It sounds like you haven’t told them any technical details about the exploit, at all. If this is the case, then they have no way to tell you apart from a timewaster or scammer. If all you have done is tell them you have an exploit and tried to schedule a meeting, it’s unlikely they’ll take you seriously.
- netsec_burn 6y agoIn fact, I have given them technical details as to what the capabilities are and the affected macOS versions. I refuse to submit all of my research without them telling me roughly what the bounty ranges are for the vulnerabilities in the same class/equivalent impact. I've done many bounty programs in the past. Companies will always choose to pay nothing or close to nothing when it is favorable to them. Apple refuses to share what the bounty ranges are given technical information about it, and asked me to submit the entirety of my research without having any idea of what the compensation may be. So they made it impossible for me and perhaps many others to help improve the security of their OS ethically. For every 1 company that pays you in bug bounties, 10 don't. If you're a security researcher, you can't afford the possibility of getting nothing for months of research.
- ric2b 6y agoIsn't the page file on disk? Can't you just force shutdown and then boot an alternative OS that ignores the file permissions and read it?
- zepto 6y agoWho knows - the problem was fixed long ago.
- brokenmachine 6y agoThen why did you write in italics to emphasize that you already have to be root, if you were so unsure?
- lofi_lory 6y agoOn many systems you were able to get root access by simply leaving the password empty. While relevant getting root is still different from getting the encryption keys.
- zepto 6y agoWhat systems, and when?
- lofi_lory 6y agohttps://www.theguardian.com/technology/2017/nov/29/macos-high-sierra-bug-apple-mac-unlock-blank-password-security-flaw https://www.theguardian.com/technology/2017/nov/29/macos-hig...
- zepto 6y agoDoesn’t seem like it was ‘many systems’. It’s a very severe bug, for sure, but it wasn’t long-standing and looks like it only affected a small number of versions before it was fixed.
- MertsA 6y agoAnd you would also already need root for encrypting the home directory to even matter in the first place. Leaving the password on disk right next to the encrypted content is on par with leaving the keys in a fancy locked safe. It completely nullifies the whole point of the added security to begin with. I'm an amateur when it comes to application security yet even I know that you should mlock() your secret data addresses and never pass secret data through command line arguments. Both trivial mistakes that Apple has made with FileVault. They even shipped code that would set the password hint to the actual password. How are their security standards so lax to have missed all of that in their encryption software alone?
- KarlKemp 6y ago“You used to be able...” “... with no attempt to fix” is somewhat contradictory. And, of course, the whole comment is inane. The MacOS security model these days very effectively prevents apps from accessing data outside their assigned sandbox. Meanwhile, distributing outside the App Store still requires only a (strict) subset of the steps required for distribution in the App Store.
- 13415 6y agoIt took them about three major OS updates to fix this problem.
- smoldesu 6y agoSocial engineering is always the most effective infection vector, and the more secure you think your device is, the more vulnerable you are. This is particularly the case on the higher end of the spectrum, where I've seen iPhone users click on obvious phishing scams with the justification of "oh, I'm on iOS, they can't get my data". I've seen a lot of the same mentality exist in the desktop Mac space, where most users perform two types of installs: relatively safe ones through the App Store, or venturing out into the wild west of the internet and bringing home a random binary that hopefully does what it says. Honestly, I'm tired of HN users downvoting anything critical of Apple. It only further confirms how much of an echo chamber this place can be.
- 2cb 6y agoThis attitude from users is a very real problem, but I'd argue it's platform agnostic. For instance there were headlines around the internet not too long ago stating Android is more secure than iOS based on claims made by Zerodium. Any Android user who read that may well have the same attitude you've described from iOS users. And it's potentially far more dangerous on Android because it allows you to sideload apps. You can even extend it to Windows. Your average user will buy a laptop preinstalled with McAfee [1] and think "no need to worry about viruses now because I've got an antivirus." Don't get me wrong I agree it's perfectly reasonable to be critical of Apple when it's warranted, but we don't yet know if it is in this case. It's entirely possible (and fairly likely) this malware was delivered as a trojan using pop ups the user had to interact with. If that's the case you can't blame Apple for user error, especially when trojans exist for every single OS that allow the user to install software from the internet. > most users perform two types of installs: relatively safe ones through the App Store, or venturing out into the wild west of the internet and bringing home a random binary that hopefully does what it says. This seems to imply any software installed from the App Store is safe while anything from outside the App Store is dangerous. Isn't the implication that App Store downloads must automatically be safe falling into the same trap you're criticising here? Quotes from the article: > Developer ID Saotia Seay (5834W6MYX3) – v1 bystander binary signature revoked by Apple > Developer ID Julie Willey (MSZ3ZH74RK) – v2 bystander binary signature revoked by Apple So both of these malware packages were signed by Apple. Seems like relying on Apple's review processes to determine how safe a particular binary is only provides the same false sense of security you're describing. [1] https://www.youtube.com/watch?v=bKgf5PaBzyg https://www.youtube.com/watch?v=bKgf5PaBzyg (sorry, couldn't resist)