From: Anthony Liguori <aliguori@us.ibm.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ewan Mellor <ewan@xensource.com>
Subject: Re: Xend listening for TCP HTTP?
Date: Thu, 15 Dec 2005 17:48:35 -0600 [thread overview]
Message-ID: <43A200D3.6030003@us.ibm.com> (raw)
In-Reply-To: <43A1FF98.7010803@us.ibm.com>
Nivedita Singhvi wrote:
> Anthony Liguori wrote:
>
>> Ok, I confirmed this, out of the box, accessing
>> http://localhost:8000/xen/domain as a lesser-privileged user allows
>> one to do very bad things.
>
>
> Anthony, were you using the default xend-config.sxp?
Yup.
> Currently, although the default is off for http support
> in xend, the default config file turns it on:
>
> #(xend-http-server no)
> (xend-http-server yes)
Yup. This was added in:
# HG changeset patch
# User emellor@leeni.uk.xensource.com
# Node ID cefe36be8592090b4edb08060cca67a004c04617
# Parent 4d49f61a7feef3fca5fb3e991a5a1d741b6cd690
Tidy xend-config.sxp, removing entries that haven't been used since the
hotplugging stuff was introduced (block-*, console-port-base,
console-address)
and introducing entries for options that have been present for ages
(xend-{http,unix,relocation}-server, xend-unix-path,
xend-relocation-address,
enable-dump). Remove vif-antispoof, as Vifctl no longer passes this option
down.
I imagine it was unintentional. Ewan?
Regards,
Anthony Liguori
> thanks,
> Nivedita
>
>> Regards,
>>
>> Anthony Liguori
>>
>> Anthony Liguori wrote:
>>
>>> Hi,
>>>
>>> On IRC, it came up that recent snapshots of Xend are now listening
>>> for TCP HTTP connections again by default. Since it's still
>>> listening on a Unix socket and xm will always prefer that, xm still
>>> only functions as root.
>>>
>>> However, less privileged users can still connect to the TCP port and
>>> through Xend gain root access. This seems like a pretty bad default
>>> configuration. I poked around on the TCP interface but couldn't
>>> seem to confirm this (does it only accept s-expression Content-Type
>>> now?).
>>>
>>> Thanks for any clarification on this.
>>>
>>> Regards,
>>>
>>> Anthony Liguori
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>
>
>
prev parent reply other threads:[~2005-12-15 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 22:12 Xend listening for TCP HTTP? Anthony Liguori
2005-12-15 22:16 ` Anthony Liguori
2005-12-15 23:43 ` Nivedita Singhvi
2005-12-15 23:48 ` Anthony Liguori [this message]
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=43A200D3.6030003@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=ewan@xensource.com \
--cc=niv@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.