From: Masami Watanabe <masami.watanabe@jp.fujitsu.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
xen-devel@lists.xensource.com
Cc: masami.watanabe@jp.fujitsu.com
Subject: Re: Individual passwords for guest VNC servers ?
Date: Thu, 31 Aug 2006 11:57:59 +0900 [thread overview]
Message-ID: <JD2006083111575929.65190015@jp.fujitsu.com> (raw)
In-Reply-To: <JC2006083110235610.59547031@jp.fujitsu.com>
Hi Dan,
I take your point about security, I'll do as follows.
- vnc_passwd is not omissible.
- The domain cannot be created if there is no vnc_passwd.
Thanks.
Watanabe.
> On Thu, Aug 31, 2006 at 10:23:56AM +0900, Masami Watanabe wrote:
> > I'm thinking of adding the following protection to VNC console.
> > I know it's not perfect, nonetheless, it's far better than the current
> > no protection situation. Please comment.
> >
> > Specification:
> > - The same challenge-response auth scheme as standard VNC to be available
> > from VNC viewer (like RealVNC).
>
> Yeah, looking at the various clients, challenge-response is the only one
> we can really rely on being present - in fact its the only one supported
> by Fedora VNC client (RealVNC IIRC?) at all.
>
> > - The vnc password of each VM is described in the VM configuration file.
> > When omit the password, do not use authentification.
> > ex) vnc_passwd = xxxxx
>
> I think we should be secure by default - if they omit the password then
> we should either generate one - and store it in xenstore, or refuse to
> activate VNC server. If we really really want to allow no passwords, then
> admin could have to explicitly request it with vnc_no_password=1
> in the config file - but my prefernce is still that we should flat out
> refuse to allow an empty password - in this day & day its just plain wrong.
> RealVNC server for example, refuses to allow empty password.
>
> > - Where "xxxxx" is an uuencoded encrypted password, that is,
> > you can get this value by
> > # cat ~/.vnc/passwd | uuencode -m passwd
> > (needs uuencode command: sharutils package)
>
> Perhaps base64 would be preferable - that's a standard part of Linux
> coreutils toolset, rather than an addon like uuencode is.
>
> Regards,
> 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 -=|
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-08-31 2:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 18:11 Individual passwords for guest VNC servers ? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 10:45 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
2006-09-26 8:07 ` Masami Watanabe
2006-09-26 14:25 ` Anthony Liguori
2006-09-28 1:04 ` Masami Watanabe
2006-09-26 18:23 Ian Pratt
2006-09-28 1:01 ` 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=JD2006083111575929.65190015@jp.fujitsu.com \
--to=masami.watanabe@jp.fujitsu.com \
--cc=berrange@redhat.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.