stat/fstat incompatibility w/ unix sockets

resolve it? TIA, -p -- Paul Swartz (o_ http://twistedmatrix.com/users/z3p.twistd/ //\ [EMAIL PROTECTED] V_/_ AIM: Z3Penguin The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or

Re: stat/fstat incompatibility w/ unix sockets

at on the filename make it difficult, and probably impossible in some cases, to tell if the socket opened is the same as the file. This makes writing secure software that uses UNIX sockets difficult, if not impossible. -p -- Paul Swartz (o_ http://twistedmatrix.com/users/z3p.t

Re: stat/fstat incompatibility w/ unix sockets

27;t change. The ctime/mtime probably shouldn't either, I'm less sure about atime. I don't have a copy of POSIX, does that say anything about the stat/fstat semantics? -p -- Paul Swartz (o_ http://twistedmatrix.com/users/z3p.twistd/ //\ [EMAIL PROTECTED] V_/_ AIM: Z3Peng