From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
Masami Watanabe <masami.watanabe@jp.fujitsu.com>
Subject: Re: Individual passwords for guest VNC servers ?
Date: Fri, 22 Sep 2006 15:43:30 +0100 [thread overview]
Message-ID: <20060922144330.GG31773@redhat.com> (raw)
In-Reply-To: <3AAA99889D105740BE010EB6D5A5A3B202A30D@paddington.ad.cl.cam.ac.uk>
On Fri, Sep 22, 2006 at 02:54:24PM +0100, Ian Pratt wrote:
> > Passing around passwords either on the command line, or environment is
> a
> > big red flag from a security POV. Also the Xen guest & xend config
> files
> > all default to world readable. I think we should follow the Apache
> model
> > and store the passwords out-of-band from the main config. eg
> >
> > (vncpasswordfile '/etc/xen/vncpassword')
> >
> > At this point it would make sense to have one password file for all
> guests,
> > and store them in format: 'vm-name: pw-hash'
>
> The new life cycle management stuff in post 3.0.3 xend changes this
> quite a bit as a config file is only used when initially creating a VM,
> and then information about it gets stored in xend's database. The
> current password associated with a VM would be one of the parameters
> stored in the database, and should be updated using 'xm vnc-password' or
> shuch like.
As long as XenD makes sure its DB is not world readable, this sounds
reasonable.
> > As Ian just suggested we could have command 'xm password' for
> updating
> > these passwords (cf apache's htpasswd command)
> >
> > Now when launching qemu-dm, we can either pass the path to the
> password
> > file on its command line, eg -passwordfile /etc/xen/password, or
> > passs the actual password to qemu-dm down a pipe (eg qemu-dm would
> read
> > the password from filehandle 3 upon startup). The latter would be my
> > preference, since then we could isolate the password handling stuff in
> > Xend, and not duplicate it in qemu-dm, and the paravirt equivalent.
>
> I wouldn't rely on qemu-dm staying in dom0. I think the information
> should be passed transiently via xenstore.
Yeah, that's probably best solution particularly since qemu-dm is
already reading/writing to the xenstore it should be little work
to also fetch the password from there.
Dan,
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-09-22 14:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 10:45 Individual passwords for guest VNC servers ? Ian Pratt
2006-09-22 12:04 ` Masami Watanabe
2006-09-22 12:49 ` Ian Pratt
2006-09-22 13:12 ` Daniel P. Berrange
2006-09-22 13:54 ` Ian Pratt
2006-09-22 14:03 ` Anthony Liguori
2006-09-22 14:43 ` Daniel P. Berrange [this message]
2006-09-26 8:07 ` Masami Watanabe
2006-09-26 14:25 ` Anthony Liguori
2006-09-28 1:04 ` Masami Watanabe
-- strict thread matches above, loose matches on Subject: below --
2006-09-26 18:23 Ian Pratt
2006-09-28 1:01 ` Masami Watanabe
2006-08-16 18:11 Daniel P. Berrange
2006-08-25 0:44 ` Daniel P. Berrange
[not found] ` <44F0FE76.4010104@codemonkey.ws>
2006-08-27 22:21 ` Daniel P. Berrange
2006-08-31 1:23 ` Masami Watanabe
2006-08-31 1:38 ` Daniel P. Berrange
2006-08-31 15:43 ` George Dunlap
2006-08-31 2:57 ` Masami Watanabe
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=20060922144330.GG31773@redhat.com \
--to=berrange@redhat.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=masami.watanabe@jp.fujitsu.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.