All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: Monitor commands related to display server passwords
Date: Thu, 1 Dec 2022 09:20:38 +0000	[thread overview]
Message-ID: <Y4hx5lfQetJQm19s@redhat.com> (raw)
In-Reply-To: <Y4ccR2d2GUHpmHwx@redhat.com>

On Wed, Nov 30, 2022 at 09:03:03AM +0000, Daniel P. Berrangé wrote:
> On Wed, Nov 30, 2022 at 09:02:56AM +0100, Markus Armbruster wrote:

> > Related: QCryptoSecret objects.
> 
> snip
> 
> > Currently used by various block backends and the tls-creds-x509 object.
> > 
> > Would it make sense with display servers, too?
> 
> In 6.0 I introduced support for 'password-secret' to SPICE and VNC
> command line.
> 
> I don't know why, but I only deprecated 'password' in SPICE and
> not in VNC.

The 'password' option in VNC isn't actually setting a password,
it is more like saying  'auth=password'. The actualpassword
had to be set via the 'change' command, we never allowed it on
the CLI before. So there was nothing to deprecate for VNC, only
SPICE.

With 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 :|



      parent reply	other threads:[~2022-12-01  9:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30  8:02 Monitor commands related to display server passwords Markus Armbruster
2022-11-30  9:03 ` Daniel P. Berrangé
2022-11-30 13:25   ` Markus Armbruster
2022-11-30 13:29     ` Daniel P. Berrangé
2022-12-01  6:48       ` Markus Armbruster
2022-12-01  9:20   ` Daniel P. Berrangé [this message]

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=Y4hx5lfQetJQm19s@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.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.