[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 jerryyhom):

 I have read through most comments.  I guess the issue is whether someone
 is willing to put in the time/effort to link macports base with a modern
 curl, and maybe no one is willing.  I have two comments.

 1.  Ken (or others), you have manually compiled with a modern curl for
 several years.  On old systems, what happens with expired certificates?
 Do you update them?

 2.  As for linking with a modern curl, I think Ryan's comment 57 makes
 sense, which also follows Apple's recommendation about OpenSSL[1].  I
 would like to nudge this issue forward, but I am not familiar with
 macports base.  Can someone comment how much development effort is
 required?

 [1]:
 <https://developer.apple.com/library/archive/documentation/Security/Conceptual/cryptoservices/SecureNetworkCommunicationAPIs/SecureNetworkCommunicationAPIs.html#//apple_ref/doc/uid/TP40011172-CH13-SW1>

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