From: Matt Piechota <piechota@argolis.org>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Rich Persaud <rich.p@xensource.com>,
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, 3 Mar 2005 13:56:33 -0500 (EST) [thread overview]
Message-ID: <20050303133456.H9815@acropolis.argolis.org> (raw)
In-Reply-To: <42274E21.2020402@us.ibm.com>
On Thu, 3 Mar 2005, Anthony Liguori wrote:
> 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.
I'm sure I saw it mentioned: you might use stunnel
(http://www.stunnel.org/) to make SSL wrappers for 8080 and whatnot.
--
Matt Piechota
Key Available from pgp.mit.edu
PGP Key fingerprint = FC90 4D65 2F8A 38E9 D1A8 FABB 7AE8 C194 5EC8 9CAD
-------------------------------------------------------
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-03 18:56 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
2005-03-03 18:12 ` Mark Williamson
2005-03-03 18:56 ` Matt Piechota [this message]
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=20050303133456.H9815@acropolis.argolis.org \
--to=piechota@argolis.org \
--cc=Tim.Deegan@cl.cam.ac.uk \
--cc=aliguori@us.ibm.com \
--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.