Vcpkg: Upgrading OpenSSL from 1.0.2h to 1.1.0
We are considering updating OpenSSL to 1.1.0.
However, there are some breaking changes in OpenSSL 1.1.0, as outlined here:
https://wiki.openssl.org/index.php/1.1_API_Changes
If you have tried upgrading to OpenSSL, please post your experience here.
Were you able/unable to update? If you did manage to upgrade, what was the extent of changes that were required?
alexkaratarakis
All 5 comments
I tried to compile grpc and folly with OpenSSL 1.1.0 (my vcpkg branch) and... grpc doesn't compile
https://github.com/grpc/grpc/issues/8801
KindDragon
on 12 May 2017
CppRestSDK 2.9.0 too, but you probably already know about it :) https://github.com/Microsoft/cpprestsdk/issues/56
KindDragon
on 12 May 2017
- websocketpp https://github.com/zaphoyd/websocketpp/issues/599
- freerdp
Could NOT find OpenSSL - libpq
fe-secure-openssl.c(1582): error C2037: left of 'ptr' specifies undefined struct/union 'bio_st' - libwebsockets (fixed in v2.2.0)
KindDragon
on 12 May 2017
May I suggest that openssl1.1 be a different port from 1.0.2. Not every 3rdparty is compatible yet. And if you look at brew on Mac you have both 1.0.2 and 1.1.0.
Doing so would allow other libs to be upgraded carefully and willingly choose to switch to the new openssl.
thierryba
on 20 Dec 2017
Fixed!
strega-nil
on 22 May 2020
Related issues
invy
路
3Comments
PhilLab
路
3Comments
madkoala
路
3Comments
cjvaijo
路
3Comments
cskrisz
路
3Comments
Most helpful comment
May I suggest that openssl1.1 be a different port from 1.0.2. Not every 3rdparty is compatible yet. And if you look at brew on Mac you have both 1.0.2 and 1.1.0.
Doing so would allow other libs to be upgraded carefully and willingly choose to switch to the new openssl.