From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com,
Masami Watanabe <masami.watanabe@jp.fujitsu.com>
Subject: Re: [PATCH][Take 2] VNC authentification
Date: Mon, 2 Oct 2006 19:12:32 +0100 [thread overview]
Message-ID: <20061002181231.GC1730@redhat.com> (raw)
In-Reply-To: <45214B54.8060805@us.ibm.com>
On Mon, Oct 02, 2006 at 12:24:36PM -0500, Anthony Liguori wrote:
> Daniel P. Berrange wrote:
> >
> >>--- a/tools/examples/xend-config.sxp Wed Sep 27 17:49:22 2006 +0100
> >>+++ b/tools/examples/xend-config.sxp Sun Oct 01 02:13:06 2006 +0900
> >>@@ -130,3 +130,7 @@
> >>
> >> # The tool used for initiating virtual TPM migration
> >> #(external-migration-tool '')
> >>+
> >>+# The default password for VNC console on HVM domain.
> >>+# Empty string is no authentication.
> >>+(vncpasswd '')
> >>
> >
> >We should add a note about this needing to be the base-64 encoded,
> >DES encrypted password, rather than plain text.
> >
>
> Why even bother encrypting the password? We're using a well known DES
> key so there is no security here. A user must still take appropriate
> precautions to protect the config files. In fact, I think munging the
> password like this gives a false sense of security.
Yeah, we really need to chmod 700 the /etc/xen directory to protect
the passwords. Once this is done, there isn't much to be gained
from encryption in the file itself except for obfuscating it from
the benign casual observer. Using plain text in the config file would
make life easier to tools too, because they won't have to carry about
this VNC-specific DES encryption routine just to create passwds in the
guest config
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-10-02 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 18:23 Individual passwords for guest VNC servers ? Ian Pratt
2006-09-28 1:01 ` Masami Watanabe
2006-09-29 8:47 ` [PATCH][Take 2] VNC authentification Masami Watanabe
2006-09-29 14:01 ` Anthony Liguori
2006-09-30 18:47 ` masami.watanabe
2006-09-29 22:11 ` Daniel P. Berrange
2006-09-30 18:53 ` Masami Watanabe
2006-10-02 16:22 ` Daniel P. Berrange
2006-10-02 17:24 ` Anthony Liguori
2006-10-02 18:12 ` Daniel P. Berrange [this message]
2006-10-02 19:15 ` Ian Pratt
2006-10-03 2:04 ` Masami Watanabe
2006-10-03 16:08 ` [PATCH][Take 3] " Masami Watanabe
2006-10-03 17:56 ` Anthony Liguori
2006-10-03 18:06 ` Daniel P. Berrange
2006-10-03 18:49 ` 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=20061002181231.GC1730@redhat.com \
--to=berrange@redhat.com \
--cc=aliguori@us.ibm.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.