From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Eric Blake" <eblake@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2 08/11] authz: add QAuthZList object type for an access control list
Date: Fri, 22 Jun 2018 09:41:17 +0100 [thread overview]
Message-ID: <20180622084117.GA23296@redhat.com> (raw)
In-Reply-To: <8736xgjdvg.fsf@dusky.pond.sub.org>
On Thu, Jun 21, 2018 at 06:36:19PM +0200, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Thu, Jun 21, 2018 at 10:28:23AM -0500, Eric Blake wrote:
> >> On 06/15/2018 10:42 AM, Daniel P. Berrangé wrote:
> >> > From: "Daniel P. Berrange" <berrange@redhat.com>
> >> >
> >> > Add a QAuthZList object type that implements the QAuthZ interface. This
> >> > built-in implementation maintains a trivial access control list with a
> >> > sequence of match rules and a final default policy. This replicates the
> >> > functionality currently provided by the qemu_acl module.
> >> >
> >>
> >> >
> >> > It is not currently possible to create this via -object, since there is
> >> > no syntax supported to specify non-scalar properties for objects. This
> >> > is likely to be addressed by later support for using JSON with -object,
> >> > or an equivalent approach.
> >>
> >> Is this statement slightly stale, since we have JSON support with --object
> >> already?
> >
> > That's news to me if we do. Markus did a PoC but AFAIK it was never
> > proposed for merge so far.
>
> Correct. Can finish the job if there's a need.
>
> [...]
I'm not hugely bothered by it - this QAuthZList impl serves two core
purposes - a replacement for the HMP monitor commands I deprecated,
an an engine for the QAuthZListFile which stores QAuthZList objects in
external json files. The latter is what I think we'll use in practice,
as it lets us auto-refresh on the fly via inotify which is much more
convenient than having libvirt do object_add/object_del.
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:[~2018-06-22 8:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 15:41 [Qemu-devel] [PATCH v2 00/11] Add a standard authorization framework Daniel P. Berrangé
2018-06-15 15:41 ` [Qemu-devel] [PATCH v2 01/11] util: add helper APIs for dealing with inotify in portable manner Daniel P. Berrangé
2018-06-15 15:41 ` [Qemu-devel] [PATCH v2 02/11] qom: don't require user creatable objects to be registered Daniel P. Berrangé
2018-06-15 15:41 ` [Qemu-devel] [PATCH v2 03/11] hw/usb: don't set IN_ISDIR for inotify watch in MTP driver Daniel P. Berrangé
2018-06-15 15:41 ` [Qemu-devel] [PATCH v2 04/11] hw/usb: fix const-ness for string params " Daniel P. Berrangé
2018-06-15 15:41 ` [Qemu-devel] [PATCH v2 05/11] hw/usb: switch MTP to use new inotify APIs Daniel P. Berrangé
2018-06-15 15:41 ` [Qemu-devel] [PATCH v2 06/11] authz: add QAuthZ object as an authorization base class Daniel P. Berrangé
2018-06-15 15:41 ` [Qemu-devel] [PATCH v2 07/11] authz: add QAuthZSimple object type for easy whitelist auth checks Daniel P. Berrangé
2018-06-15 15:42 ` [Qemu-devel] [PATCH v2 08/11] authz: add QAuthZList object type for an access control list Daniel P. Berrangé
2018-06-21 15:28 ` Eric Blake
2018-06-21 15:39 ` Daniel P. Berrangé
2018-06-21 16:36 ` Markus Armbruster
2018-06-22 8:41 ` Daniel P. Berrangé [this message]
2018-06-15 15:42 ` [Qemu-devel] [PATCH v2 09/11] authz: add QAuthZListFile object type for a file " Daniel P. Berrangé
2018-06-21 15:30 ` Eric Blake
2018-06-21 15:40 ` Daniel P. Berrangé
2018-06-15 15:42 ` [Qemu-devel] [PATCH v2 10/11] authz: add QAuthZPAM object type for authorizing using PAM Daniel P. Berrangé
2018-06-15 15:42 ` [Qemu-devel] [PATCH v2 11/11] authz: delete existing ACL implementation 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=20180622084117.GA23296@redhat.com \
--to=berrange@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@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.