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: 1.3.13?


Quick addenda to the previous email:

*) One reason I changed the UNIX domain socket handshake to avoid
setting and waiting for events was that I hoped to be able to
extend the protocol to the connectionless use of UNIX domain
sockets (cygwin provides no security here at present).  Any
solution based on WSAConnect/WSAAccept obviously wouldn't work for
that, so we'd need another solution there -- a single solution to
both connection-full and -less sockets would be good but I can't
think of one right now.

*) My assumption was, from Egor's revelation, that we can't
control the visibility of an event (or whatever) object, i.e. we
can control what a process can do with an object, via its security
settings, but we can't control it's visibility the same way.  I
don't know the NT security model at all well, but I don't see a
way to do this.

// Conrad




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