WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] xen-2.0: privileged port connections

To: Tommi Virtanen <tv@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen-2.0: privileged port connections
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Thu, 24 Mar 2005 13:56:29 -0600
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Kurt Garloff <garloff@xxxxxxx>, Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, ian.pratt@xxxxxxxxxxxx
Delivery-date: Thu, 24 Mar 2005 19:50:37 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42430FA0.5050604@xxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: IBM
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3818@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <42430FA0.5050604@xxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
On Thu, 2005-03-24 at 13:06, Tommi Virtanen wrote:
> 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.

Thanks, I couldn't figure out why exporting the consoles over a domain
socket wasn't working :-)  Turns out we're using .getPeer().

I think perhaps we didn't use twisted as best as we could have so I
agree with that it's going to be a fair bit of work.

Regards,

-- 
Anthony Liguori
Linux Technology Center (LTC) - IBM Austin
E-mail: aliguori@xxxxxxxxxx
Phone: (512) 838-1208




-------------------------------------------------------
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel