From jjr@www.larush.com  Sat May 14 03:03:55 2005
Return-Path: <jjr@www.larush.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7289716A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 14 May 2005 03:03:55 +0000 (GMT)
Received: from www.larush.com (www.larush.com [69.41.164.28])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 09AAC43D82
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 14 May 2005 03:03:53 +0000 (GMT)
	(envelope-from jjr@www.larush.com)
Received: from www.larush.com (localhost [127.0.0.1])
	by www.larush.com (8.13.3/8.13.1) with ESMTP id j4E33r6R045850
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 13 May 2005 22:03:53 -0500 (CDT)
	(envelope-from jjr@www.larush.com)
Received: (from jjr@localhost)
	by www.larush.com (8.13.3/8.13.1/Submit) id j4E33qeJ045849;
	Fri, 13 May 2005 22:03:52 -0500 (CDT)
	(envelope-from jjr)
Message-Id: <200505140303.j4E33qeJ045849@www.larush.com>
Date: Fri, 13 May 2005 22:03:52 -0500 (CDT)
From: "John J. Rushford Jr." <jjr@www.larush.com>
Reply-To: "John J. Rushford Jr." <jjr@www.larush.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: stunnel 4.10 port is broken
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         81001
>Category:       ports
>Synopsis:       stunnel 4.10 port is broken
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    roam
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 14 03:10:01 GMT 2005
>Closed-Date:    Tue Jun 14 10:41:27 GMT 2005
>Last-Modified:  Tue Jun 14 10:41:27 GMT 2005
>Originator:     John J. Rushford Jr.
>Release:        FreeBSD 5.4-STABLE i386
>Organization:
>Environment:
System: FreeBSD www.larush.com 5.4-STABLE FreeBSD 5.4-STABLE #5: Sun Apr 17 16:32:09 CDT 2005 jjr@www.larush.com:/usr/obj/usr/src/sys/GENERIC i386

>Description:
	I run stunnel as a daemon for pop3s and smtps.  I ran portupgrade
	to upgrade stunnel from 4.7 to the latest port of 4.10.  After the
	upgrade using the same stunnel.conf from the 4.7 release I started
	stunnel and notice that the daemon exits after handling one connection
	of either pop3s or smtps.  It behaves as if it is configured to
	be run from inetd by default.
>How-To-Repeat:
	Install the port stunnel 4.10 and configure it to run as a daemon
	servicing pop3s and smtps, ports 995, and 465 respectively.  Use 
	a mail client configured to use pop3s on port 995 and smtps on port 
	465.  You will notice that after either a pop3s session or smtps 
	session, the daemon exits.
>Fix:
unknown


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports-bugs->roam 
Responsible-Changed-By: thierry 
Responsible-Changed-When: Sat May 14 08:12:18 GMT 2005 
Responsible-Changed-Why:  

Assign to maintainer. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=81001 

From: Michael Ablassmeier <abi@grinser.de>
To: bug-followup@FreeBSD.org, jjr@www.larush.com
Cc:  
Subject: Re: ports/81001: stunnel 4.10 port is broken
Date: Wed, 8 Jun 2005 20:02:57 +0200

 hi,
 
 broken on 5.3 too. Upstream is aware of this problem and seems to
 need a freebsd account to debug the issue, though. See this thread on
 stunnel-users for more information:
 
  http://stunnel.mirt.net/pipermail/stunnel-users/2005-May/000490.html
 
 (4.10 is known to be a experimental release (see release announcement),
 why did it enter the ports tree at all? *rant*)
 
 bye,
     - michael

From: "John J. Rushford" <jjr@alisa.org>
To: abi@grinser.de
Cc: "John J. Rushford" <jjr@alisa.org>, bug-followup@FreeBSD.org,
        jjr@www.larush.com
Subject: Re: ports/81001: stunnel 4.10 port is broken
Date: Wed, 8 Jun 2005 18:33:47 -0600

 Michael,
 
 Thanks for the info.  Good question, why did the experimental 4.10  
 get into the ports tree?
 
 thanks
 John
 
 On Jun 8, 2005, at 12:02 PM, Michael Ablassmeier wrote:
 
 > hi,
 >
 > broken on 5.3 too. Upstream is aware of this problem and seems to
 > need a freebsd account to debug the issue, though. See this thread on
 > stunnel-users for more information:
 >
 >  http://stunnel.mirt.net/pipermail/stunnel-users/2005-May/000490.html
 >
 > (4.10 is known to be a experimental release (see release  
 > announcement),
 > why did it enter the ports tree at all? *rant*)
 >
 > bye,
 >     - michael
 >
 >
 

From: Michael Ablassmeier <abi@grinser.de>
To: bug-followup@freebsd.org, jrr@alisa.org
Cc:  
Subject: Re: ports/81001: stunnel 4.10 port is broken
Date: Mon, 13 Jun 2005 23:18:39 +0200

 hi again,
 
 On Wed, Jun 08, 2005 at 06:33:47PM -0600, John J. Rushford wrote:
 > Thanks for the info.  Good question, why did the experimental 4.10  
 > get into the ports tree?
 
 upstream sent me the following patch. It seems to fix the issue:
 
  On Mon, Jun 13, 2005 at 11:06:41PM +0200, Michal Trojnara wrote:
  > I have a solution:
  > ftp://stunnel.mirt.net/stunnel/bsd.patch
  > I hope it works for you.
 
 bye,
     - michael
State-Changed-From-To: open->closed 
State-Changed-By: roam 
State-Changed-When: Tue Jun 14 10:40:44 GMT 2005 
State-Changed-Why:  
I added Michael Trojnara's patch to stunnel-4.10_2, committed earlier today. 
Thanks for the problem report and analysis! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=81001 
>Unformatted:
