From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
libvir-list@redhat.com, Gerd Hoffmann <kraxel@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] ui: support for authorization control on TLS connections
Date: Thu, 7 Mar 2019 12:23:58 +0000 [thread overview]
Message-ID: <20190307122358.GV32268@redhat.com> (raw)
In-Reply-To: <20190227145755.26556-1-berrange@redhat.com>
ping - soft freeze is less than a week away & i'd like this to get into
a ui queue pull request in time for 4.0 if there's no review objections
On Wed, Feb 27, 2019 at 02:57:53PM +0000, Daniel P. Berrangé wrote:
> This series provides the VNC parts of the authorization control series
> previously posted as:
>
> v1: https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg04482.html
> v2: https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg05727.html
> v3: https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg01639.html
> v4: https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg04319.html
>
> The core authz framework is now merged & these patches have all had
> positive review. Thus these VNC parts are ready to go into the VNC
> maintainer's tree, should the maintainer consider them acceptable.
>
> Note the 2nd patch is modifying the HMP, but I considered it part
> of ui/vnc, since that's the only bit of QEMU which ever used these
> HMP commands, and it has a dependancy on the first patch merging
> first.
>
> Daniel P. Berrangé (2):
> vnc: allow specifying a custom authorization object name
> monitor: deprecate acl_show, acl_reset, acl_policy, acl_add,
> acl_remove
>
> monitor.c | 23 ++++++++++++++++++
> qemu-deprecated.texi | 11 +++++++++
> qemu-options.hx | 35 ++++++++++++++++++--------
> ui/vnc.c | 58 +++++++++++++++++++++++++++++++++++++-------
> 4 files changed, 108 insertions(+), 19 deletions(-)
>
> --
> 2.20.1
>
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 :|
next prev parent reply other threads:[~2019-03-07 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 14:57 [Qemu-devel] [PATCH 0/2] ui: support for authorization control on TLS connections Daniel P. Berrangé
2019-02-27 14:57 ` [Qemu-devel] [PATCH 1/2] vnc: allow specifying a custom authorization object name Daniel P. Berrangé
2019-02-27 14:57 ` [Qemu-devel] [PATCH 2/2] monitor: deprecate acl_show, acl_reset, acl_policy, acl_add, acl_remove Daniel P. Berrangé
2019-03-07 12:23 ` Daniel P. Berrangé [this message]
2019-03-07 13:27 ` [Qemu-devel] [PATCH 0/2] ui: support for authorization control on TLS connections Gerd Hoffmann
2019-03-07 13:32 ` Daniel P. Berrangé
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=20190307122358.GV32268@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 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.