public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul J R <me-wwXWdph6gTo@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: web interface?
Date: Wed, 01 Aug 2007 01:52:39 +1000	[thread overview]
Message-ID: <46AF5AC7.7080509@pjr.cc> (raw)

Hi guys, I had a quick question.

I was playing around writing a php-based web interface for KVM. 
Basically something that would allow you to use a tiny distro and let 
you manage disk/net etc via php (atm its crude to say the least).

It all seems relatively straight forward except for one component - the 
console bits. I wanted to make it so you could click on your new vm, 
then click on a "console" link and *poof* your console appears on your 
web browser via an embedded java applet. The problem is security, 
Authenticating users on the page is simple enough, but i cant see a 
method by which i could put a password on the vnc port in qemu?

Ideally, what i would like to be able to do is when someone accesses the 
console it sets the password randomly, then embed's it into the request. 
Once everyone disconnects it resets the password (but thats not quite so 
important at this point).

Of course, if someone is already doing a web interface then i'd like to 
know that too :)

Thanks in advance guys.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

             reply	other threads:[~2007-07-31 15:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 15:52 Paul J R [this message]
     [not found] ` <46AF5AC7.7080509-wwXWdph6gTo@public.gmane.org>
2007-07-31 16:20   ` web interface? ron minnich
     [not found]     ` <13426df10707310920g3762c0b7l674c3767d3ec852b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-31 16:25       ` Jorge Lucángeli Obes
     [not found]         ` <59abf66e0707310925q6164754fgeb639ea0a51752d8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-31 17:26           ` Paul J R
     [not found]             ` <46AF70E1.2020107-wwXWdph6gTo@public.gmane.org>
2007-07-31 18:03               ` Daniel P. Berrange
     [not found]                 ` <20070731180358.GG18730-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-08-01 16:25                   ` Paul J R
     [not found]                     ` <46B0B40A.7070307-wwXWdph6gTo@public.gmane.org>
2007-08-01 16:36                       ` Daniel P. Berrange
2007-07-31 21:49               ` ron minnich
     [not found]                 ` <13426df10707311449k3954bd1dkba1025d5a12ac2fc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-01 15:47                   ` Paul J R
2007-07-31 16:33   ` Matthew Kent
2007-07-31 18:05     ` Daniel P. Berrange
2007-07-31 16:40   ` Avi Kivity
2007-07-31 16:57   ` Daniel P. Berrange
     [not found]     ` <20070731165737.GF18730-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-07-31 17:10       ` Matthew Kent

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=46AF5AC7.7080509@pjr.cc \
    --to=me-wwxwdph6gto@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox