[MacPorts] #51516: MacPorts should use a bundled copy of a newer libcurl and SSL library rather than the OS X version

[MacPorts]

#51516: MacPorts should use a bundled copy of a newer libcurl and SSL library
rather than the OS X version
--------------------------+--------------------------------
  Reporter:  ryandesign   |      Owner:  macports-tickets@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:  MacPorts Future
 Component:  base         |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------------------

Comment (by RJVB):

 I suppose the underlying issue we're dealing with here is also the reason
 why many native apps on legacy OS versions will no longer connect to
 websites and services?

 There's also a way to fix that with a proxy server:
 https://jonathanalland.com/downloads/legacy-mac-proxy.dmg . That
 particular solution works at the system-wide level and would interfere
 with the functioning of MacPorts applications using up-to-date secure-
 connection libraries but it might be possible to use a dedicated proxy
 used only by MacPorts itself? Mostly thinking aloud: this might be usable
 as a bootstrapping solution?

 And out of curiosity, I think we cannot build a sufficiently feature-full
 version of Apple's SecureTransport fw ourselves, but could we redistribute
 a sufficiently current version, (to be) relinked with
 `libMacportsLegacySupport.dylib`?

-- 
Ticket URL: <https://trac.macports.org/ticket/51516#comment:149>
MacPorts <https://www.macports.org/>
Ports system for macOS