ports/81001: stunnel 4.10 port is broken

John J. Rushford Jr. jjr at www.larush.com
Sat May 14 03:10:02 UTC 2005


>Number:         81001
>Category:       ports
>Synopsis:       stunnel 4.10 port is broken
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 14 03:10:01 GMT 2005
>Closed-Date:
>Last-Modified:
>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 at 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:
>Unformatted:



More information about the freebsd-ports-bugs mailing list