Package: stunnel4 Version: 3:4.29-1 Severity: normal Dear maintainers,
After some time [1] of operation stunnel suddenly complains: 2012.06.08 08:42:50 LOG5[1656:3074509680]: tlstunnel accepted connection from xxx.xxx.xxx.xxx:32933 2012.06.08 08:42:50 LOG3[1656:3074509680]: SSL_accept: Peer suddenly disconnected 2012.06.08 08:42:50 LOG5[1656:3074509680]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2012.06.08 08:42:50 LOG5[1656:3074509680]: tlstunnel accepted connection from xxx.xxx.xxx.xxx:22938 2012.06.08 08:42:51 LOG4[1656:3074509680]: Found CRL is expired - revoking all certificates until you get updated CRL stunnel is configured to work with CRLs: CRLpath = /etc/ssl/crls This directory contains the CRL and the appropriate hashes. The CRL itself is cron based generated. It seems that stunnel doesn't reread the CRL. After restarting stunnel everything works well again. [1]: a time greater than the CRL valid time -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages stunnel4 depends on: ii adduser 3.112+nmu2 add and remove users and groups ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libssl0.9.8 0.9.8o-4squeeze13 SSL shared libraries ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii netbase 4.45 Basic TCP/IP networking system ii openssl 0.9.8o-4squeeze13 Secure Socket Layer (SSL) binary a ii perl-modules 5.10.1-17squeeze3 Core Perl modules stunnel4 recommends no packages. Versions of packages stunnel4 suggests: pn logcheck-database <none> (no description available) -- Configuration Files: /etc/default/stunnel4 changed [not included] /etc/logrotate.d/stunnel4 changed [not included] /etc/stunnel/stunnel.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
