OpenSSL v1.1.0 compatibility issues about bluesslservice HOT 11 CLOSED

As of now, there's no way to support both the 1.0.x and 1.1.x versions of OpenSSL in the same module using the same interface. I'm investigating creating a branch of this framework that will support OpenSSL v1.1.x that will be separate from the current version. The current version, 1.0, of BlueSSLService will be used for OpenSSL 1.0.x while a new 2.0 version of BlueSSLService will be used to support OpenSSL 1.1.x. No estimate at this time as to when this will available. I hope to be able to start on it soon. In the meantime, I've marked this issue as an enhancement.

Another solution would be to create a proxy, a small C library that exposes the API needed for BlueSSL and have it configured to use the available openssl version installed on the local machine (and maybe even common crypto on macOS instead of openssl).

from bluesslservice.

i quote this issue, i have similar problems in Ubuntu 16.04 with OpenSSL and Kitura.

from bluesslservice.

As of now, there's no way to support both the 1.0.x and 1.1.x versions of OpenSSL in the same module using the same interface. I'm investigating creating a branch of this framework that will support OpenSSL v1.1.x that will be separate from the current version. The current version, 1.0, of BlueSSLService will be used for OpenSSL 1.0.x while a new 2.0 version of BlueSSLService will be used to support OpenSSL 1.1.x. No estimate at this time as to when this will available. I hope to be able to start on it soon. In the meantime, I've marked this issue as an enhancement.

from bluesslservice.

I have same errors on Linux, OpenSSL 1.1.0f

from bluesslservice.

I solved it: sudo apt-get install libssl1.0-dev

from bluesslservice.

Yeh, but that's a pretty weak solution. We should leave this open, for a real fix for building against OpenSSL v1.1.x. :-)

from bluesslservice.

👍 I agree. Hopefully I have a chance to look at it soon.

from bluesslservice.

Curious, is this a limitation in how Swift handles external modules like this? I mean, I've worked on several projects where supporting different versions of a dependency like this is easily done. The solution at hand right now (downgrading OpenSSL) is really problematic, since so much depends on OpenSSL these days :).

Having a 2.0 version of BlueSSLService seems fine though.

from bluesslservice.

@zwoop @LorenzoPirro @Art3mS1d #61 adds support for openssl 1.1.x

from bluesslservice.

Resolved in #61

from bluesslservice.

Addressed in BlueSSLService 1.0.24 and newer.

from bluesslservice.