From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: libvir-list@redhat.com,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: [PATCH v2 0/3] ui: add support for 'secret' object to provide VNC/SPICE passwords
Date: Thu, 11 Mar 2021 11:43:40 +0000 [thread overview]
Message-ID: <20210311114343.439820-1-berrange@redhat.com> (raw)
This fixes a long standing limitation of the VNC/SPICE code which was
unable to securely accept passswords on the CLI, instead requiring use
of separate monitor commands after startup.
In v2:
- Dropped patch removing ACL commands, as it will move to a bigger
deprecation cleanup series
- Rebased and resolved conflicts
Daniel P. Berrangé (3):
ui: introduce "password-secret" option for VNC servers
ui: introduce "password-secret" option for SPICE server
ui: deprecate "password" option for SPICE server
docs/system/deprecated.rst | 8 ++++++++
qemu-options.hx | 18 ++++++++++++++++--
ui/spice-core.c | 32 ++++++++++++++++++++++++++++++--
ui/vnc.c | 23 ++++++++++++++++++++++-
4 files changed, 76 insertions(+), 5 deletions(-)
--
2.29.2
next reply other threads:[~2021-03-11 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 11:43 Daniel P. Berrangé [this message]
2021-03-11 11:43 ` [PATCH v2 1/3] ui: introduce "password-secret" option for VNC servers Daniel P. Berrangé
2021-03-11 11:43 ` [PATCH v2 2/3] ui: introduce "password-secret" option for SPICE server Daniel P. Berrangé
2021-03-11 11:43 ` [PATCH v2 3/3] ui: deprecate "password" " Daniel P. Berrangé
2021-03-11 12:40 ` [PATCH v2 0/3] ui: add support for 'secret' object to provide VNC/SPICE passwords 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=20210311114343.439820-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@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 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).