All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Veillard <veillard@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com, Ewan Mellor <ewan@xensource.com>
Subject: Re: [RFC] Xend XML-RPC Refactoring
Date: Sun, 12 Mar 2006 04:27:24 -0500	[thread overview]
Message-ID: <20060312092724.GB22089@redhat.com> (raw)
In-Reply-To: <44137D7B.7050403@us.ibm.com>

On Sat, Mar 11, 2006 at 07:46:35PM -0600, Anthony Liguori wrote:
> Ewan Mellor wrote:
> >On Sat, Mar 11, 2006 at 04:36:57PM -0500, Daniel Veillard wrote:
> >
> >Turning the server on and off is just for basic sanity -- the admin gets
> >to choose which ports they want open so that they don't have to audit
> >aspects in which they aren't interested.
> >
> >Of course, a full user / permissions system for the protocol would be a
> >good idea, but like you say, it's not trivial work.  We could kick that
> >discussion off if you want, but it's going to need someone to design
> >the permissions semantics, management of users and roles, etc.  Is
> >anyone interested in starting this?
> >  
> We can do basic authentication and require root credentials as a start.  
> That's really easy to do but I'm not sure sending the root password as 
> clear text really makes things much better :-)
> 
> Python, unfortunately, doesn't have server-side SSL bindings so basic 
> authentication over SSL is not an option without some custom OpenSSL 
> bindings.

  Hum, I could check how much "custom" is required, I remember doing
that a long time ago but I could ask around :-) if interested.

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/

  reply	other threads:[~2006-03-12  9:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 23:37 [RFC] Xend XML-RPC Refactoring Ian Pratt
2006-03-08  0:07 ` Anthony Liguori
2006-03-11 20:55   ` Ewan Mellor
2006-03-11 21:36     ` Daniel Veillard
2006-03-11 22:20       ` Ewan Mellor
2006-03-12  1:46         ` Anthony Liguori
2006-03-12  9:27           ` Daniel Veillard [this message]
2006-03-12  9:57         ` Daniel Veillard
2006-03-12 17:41           ` Anthony Liguori
2006-03-12 18:29             ` Daniel Veillard
2006-03-12 20:28               ` Anthony Liguori
2006-03-12 21:49                 ` Daniel Veillard
2006-03-12  1:44     ` Anthony Liguori
2006-03-13 10:30       ` Ewan Mellor
2006-03-14  6:58     ` Anthony Liguori
2006-03-14  8:35       ` Ewan Mellor
  -- strict thread matches above, loose matches on Subject: below --
2006-01-31 21:25 Anthony Liguori
2006-01-31 21:36 ` Ronald G Minnich
2006-01-31 21:47   ` Matt Sottile
2006-01-31 21:58   ` Anthony Liguori
2006-02-01  9:53   ` Ewan Mellor
2006-02-01  9:37 ` Daniel Veillard

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=20060312092724.GB22089@redhat.com \
    --to=veillard@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=ewan@xensource.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.