On Mon, Jan 24, 2022 at 02:50:39PM +0100, Markus Armbruster wrote: > Stefan Reiter <s.rei...@proxmox.com> writes: > > > Since the removal of the generic 'qmp_change' command, one can no longer > > replace > > the 'default' VNC display listen address at runtime (AFAIK). For our users > > who > > need to set up a secondary VNC access port, this means configuring a second > > VNC > > display (in addition to our standard one for web-access), but it turns out > > one > > cannot set a password on this second display at the moment, as the > > 'set_password' call only operates on the 'default' display. > > > > Additionally, using secret objects, the password is only read once at > > startup. > > This could be considered a bug too, but is not touched in this series and > > left > > for a later date. > > Related: Vladimir recently posted a patch to add a new command for > changing VNC server listening addresses. Daniel asked him to work it > into display-reload instead[1]. Vladimir complied[2]. > > Daniel, what do you think about this one? Should it also use > display-reload?
I'd ultimately intend to deprecate & remove the direct setting of passwords on the CLI, and exclusively rely on the 'secret' object for passing in passwords. With this in mind, I'd not be enthusiastic about adding new commands for changing passwords in QMP directly, rather I think we should have a way to change the 'secret' object in use. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
