Changes between Initial Version and Version 1 of Ticket #51516, comment 149


Ignore:
Timestamp:
Jun 8, 2024, 12:32:34 PM (4 weeks ago)
Author:
RJVB (René Bertin)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #51516, comment 149

    initial v1  
    11I 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?
    22
    3 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?
     3There's also a way to fix that with a proxy server: https://jonathanalland.com/downloads/legacy-mac-proxy.dmg (from https://jonathanalland.com/old-osx-projects.html). 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?
    44
    55And 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`?