From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PULL 00/11] Merge authz core patches
Date: Wed, 27 Feb 2019 09:31:41 +0000 [thread overview]
Message-ID: <20190227093141.GC31688@redhat.com> (raw)
In-Reply-To: <41d3532c-0ab4-db82-dc9a-cc9fb45c6162@redhat.com>
On Tue, Feb 26, 2019 at 08:07:34PM +0100, Philippe Mathieu-Daudé wrote:
> On 2/26/19 8:04 PM, Peter Maydell wrote:
> > On Mon, 25 Feb 2019 at 12:35, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >>
> >> The following changes since commit 8eb29f1bf5a974dc4c11d2d1f5e7c7f7a62be116:
> >>
> >> Merge remote-tracking branch 'remotes/awilliam/tags/vfio-updates-20190221.0' into staging (2019-02-22 15:48:04 +0000)
> >>
> >> are available in the Git repository at:
> >>
> >> https://github.com/berrange/qemu tags/authz-core-pull-request
> >>
> >> for you to fetch changes up to cfde05c6c0db7d3122a5491d50f62f7910ab8abb:
> >>
> >> authz: delete existing ACL implementation (2019-02-25 12:28:25 +0000)
> >>
> >> ----------------------------------------------------------------
> >> Add a standard authorization framework
> >>
> >> The current network services now support encryption via TLS and in some
> >> cases support authentication via SASL. In cases where SASL is not
> >> available, x509 client certificates can be used as a crude authorization
> >> scheme, but using a sub-CA and controlling who you give certs to. In
> >> general this is not very flexible though, so this series introduces a
> >> new standard authorization framework.
> >>
> >
> > Applied, thanks.
>
> Argh there is a v2... Daniel didn't NACK'd this one.
It is no big deal. The only changes were very minor and were fine as
a followup.
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 :|
prev parent reply other threads:[~2019-02-27 9:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 12:31 [Qemu-devel] [PULL 00/11] Merge authz core patches Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 01/11] util: add helper APIs for dealing with inotify in portable manner Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 02/11] qom: don't require user creatable objects to be registered Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 03/11] hw/usb: don't set IN_ISDIR for inotify watch in MTP driver Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 04/11] hw/usb: fix const-ness for string params " Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 05/11] hw/usb: switch MTP to use new inotify APIs Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 06/11] authz: add QAuthZ object as an authorization base class Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 07/11] authz: add QAuthZSimple object type for easy whitelist auth checks Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 08/11] authz: add QAuthZList object type for an access control list Daniel P. Berrangé
2019-02-25 14:36 ` Eric Blake
2019-02-26 6:04 ` Markus Armbruster
2019-02-26 15:29 ` Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 09/11] authz: add QAuthZListFile object type for a file " Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 10/11] authz: add QAuthZPAM object type for authorizing using PAM Daniel P. Berrangé
2019-02-25 12:31 ` [Qemu-devel] [PULL 11/11] authz: delete existing ACL implementation Daniel P. Berrangé
2019-02-26 19:04 ` [Qemu-devel] [PULL 00/11] Merge authz core patches Peter Maydell
2019-02-26 19:07 ` Philippe Mathieu-Daudé
2019-02-26 19:09 ` Peter Maydell
2019-02-27 11:12 ` Daniel P. Berrangé
2019-02-27 9:31 ` 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=20190227093141.GC31688@redhat.com \
--to=berrange@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@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.