Changes between Initial Version and Version 1 of Ticket #58848, comment 8


Ignore:
Timestamp:
Aug 17, 2019, 5:45:35 PM (5 years ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #58848, comment 8

    initial v1  
    88The issue with SSL being outdated in MacPorts goes back several years now. See <https://trac.macports.org/ticket/51516>. By default, MacPorts is built against the system's installed SSL infrastructure, which is very outdated on older systems. There has been talk, as per that ticket, of bundling openssl with MacPorts, but there is resistance about being in the security game, naturally.
    99
    10 What I do is install a separate current version of `openssl` and build MacPorts against that. By doing that, your MacPorts SSL is right up to date.
     10What I do is install a separate current version of `openssl` and `curl` using a separate install of MacPorts in `/opt/bootstrap` and build my working MacPorts against that. By doing that, your MacPorts SSL is right up to date.
    1111
    1212To do that, I build MacPorts from source. It's easy enough, and takes me only a few minutes, but admittedly it is a bit of a process to follow. Nonetheless, I do it on every machine I have running 10.9 and less. I never see any SSL errors using MacPorts this way.