This means they natively support modern HTTPS, but ignore Keychain Access. Versions of curl that are built with MacPorts are linked against modern copies of the OpenSSL library. If you set the environment variable, it works perfectly! Without the environment variable set, it won't use the proxy, and won't work.
The built-in Apple version of curl does not support modern HTTPS, but it does use Keychain Access. Curl ignores System Preferences to make it use a proxy, you need to set the HTTPS_PROXY environment variable. However, if some apps read the environment variable, but do not use Keychain Access, they won't find the Squid certificate and will break.
Notefile widget mac update#
The latest update to my proxy package automatically sets the HTTPS_PROXY environment variable so that more apps will use the proxy. So, what determines whether an app connects via our proxy? Well, some use the proxy settings in System Preferences, and others look for an HTTPS_PROXY environment variable.
Notefile widget mac software#
Ironically, this software probably would work fine if it didn't use the proxy at all, because modern versions of OpenSSL natively support modern HTTPS protocols. Software built against non-Apple versions of OpenSSL generally falls into the latter category. The developer might have intentionally decided to ignore user certificates (certificate pinning), but it could also be because the software relies on its own certificate store rather than Keychain Access. There are several possible causes for #2.
0 kommentar(er)
