3 ms·
Can you please provide more detail as to what attack vectors you forsee being a problem? I want to be conscientious of security concerns, but I legitimately can
by Wowfunhappy 7y ago
Can you please provide more detail as to what attack vectors you forsee being a problem? I want to be conscientious of security concerns, but I legitimately can't think of a scenario that would make what I'm doing genuinely unsafe.
This machine:
• Is connected to the internet.
• Is behind a router. All incoming ports are closed, except one for ssh. (An updated SSH binary has been installed via Macports.)
• Runs Little Snitch, so I can monitor what data gets sent out of my machine.
• Is running an up-to-date copy of Firefox.
• Has all important data backed up to cold storage regularly.
I consider any application I install locally to be trusted code, so the only source of untrusted code is the Javascript that I run inside of Firefox, which is up to date.
Some attack scenarios I can imagine:
1. There's a Firefox zero day. My vulnerable OS does not offer the extra layers of protection that a newer one might.
2. Someone exploits Spectre/Meltdown/etc via Javascript. My attacker is incredibly lucky, and the tiny portion of memory they retrieve just so happens to be the bit that contains something vital, like my master password.
3. Someone emails me a malicious image, which isn't caught by Gmail (personal accounts) or Microsoft Exchange (work account), and infects my machine when it's rendered by Apple Mail.
4. A person I know/trust is tricked into sending me an infected document, likely a PDF or MS Office file. Even though I don't have Acrobat or Microsoft Office installed, the vulnerability is compatible with Preview or iWork '09.
I'm not a particularly important person, so I think I'm more likely to die in a plane crash than get hit by 1 or 2. The latter two scenarios are maybe a bit more concerning, but not to the point where I consider them real threats. Particularly given that I also have cold data backups and Little Snitch.
- marcoperaza 7y agoFor one, a large number of native applications use the OS's webview widget, so you remain exposed to the outdated Safari engine even if you don't use Safari. You're also going to have to use outdated versions of various software packages, as you describe in your post. That's another security hole. As you note, bugs are often found in video and image decoders. The one in your OS isn't being updated anymore. And consider that not every fix for a segfault or other bug gets labeled as a "security patch", but that doesn't mean that they don't present security issues. I imagine most engineers fix the buggy code and move on, and never really consider if there was a security hole there. In other words, it's common for vulnerabilities to be discovered long after they were fixed. And there are probably many more that remain undiscovered despite being present in old versions.
- Wowfunhappy 7y agoYeah, the chances I'd run into those things just seems incredibly low. Separately: > And consider that not every fix for a segfault or other bug gets labeled as a "security patch", but that doesn't mean that they don't present security issues. But this would imply that the newer version is inherently less buggy, wouldn't it? At least in terms of user-visible bugs, Mavericks is actually a lot more solid in my experience. That's a part of why I want to do this. Apple keeps adding new features and breaking old ones in the process. There is no question Mavericks has more known vulnerabilities, and that's significant. But as an academic question, I'm not at all convinced that Mavericks has more unknown vulnerabilities. If nothing else, it almost certainly has a smaller attack surface.