From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.sourceforge.net
Subject: Re: [PATCH] xen-2.0: privileged port connections
Date: Thu, 24 Mar 2005 07:31:06 +0000 [thread overview]
Message-ID: <42426CBA.4000108@blueyonder.co.uk> (raw)
In-Reply-To: <20050323123639.GM12479@tpkurt.garloff.de>
Kurt Garloff wrote:
> Hi,
>
> as discussed previously, I went ahead and introduced a setting that
> allows you to restrict the stuff you can when controlling xen by
> connecting to the port 8000 unless you connect from a privileged
> port.
I thought the consensus was to use Unix domain socket-based
restrictions for this?
--
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
next prev parent reply other threads:[~2005-03-24 7:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 12:36 [PATCH] xen-2.0: privileged port connections 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-23 17:43 Ian Pratt
2005-03-23 17:59 ` Ryan Harper
2005-03-24 19:06 ` Tommi Virtanen
2005-03-24 19:56 ` Anthony Liguori
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
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=42426CBA.4000108@blueyonder.co.uk \
--to=david.nospam.hopwood@blueyonder.co.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.