From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>,
Masami Watanabe <masami.watanabe@jp.fujitsu.com>
Subject: Re: Individual passwords for guest VNC servers ?
Date: Fri, 22 Sep 2006 09:03:47 -0500 [thread overview]
Message-ID: <4513ED43.2020007@us.ibm.com> (raw)
In-Reply-To: <3AAA99889D105740BE010EB6D5A5A3B202A30D@paddington.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> Passing around passwords either on the command line, or environment is
>>
VNC password is very easy to support. The only problem is storing the
password (as everyone seems to understand). One thing I want to point
out though is that the VNC password is almost plain-text equiv at this
point.
There are some more interesting things that can be done to secure VNC
(like tunnel it through ssh). It would be nice to consider automating
this sort of thing if we're going to try and attempt to implement
security features.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2006-09-22 14:03 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 [this message]
2006-09-22 14:43 ` Daniel P. Berrange
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=4513ED43.2020007@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=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.