Hi, On Sun, Nov 7, 2021 at 9:14 AM Lev Stipakov <lstipa...@gmail.com> wrote:
> Hi, > > We agreed during the hackathon that we are going to ship a 2.6 Windows > client with OpenSSL 3.0. Apart from merging relevant patches, there > are few (small) blocks: > > - vcpkg hasn't yet added OpenSSL 3.0 to official repo, but there is a > PR https://github.com/microsoft/vcpkg/pull/20428 This shouldn't be a > problem for us, since we could just have this port in openvpn repo, > like we do with pkcs11-helper. > > - The latest release of pkcs11-helper doesn't build with openssl3, > but things are progressing - > https://github.com/OpenSC/pkcs11-helper/issues/42. We would also have > to make sure that our vcpkg port for pkcs11-helper builds with > openssl3. > > Once OpenSSL 3.0 support is somewhat settled, we could look into > configuration file loading. I haven't checked vcpkg scripts, but in > the best case scenario we won't have to do anything and just rely on > readonly values you've mentioned. > While this sounds good for 2.6, can we fix this in 2.5 as well? In mingw cross builds our mistake was using "--openssl-dir /etc/ssl" with OpenSSL "Configure". Not sure what we do now for MSVC builds. The default locations are pretty decent as per NOTES.WIN in OpenSSL 1.1.1 tree. Selva
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
