X-Spam-Check-By:	sourceware.org
Message-ID:	<4a162fd0511231156h142d7a7fnb598aee09b134ec4@mail.gmail.com>
Date:	Wed, 23 Nov 2005 11:56:55 -0800
From:	Jeff Hardy <linuxrlz AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	WSADuplicateSocket used to implement ssh session multiplexing?
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id jANJv4wc028929

I understand that windows does not allow sending open file descriptors
over sockets and that is the reason that session multiplexing through
a control master doesn't work. The documentation for
WSADuplicateSocket states that the resulting WSAPROTOCOL_INFO
structure can be sent through an IPC to a target process and that the
target process can then call WSASocket with that info and the effect
is a shared socket. If the sending process closes the socket, then the
target has the connection to itself.

 Is this essentially the same as sending an open file descriptor
through a socket? I am of course assuming that the fd that is being
sent is for a socket.

Or am I really missing the big picture?

-jeff hardy

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -