Comment by brewmarche
3 days ago
The MacBook Air mentioned (2014) will install Mavericks when booted into recovery mode anyway (unless you use Option-Command-R which will give you the newest compatible version which is Big Sur).
I did that a few days ago and I agree, it’s quite snappy! Missing certificates can also be installed manually (e.g. from the curl CA bundle), but even then TLS 1.3 support is lacking in most apps which breaks a lot of stuff without the suggested proxy.
A lot of MacPorts ports also do not build sadly.
The look is so much better than current macOS.
> The MacBook Air mentioned (2014) will install Mavericks when booted into recovery mode anyway (unless you use Option-Command-R which will give you the newest compatible version which is Big Sur).
Certain 2014 Macbook Airs, including my own, will install Yosemite instead in recovery mode for some reason, even though obviously I'm using Mavericks and it runs fine.
I think it depends on what was the current version when your model came out. Should have said mid-2014 like OP, sorry
> Should have said mid-2014 like OP, sorry
I don't want to belabor the point, but just to be clear—I am referring to a mid-2014 MBA, anything newer and Mavericks wouldn't work! (There is no "late 2014" MBA as far as I'm aware.) Mine offers to install Yosemite in recovery mode.
It may indeed be based on when that specific computer came off of the assembly line or something, I have no idea, but for that exact model of computer you can get different results in recovery mode!
10 replies →
Regarding SSL: just make sure you are using macOS 10.9.3, earlier versions (all of them, and I mean, all since the 80s) never had a working SSL implementation.
For more, read about the GOTO FAIL bug: https://nvd.nist.gov/vuln/detail/cve-2014-1266
I often bring this one up when I see missing braces in PRs.
It's pretty hard to install anything below 10.9.5, Apple updated all the installers to go straight to that version.
But if you're using Aqua Proxy, you're not really using the system's SSL implementation anyway, you're using Go 1.19's SSL.