We’re using libssh2 with OpenSSL 1.1.0f without issue. Are you sure you’ve built 1.1.x correctly?
Will
> On Oct 27, 2017, at 4:50 AM, Jerome Zimmermann <Jerome.Zimmermann_at_ipetronik.com> wrote:
>
> Hi list,
>
> just for the sake of completeness.
>
> Using OpenSSL 1.0.2l (instead of OpenSSL 1.1.0c) with the libssh2 version 1.8.0 worked on our machine.
>
> Best regards.
>
>
> Impressum/Imprint: https://www.ipetronik.com/impressum <https://www.ipetronik.com/impressum>
>
>
> >>> "Jerome Zimmermann" <Jerome.Zimmermann_at_ipetronik.com> 23.10.2017 15:18 >>>
> Hello everyone,
>
> >> First thing the list is going to tell you is you need be using the latest version. The current version is 1.8.0 and can be found here:
>
> Of course we used the current libssh2 version 1.8.0.
>
> Besides, I think I forgot to say that we are working on a RTOS platform (based on Win32).
>
> Could it be possible, that if the OpenSSL is build with the wrong configuration parameters that this could lead to failures (as in my case for the key exchange) ?
>
> Here my configuration:
>
> perl Configure VC-WIN32 --prefix=xxx --openssldir=xxx no-shared no-capieng no-sock no-async no-unit-test no-ui
>
> Best regards
>
> Impressum/Imprint: https://www.ipetronik.com/impressum <https://www.ipetronik.com/impressum>
>
>
> >>> Will Cosgrove <will_at_panic.com> 19.10.2017 19:03 >>>
> Hi Jerome,
> First thing the list is going to tell you is you need be using the latest version. The current version is 1.8.0 and can be found here:
>
> https://www.libssh2.org <https://www.libssh2.org/>
>
> Or you can use a daily snapshot which is very stable from GitHub.
>
> Cheers,
> Will
> _______________________________________________
> libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
_______________________________________________
libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2017-10-27