The following reply was made to PR pkg/23245; it has been noted by GNATS.

From: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
To: gnats-bugs@netbsd.org
Cc: pkg-manager@netbsd.org
Subject: Re: pkg/23245
Date: Sat, 21 Oct 2006 01:32:47 +0200

 Things got worse.
 
 I have tried both stunnel 4.15 (the current pkgsrc version) and 4.18, the
 latter built with and without pthreads support.
 
 [hauke@pizza] /etc/uucp # stunnel -version
 stunnel 4.18 on sparc--netbsdelf with OpenSSL 0.9.7d 17 Mar 2004
 Threading:FORK SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP
 
 Global options
 debug           = 5
 pid             = /var/run/stunnel/stunnel.pid
 RNDbytes        = 64
 RNDfile         = /dev/urandom
 RNDoverwrite    = yes
 
 Service-level options
 cert            = /etc/pkg/stunnel/stunnel.pem
 ciphers         = ALL:!ADH:+RC4:@STRENGTH
 key             = /etc/pkg/stunnel/stunnel.pem
 session         = 300 seconds
 sslVersion      = SSLv3 for client, all for server
 TIMEOUTbusy     = 300 seconds
 TIMEOUTclose    = 60 seconds
 TIMEOUTconnect  = 10 seconds
 TIMEOUTidle     = 43200 seconds
 verify          = none
 
 With the config file
 
 [hauke@pizza] /etc/uucp # cat stunnel.conf
 # $Id: stunnel.conf,v 1.3 2003/09/08 21:16:52 hauke Exp hauke $
 #
 # stunnel setup for uucp client
 
 debug = mail.debug
 foreground = yes
 client = yes
 pid =
 
 [uucico]
 connect = uucp.xxxxx.yyy:940
 exec = /usr/libexec/uucp/uucico
 execargs = uucico --nodetach --debug abnormal -S uucp
 
 
 all the builds _loop_, i.e. call uucico again and again after it has
 completed the data transfer.
 
 The tunnel is set up correctly, but stunnel mis-manages the local client.
 In addition, when "foreground = no" is set in the above configuration,
 non-terminating stunnel processes end up hanging in the background as
 before.
 
 I can reproduce the problem, and provide a debug log and ktrace if needed.
 
 The pkg update 4.15 -> 4.18 is here:
 http://la.causeuse.org/hauke/NetBSD/pkgsrc/pr23245.shar
 
 	hauke
 
 
 --
 "It's never straight up and down"     (DEVO)