5 ms·

They may have bought it 5 years ago, but it wasn't 5 years old. Also for future reference you can update the certs on older OS X versions to get a few more year

by a2tech 4y ago

They may have bought it 5 years ago, but it wasn't 5 years old. Also for future reference you can update the certs on older OS X versions to get a few more years out of a system for someone thats happy with it: https://apple.stackexchange.com/questions/422332/how-do-i-update-my-root-certificates-on-an-older-version-of-mac-os-e-g-el-capi https://apple.stackexchange.com/questions/422332/how-do-i-up...

belorn 4y ago
An interesting hack. We went with a different hack to accomplish a working solution, but good to know there is alternatives. The idea in the link is that one transfer the System Root certificates from another (more modern) Mac to which the customer should already own. In theory I guess we as a email provider could continuously buy the latest version of mac and use that as the transfer host (hopefully do not transferring any account specific certificates). It must work without any corner cases (not overwriting anything on the customer end), the script need to work in future macos versions, and the assumption is that the first group of certificates is the relevant ones, and that it doesn't break anything on the customer end. For those who has not read the link, this do not update the System Roots keychain since users are not allowed to do that in macos. Instead this adds a trustRoot certificate. A nice trick. One of the comments say that it didn't fix the problem for them but who know what their situation was.
nucleardog 4y ago
Yep. My wife's still running a MBP from 2012 that I think finally got its last update to Big Sur (released 2020) without issue. Looking at the compatibility charts, everything from 2015 on-ward supports Monterey (2021, the latest version). The last laptop that couldn't update past El Capitan was 2009. As far as Macbooks (non-pro), last one stuck on El Capitan is the 2009 model as well. And it's not even that Apple broke anything on the 13 year old laptop, it's just that the rest of the world moved on and they're no longer fixing it.

by a2tech 4y ago

belorn 4y ago

An interesting hack. We went with a different hack to accomplish a working solution, but good to know there is alternatives. The idea in the link is that one transfer the System Root certificates from another (more modern) Mac to which the customer should already own. In theory I guess we as a email provider could continuously buy the latest version of mac and use that as the transfer host (hopefully do not transferring any account specific certificates). It must work without any corner cases (not overwriting anything on the customer end), the script need to work in future macos versions, and the assumption is that the first group of certificates is the relevant ones, and that it doesn't break anything on the customer end. For those who has not read the link, this do not update the System Roots keychain since users are not allowed to do that in macos. Instead this adds a trustRoot certificate. A nice trick. One of the comments say that it didn't fix the problem for them but who know what their situation was.

nucleardog 4y ago

Yep. My wife's still running a MBP from 2012 that I think finally got its last update to Big Sur (released 2020) without issue. Looking at the compatibility charts, everything from 2015 on-ward supports Monterey (2021, the latest version). The last laptop that couldn't update past El Capitan was 2009. As far as Macbooks (non-pro), last one stuck on El Capitan is the 2009 model as well. And it's not even that Apple broke anything on the 13 year old laptop, it's just that the rest of the world moved on and they're no longer fixing it.