hi Mike, root@binz:~# stunnel -version Initializing inetd mode configuration stunnel 5.57 on aarch64-mbient-linux-gnu platform Compiled/running with OpenSSL 1.1.1q 5 Jul 2022 Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,OCSP,PSK,SNI Auth:LIBWRAP
Global options: RNDbytes = 1024 RNDoverwrite = yes Service-level options: ciphers = HIGH:!aNULL:!SSLv2:!DH:!kDHEPSK ciphersuites = TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256 (with TLSv1.3) curves = X25519:P-256:X448:P-521:P-384 debug = daemon.notice logId = sequential options = NO_SSLv2 options = NO_SSLv3 securityLevel = 2 sessionCacheSize = 1000 sessionCacheTimeout = 300 seconds stack = 65536 bytes TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none GNU C Library (GNU libc) stable release version 2.32. Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 9.3.0. libc ABIs: UNIQUE ABSOLUTE For bug reporting instructions, please see: <https://www.gnu.org/software/libc/bugs.html>. "mbient-linux" is a customized linux which is not public. It uses also another non-public client certificate engine (qautheng). Could it be that the qautheng somehow interferes with stunnel and causes the crash? Following are the sample logs from stunnel regarding qautheng: 2023.04.25 11:03:05 LOG6[ui]: Client certificate engine (qautheng) not supported 2023.04.25 11:03:05 LOG6[ui]: Loading certificate from engine ID: /mnt/cathi/certs/client_cert.pem 2023.04.25 11:03:05 LOG3[ui]: ENGINE_ctrl_cmd: Peer suddenly disconnected BR, Phan Anh _______________________________________________ stunnel-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
