From: Anthony Liguori <aliguori@us.ibm.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ewan Mellor <ewan@xensource.com>
Subject: Re: [RFC][PATCH] Secure XML-RPC for Xend
Date: Fri, 09 Jun 2006 07:00:57 -0500 [thread overview]
Message-ID: <448962F9.5020400@us.ibm.com> (raw)
In-Reply-To: <20060609083434.GA19035@fork.recoil.org>
> 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? That way it will work for old OpenSSH versions and you
> don't have to deal with all the quirks.
>
Another option is just to make sure that the XML-RPC supports keep-alive
and reuse the same xm serve session. I think that's probably the most
compatible approach.
>> 2) A command *must* be executed to cleanup the ssh session on exit. I
>> currently use __del__() which doesn't seem to make Python happy in certain
>> cases.
>> 3) I have done basic testing but not regression testing with xm-test
>>
>> diff -r 4f1e39ec05d6 -r 4de241a7e91a tools/python/xen/util/xmlrpclib2.py
>>
> ...
>
>> + def runcmd(self, cmd, data=None):
>> + """Runs a command using an existing SSH connection.
>> +
>> + This function will run the passed in command on a remote
>> + machine and either return the output or raise an OSError
>> + if the command exits with a non-zero status (or some
>> + other failure occurs)."""
>> +
>> + cmdline = self.getcmd(cmd)
>> + if data:
>> + f = open("/tmp/stuff.txt", "w")
>> + f.write(data)
>> + f.close()
>> + cmdline = "cat /tmp/stuff.txt | %s" % cmdline
>>
>
> Ouch, this bit definitely needs to be fixed at least :)
>
Yikes, didn't know that was still there :-)
Regards,
Anthony Liguori
next prev parent reply other threads:[~2006-06-09 12:00 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
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 [this message]
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=448962F9.5020400@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=anil@recoil.org \
--cc=ewan@xensource.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.