Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Message-ID:	<3E676D2B.B4AD2239@ieee.org>
Date:	Thu, 06 Mar 2003 10:45:47 -0500
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Accept-Language:	en,pdf
MIME-Version:	1.0
To:	Jason Tishler <jason AT tishler DOT net>,
	"cygwin-developers AT cygwin DOT com" <cygwin-developers AT cygwin DOT com>
Subject:	Re: Winsock closesocket() problem
References:	<20030306144658 DOT GB2008 AT tishler DOT net> <3E6762CA DOT 8EF5B6A8 AT ieee DOT org> <20030306154047 DOT GC2008 AT tishler DOT net>

Jason,

in your test case the setuid is called after the initial socket().
Thus it is conceivable that the impersonated thread (after setuid) 
cannot always access the socket.

However when you first brought up the issue with exim, setuid()
occurs before socket().
Also exim can send and receive on those sockets, the only problem
is in closing them.

Just adding info, not explaining anything :(

Pierre

- Raw text -