Re: SSL and old macOS versions
Re: SSL and old macOS versions
- Subject: Re: SSL and old macOS versions
- From: Daniel Jalkut <email@hidden>
- Date: Wed, 18 Jul 2018 10:32:08 -0400
Until recently I was building my main product (MarsEdit) with the 10.6 SDK (!).
I still build a couple other apps this way.
Speaking only for myself, the rationale for sticking with such an old SDK was
to minimize the risk of unexpected behavior while maintaining an app with
support for older operating systems. Yes, it may be sort of absurd to continue
supporting users running on 10.6, but it was a compatibility line I staked out
a long time ago and planned to stick with until “a major version upgrade.”
Generally speaking it has historically been much safer to stick with the same
SDK while creating bug fix updates or even minor functionality improvements.
The risk of a “compiled on or after” behavior change made it daunting to
consider using a newer SDK. This particular situation with TLS is one of the
rare instances where an app is functionally penalized for being compiled on an
old SDK. It’s a real shame because people will experience the failure as we
move forward on old apps that are not maintained, but which still happen to
run. They’ll just stop working as the world moves to HTTPS everywhere and
TLS1.2+ at that.
Daniel
> On Jul 18, 2018, at 3:27 AM, Quinn The Eskimo! <email@hidden> wrote:
>
> Why are you building with the 10.8 SDK? I understand that it can take time
> to move forward to new tools, but 10.9 is five years old now. The longer you
> stay on the old SDKs, the further off the beaten path you end up, and this is
> just one example of the various land mines waiting for you out there.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden