From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Veillard Subject: Re: [RFC][PATCH] Secure XML-RPC for Xend Date: Fri, 9 Jun 2006 04:41:48 -0400 Message-ID: <20060609084147.GH31509@redhat.com> References: <4488D93D.7070303@us.ibm.com> <20060609083434.GA19035@fork.recoil.org> Reply-To: veillard@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20060609083434.GA19035@fork.recoil.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anil Madhavapeddy Cc: xen-devel , Ewan Mellor List-Id: xen-devel@lists.xenproject.org On Fri, Jun 09, 2006 at 09:34:35AM +0100, Anil Madhavapeddy wrote: > > 1) Python moans about tempnam(). I don't think there's a better solution > > though. > > I don't like the dependency on directly calling ssh multiplexing, > as it requires a relatively modern OpenSSH (>3.9) and the above > race condition is introduced. A newer feature in OpenSSH is to let > the ControlPath consist of "%h,%p,%r" wildcards which fill in the > host/user/port being connected to in a socket pathname, which solves > that particular race. > > Why not just do the SSH every time, and let the user either set up > connection multiplexing or ssh agent in their local environment > instead? 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. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/