From: Anil Madhavapeddy <anil@recoil.org>
To: Daniel Veillard <veillard@redhat.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ewan Mellor <ewan@xensource.com>
Subject: Re: [RFC][PATCH] Secure XML-RPC for Xend
Date: Fri, 9 Jun 2006 09:54:44 +0100 [thread overview]
Message-ID: <20060609085443.GA28541@fork.recoil.org> (raw)
In-Reply-To: <20060609084147.GH31509@redhat.com>
On Fri, Jun 09, 2006 at 04:41:48AM -0400, Daniel Veillard wrote:
>
> SSH authentication is really expensive especially when you compare to
> other cost in the XML-RPC. I would really like some persistency
> of the connection if possible, especially for operations like monitoring,
> it's okay to reopen from time to time, but without reuse it would just not
> work.
Yes, but the right place to do it is not in Xend. The auth caching
can be set up outside of Xend much more robustly depending on your
version of OpenSSH. If done in Xend, then it definitely needs to
use the wildcard support in ControlPath to avoid the authentication
race condition, and an OpenSSH version check.
As Ian says, stunnel/SSL is probably easier from the client's point
of view (although I do like the easier SSH key management this patch
allows).
Anil
next prev parent reply other threads:[~2006-06-09 8:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 2:13 [RFC][PATCH] Secure XML-RPC for Xend Anthony Liguori
2006-06-09 2:45 ` Matthew Palmer
2006-06-09 8:34 ` Anil Madhavapeddy
2006-06-09 8:41 ` Daniel Veillard
2006-06-09 8:54 ` Anil Madhavapeddy [this message]
2006-06-09 14:57 ` Anthony Liguori
2006-06-09 15:45 ` Daniel Veillard
2006-06-09 15:57 ` Anthony Liguori
2006-06-09 12:00 ` Anthony Liguori
2006-06-14 8:36 ` Ewan Mellor
2006-06-14 17:26 ` Anthony Liguori
2006-06-14 17:36 ` Ewan Mellor
-- strict thread matches above, loose matches on Subject: below --
2006-06-09 8:10 Ian Pratt
2006-06-09 12:10 ` Anthony Liguori
2006-06-14 8:43 ` Ewan Mellor
2006-06-14 17:34 ` Anthony Liguori
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=20060609085443.GA28541@fork.recoil.org \
--to=anil@recoil.org \
--cc=ewan@xensource.com \
--cc=veillard@redhat.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.