Hello,
Does anyone (Jeremy??) know if the Security.framework sources provided on
opensource.apple.com (latest version
https://opensource.apple.com/source/Security/Security-57740.31.2/) are
feature-complete and has anyone tried to build this framework with the goal of
providing recent security
On Saturday January 21 2017 15:21:19 Marcus Calhoun-Lopez wrote:
> The openssl dependency is one reason that qt5-qtcreator does not build on the
> buildbots.
I never understood why one could distribute binaries of libraries that link to
openssl but not of applications that use those libraries..
On Saturday January 21 2017 23:57:50 René J.V. Bertin wrote:
>Qt also has a dynamic openssl mode, in which it loads libssl at runtime. I
>reckon that it should be possible to ensure it uses the one from MacPorts.
>I'll try to look into that one of these days.
That looks like it won't be very ha
On Saturday January 21 2017 15:21:19 Marcus Calhoun-Lopez wrote:
> My current plan is to use Secure Transport instead and create an openssl
> variant.
Until we know more about the pros and cons it may be preferable to make a
securetransport variant, or else make the openssl variant the default
The openssl dependency is one reason that qt5-qtcreator does not build on the
buildbots.
My current plan is to use Secure Transport instead and create an openssl
variant.
Unfortunately, my knowledge of Transport Layer Security is limited, so I do not
know if there are other considerations.
-Mar
Hi,
Somehow I never noticed this before:
- Qt4 and Qt5 are configured with -openssl-linked to ensure the MacPorts
version is used
- this disables SecureTransport support which Qt normally uses on Mac
I guess that using OpenSSL means we get whatever more recent SSL is in MacPorts
than the host'
