From: "Daniel P. Berrange" <berrange@redhat.com>
To: John Anderson <johnha@ccbill.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen API/libvirt & Remote
Date: Fri, 4 Aug 2006 14:46:55 +0100 [thread overview]
Message-ID: <20060804134655.GB23276@redhat.com> (raw)
In-Reply-To: <A7F39817EC2477418A3AA053E69F835A3AA0F8@Exchange.ccbill-hq.local>
On Thu, Aug 03, 2006 at 10:14:05AM -0700, John Anderson wrote:
> Authentication would have been my next question had I discovered that
> remote access was possible and widely used, but since there is no
> authentication mechanism, I agree that opening the http port is a bad
> thing.
>
> I think I've found a solution. I've wrapped the libvirt calls I need
> with gSOAP using SSL certificate authentication. It seems to be
> working for me and secure.
Could you elaborate a little on how you implemented this ? Did it
involve changes to libvirt or xend code to support it ? If its a
solution which other people would benefit from I'd like to see if
we could incorporate any neccessary changes in libvirt, or at least
document it as one of the deployment scenarios.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-08-04 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 17:14 Xen API/libvirt & Remote John Anderson
2006-08-04 13:46 ` Daniel P. Berrange [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-04 18:09 John Anderson
2006-08-05 8:27 ` Daniel Veillard
2006-08-02 23:28 John Anderson
2006-08-03 8:45 ` Daniel Veillard
2006-08-08 21:41 ` Ewan Mellor
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=20060804134655.GB23276@redhat.com \
--to=berrange@redhat.com \
--cc=johnha@ccbill.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.