All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Rich Persaud <rich.p@xensource.com>
Cc: Mark Williamson <maw48@cl.cam.ac.uk>,
	xen-devel@lists.sourceforge.net,
	Ted Hilts <thilts@help-for-you.com>,
	Tim.Deegan@cl.cam.ac.uk
Subject: Re: Xend port
Date: Thu, 03 Mar 2005 11:49:21 -0600	[thread overview]
Message-ID: <42274E21.2020402@us.ibm.com> (raw)
In-Reply-To: <42273EE1.1050905@xensource.com>

Rich Persaud wrote:

> Questions:
>
> 1) xend web interface appears on port 8080 (non SSL).  Is the 
> xend-config.sxp parameter not honored?

I'm not sure.  I'm reasonably sure that even if you could support 
changing the port, changing it to 443 would not automatically make it 
use SSL.

> 2) Does Twisted natively support SSL? I found conflicting statements 
> in my brief research.

I'm not sure about "native" but I'm quite sure you can use SSL with Twisted.

> 3) What is listening on ports 8000 and 8001?

Xend listens on 8000 (provides a web interface).  8001 is used by Xend 
for events.

> 4) Related subject, how is xfrd (port 8002) secured against malicious 
> domain transfers?

It's not.  This is one of the reasons why VM-Tools takes such a 
different approach to domain migration.

All of the tools in VM-Tools are small and single purposed.  One of 
these tools (vm-create) will have the ability to read a saved image from 
standard input.  Another tool (vm-save) will be able to save an image to 
standard output.

Migration is simply a matter of piping vm-save to an instance of 
vm-create executed via ssh.

The transport is actually transparent to the migration process.  You 
could just as easily use rexec, or write a simple remote shell that did 
IP-level filtering instead of authentication.

This approach gives you a wide variety of choices in terms of signing, 
sealing, and authentication mechanisms.  Since ssh uses pam, you 
instantly are tied into most existing single sign-on environments 
(through pam_krb5, pam_winbind, etc.).  While using ssh as the transport 
is debatable, I believe tying into pam is inevitable for any migration 
implementation.

Of course, VM-Tools is still a work in progress.  Someone is currently 
working on migration support.  We're hoping to have it available by the 
end of the month.

Regards,

>
> Rich
>
>
>
>
>
> -------------------------------------------------------
> 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@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>



-------------------------------------------------------
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

  reply	other threads:[~2005-03-03 17:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03  3:32 A little more clarification Ted Hilts
2005-03-03  9:30 ` Tim Deegan
2005-03-03 15:33 ` Mark Williamson
2005-03-03 16:44   ` Xend port Rich Persaud
2005-03-03 17:49     ` Anthony Liguori [this message]
2005-03-03 18:12       ` Mark Williamson
2005-03-03 18:56       ` Matt Piechota
2005-03-05  8:52     ` Tommi Virtanen
2005-03-03 23:56   ` A little more clarification -- Thank You! Ted Hilts

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=42274E21.2020402@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Tim.Deegan@cl.cam.ac.uk \
    --cc=maw48@cl.cam.ac.uk \
    --cc=rich.p@xensource.com \
    --cc=thilts@help-for-you.com \
    --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.