Re: Version 5.54 'make check' fails test 042_inetd
Małgorzata Olszówka <[email protected]> Tue, 21 May 2019 13:42:33 +0200
| Newsgroups | gmane.network.stunnel.user |
|---|---|
| Message-ID | <[email protected]> |
>>>> On 20 May 2019, at 3:29 pm, James Brown <[email protected] <mailto:[email protected]>> wrote: >>>> >>>> Having problems installing version 5.54 on macOS X with this configure command: >> [snip] >>>> test 042_inetd failed >>>> error logs logs/042_inetd.log >> >> So what does this file contain? > > *** inetd mode *** > 2019.05.20 15:22:07 LOG6[0]: TLSv1.3 ciphersuite: TLS_CHACHA20_POLY1305_SHA256 (256-bit encryption) > 2019.05.20 15:22:07 LOG7[0]: Compression: null, expansion: null > 2019.05.20 15:22:07 LOG3[0]: transfer() loop executes not transferring any data > 2019.05.20 15:22:07 LOG3[0]: please report the problem to [email protected] > 2019.05.20 15:22:07 LOG3[0]: stunnel 5.54 on x86_64-apple-darwin18.5.0 platform > 2019.05.20 15:22:07 LOG3[0]: Compiled/running with OpenSSL 1.1.1b 26 Feb 2019 > 2019.05.20 15:22:07 LOG3[0]: Threading:PTHREAD Sockets:POLL,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI > 2019.05.20 15:22:07 LOG7[0]: errno: (*__error()) > 2019.05.20 15:22:07 LOG3[0]: protocol=TLSv1.3, SSL_pending=0, SSL_has_pending=0 > 2019.05.20 15:22:07 LOG3[0]: sock_open_rd=Y, sock_open_wr=Y > 2019.05.20 15:22:07 LOG3[0]: SSL_RECEIVED_SHUTDOWN=n, SSL_SENT_SHUTDOWN=n > 2019.05.20 15:22:07 LOG3[0]: sock_can_rd=n, sock_can_wr=n > 2019.05.20 15:22:07 LOG3[0]: ssl_can_rd=n, ssl_can_wr=n > 2019.05.20 15:22:07 LOG3[0]: read_wants_read=Y, read_wants_write=n > 2019.05.20 15:22:07 LOG3[0]: write_wants_read=n, write_wants_write=n > 2019.05.20 15:22:07 LOG3[0]: shutdown_wants_read=n, shutdown_wants_write=n > 2019.05.20 15:22:07 LOG3[0]: socket input buffer: 0 byte(s), TLS input buffer: 0 byte(s) > 2019.05.20 15:22:07 LOG5[0]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket Hello, I tried to replicate this “transfer() loop” bug in the inetd mode, but I couldn't. It would be useful to have the remote access to a macOS X test machine for debugging stunnel. >> Also, why did it skip the IPv6 test? Please find the attached patch for the 020_IPv6 test. Best regards, Małgorzata Olszówka _______________________________________________ stunnel-users mailing list [email protected] https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
020_IPv6.patch
(text/plain, 520 B)
diff --git a/tests/recipes/020_IPv6 b/tests/recipes/020_IPv6
index d5c98de..6994b3a 100644
--- a/tests/recipes/020_IPv6
+++ b/tests/recipes/020_IPv6
@@ -24,7 +24,7 @@ EOT
}
# nc does not support IPv6
-if grep -q "IPv6" "results.log" && [ -n "$(command -v ncat)" ] && \
+if grep -q "IPv6" "results.log" && \
(([ -n "$(command -v ip)" ] && PATH="${PATH}:/sbin:/usr/sbin" ip address | grep -q "inet6") || \
([ -n "$(command -v ifconfig)" ] && PATH="${PATH}:/sbin:/usr/sbin" ifconfig | grep -q "inet6"))
then