From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tommi Virtanen Subject: Re: [PATCH] xen-2.0: privileged port connections Date: Thu, 24 Mar 2005 21:06:08 +0200 Message-ID: <42430FA0.5050604@tv.debian.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Ian Pratt Cc: Kurt Garloff , Anthony Liguori , Xen development list , ian.pratt@cl.cam.ac.uk List-Id: xen-devel@lists.xenproject.org Ian Pratt wrote: > For Xen 2.x, unix domain sockets would be too much of a pain to > implement over Twisted. Kurt's approach gets us closer toward 'secure by > default'. That just tells me you don't know twisted (putting my "Twisted upstream developer" hat on..) Replace current reactor.listenTCP(port, protocolFactory) with reactor.listenUNIX(path, protocolFactory). If there's code that assumes TCP things (transport.getPeer() to give IP addresses and ports etc), those may need to be fixed, naturally. If you would use .tacs, as the recommended Twisted way of deplying server applications is, that would more like a configuration file change, done in /etc, as suits the admin. If you would use strports, that would be switching from string "8080" to string "unix:/path/to/socket". The actual protocol mechanics work identically. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click