This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Winsock closesocket() problem

From: "Pierre A. Humblet" <Pierre dot Humblet at ieee dot org>
To: Jason Tishler <jason at tishler dot net>, "cygwin-developers at cygwin dot com" <cygwin-developers at cygwin dot com>
Date: Thu, 06 Mar 2003 10:45:47 -0500
Subject: Re: Winsock closesocket() problem
References: <20030306144658.GB2008@tishler.net> <3E6762CA.8EF5B6A8@ieee.org> <20030306154047.GC2008@tishler.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

References:
- Winsock closesocket() problem
  - From: Jason Tishler
- Re: Winsock closesocket() problem
  - From: Pierre A. Humblet
- Re: Winsock closesocket() problem
  - From: Jason Tishler

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]