From: Tommi Virtanen <tv@tv.debian.net>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Kurt Garloff <garloff@suse.de>,
Anthony Liguori <aliguori@us.ibm.com>,
Xen development list <xen-devel@lists.sourceforge.net>,
ian.pratt@cl.cam.ac.uk
Subject: Re: [PATCH] xen-2.0: privileged port connections
Date: Thu, 24 Mar 2005 21:06:08 +0200 [thread overview]
Message-ID: <42430FA0.5050604@tv.debian.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3818@liverpoolst.ad.cl.cam.ac.uk>
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
next prev parent reply other threads:[~2005-03-24 19:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 17:43 [PATCH] xen-2.0: privileged port connections Ian Pratt
2005-03-23 17:59 ` Ryan Harper
2005-03-23 21:36 ` Kurt Garloff
2005-03-24 19:06 ` Tommi Virtanen [this message]
2005-03-24 19:56 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2005-03-23 18:51 Ian Pratt
2005-03-23 19:27 ` Anthony Liguori
2005-03-23 21:37 ` Christian Limpach
2005-03-23 23:58 ` Kurt Garloff
2005-03-23 12:36 Kurt Garloff
2005-03-23 15:41 ` Anthony Liguori
2005-03-23 16:57 ` Kurt Garloff
2005-03-23 17:03 ` Anthony Liguori
2005-03-23 17:23 ` Kurt Garloff
2005-03-23 17:45 ` Anthony Liguori
2005-03-23 18:06 ` Rik van Riel
2005-03-23 17:36 ` Nivedita Singhvi
2005-03-24 7:31 ` David Hopwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42430FA0.5050604@tv.debian.net \
--to=tv@tv.debian.net \
--cc=aliguori@us.ibm.com \
--cc=garloff@suse.de \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.