On 11/25/20 12:34 PM, Stuart Henderson wrote: > On 2020/11/25 12:03, Aisha Tammy wrote: >> Hi, >> It has come to my attention that upstream does not support >> libressl and only wants to support openssl >> https://github.com/uNetworking/uWebSockets/issues/994 >> >> I am unsure on how to fix this port. >> There is no problem right now as the only consumer www/purritobin >> does not use the SSL functionality in 0.2.4 (the current version in tree). >> >> The new updated version www/purritobin-0.3.1 (not yet sent the diff) >> does use SSL functionality optionally during runtime, which will be broken >> if net/usockets doesn't get fixed. >> >> Can anyone help with fixing this linking? >> >> The updated version of usockets and purritobin do work correctly when >> linked with OpenSSL when used on linux (tested on gentoo). >> >> Thanks, >> Aisha > "LibreSSL seems to be just like most forks are; a joke." lovely. I know right :( > what is the actual breakage when trying to use it with libressl? >
When doing a paste, with curl, using an SSL connection, the error is: * Trying 73.215.141.174:42069... * Connected to epsilonknot.xyz (73.215.141.174) port 42069 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS alert, handshake failure (552): * error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure * Closing connection 0 curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure Thanks a bunch, Aisha
