From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] vnc: refuse to set a password with VNC_AUTH_NONE
Date: Wed, 11 Dec 2013 17:43:14 +0100 [thread overview]
Message-ID: <52A89622.8010504@redhat.com> (raw)
In-Reply-To: <1386779361.26258.48.camel@nilsson.home.kraxel.org>
Il 11/12/2013 17:29, Gerd Hoffmann ha scritto:
> On Mi, 2013-12-11 at 17:06 +0100, Paolo Bonzini wrote:
>> Il 11/12/2013 16:54, Gerd Hoffmann ha scritto:
>>> Current code silently changes the authentication settings
>>> in case you try to set a password without password authentication
>>> turned on. This is bad. Return an error instead.
>>>
>>> If we want allow changing auth settings at runtime this should
>>> be done explicitly using a separate monitor command, not as
>>> side effect of set_passwd.
>>>
>>> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>>
>> Isn't this backwards-incompatible?
>
> Yes. I think it is the correct thing nevertheless.
Fine by me, let's just make sure we document it well. Can you start the
2.0 changelog wiki page?
> Users which want a passwort protected guests should configure vnc
> correctly to avoid a unprotected window between qemu start and setting
> the password.
>
> Also note that enabling passwd auth via "set_passwd" side-effect
> bypasses fips restrictions.
That'd be a clear bug, even one that could be fixed in stable versions.
Paolo
> So this is a clear security improvement IMHO.
>
> cheers,
> Gerd
>
>
>
next prev parent reply other threads:[~2013-12-11 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 15:54 [Qemu-devel] [PATCH] vnc: refuse to set a password with VNC_AUTH_NONE Gerd Hoffmann
2013-12-11 16:06 ` Paolo Bonzini
2013-12-11 16:29 ` Gerd Hoffmann
2013-12-11 16:43 ` Paolo Bonzini [this message]
2013-12-12 12:44 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2014-05-21 10:54 Gerd Hoffmann
2014-05-22 4:05 ` Gonglei (Arei)
2014-05-22 5:47 ` Gerd Hoffmann
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=52A89622.8010504@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@amazon.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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 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.