From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Neil Wilson <neil@aldur.co.uk>, Gerd Hoffman <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] vnc: Fix password expiration through 'change vnc ""'
Date: Thu, 03 Feb 2011 11:16:36 -0600 [thread overview]
Message-ID: <4D4AE2F4.3060901@codemonkey.ws> (raw)
In-Reply-To: <20110203170239.GK19545@redhat.com>
On 02/03/2011 11:02 AM, Daniel P. Berrange wrote:
> On Thu, Feb 03, 2011 at 10:35:51AM -0600, Anthony Liguori wrote:
>
>> On 02/03/2011 10:29 AM, Daniel P. Berrange wrote:
>>
>>> On Mon, Jan 31, 2011 at 02:43:19PM -0600, Anthony Liguori wrote:
>>>
>>>> commit 52c18be9e99dabe295321153fda7fce9f76647ac introduced a regression in the
>>>> change vnc password command that changed the behavior of setting the VNC
>>>> password to an empty string from disabling login to disabling authentication.
>>>>
>>>> This commit refactors the code to eliminate this overloaded semantics in
>>>> vnc_display_password and instead introduces the vnc_display_disable_login. The
>>>> monitor implementation then determines the behavior of an empty or missing
>>>> string.
>>>>
>>> Personally I think this is a little overkill& just reverting the
>>> original patch was fine, but from a functional POV your patch
>>> produces the same results, so I won't argue.
>>>
>> For 0.15, I'd like to introduce a new set of commands such that we
>> don't multiplex the change command anymore. This refactoring lays
>> the ground work for that.
>>
>> For instance, if you created a block device with the name 'vnc',
>> you'd get very unexpected results! Multiplexing based on special
>> values on top of existing commands is pretty evil.
>>
> Doesn't Gerd's 'set_password' command already replace the functionality
> of the 'change vnc' command. So we should likely declare 'change vnc'
> as deprecated in 0.14 and remove it in 0.16
>
Yup. But it doesn't let you disable login. Since that was a feature of
'change vnc', I think we need to provide a proper interface to do this.
Likewise, we need a new interface for changing the block device. The
way password setting is handled is fubar right now.
I've got some new commands documented in a git tree if you're interested.
http://repo.or.cz/w/qemu/aliguori.git/blob/refs/heads/glib:/qmp-schema.json
Regards,
Anthony Liguori
> Regards,
> Daniel
>
next prev parent reply other threads:[~2011-02-03 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 20:43 [Qemu-devel] [PATCH] vnc: Fix password expiration through 'change vnc ""' Anthony Liguori
2011-01-31 21:32 ` Anthony Liguori
2011-02-03 16:29 ` [Qemu-devel] " Daniel P. Berrange
2011-02-03 16:35 ` Anthony Liguori
2011-02-03 17:02 ` Daniel P. Berrange
2011-02-03 17:16 ` Anthony Liguori [this message]
2011-02-04 8:56 ` Markus Armbruster
2011-02-14 10:57 ` Gerd Hoffmann
2011-02-14 12:10 ` Anthony Liguori
2011-02-14 12:24 ` Daniel P. Berrange
2011-02-14 14:14 ` Anthony Liguori
2011-02-14 14:47 ` Daniel P. Berrange
2011-02-14 13:56 ` Gerd Hoffmann
2011-02-14 14:16 ` 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=4D4AE2F4.3060901@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=neil@aldur.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).