Re: [Qemu-devel] [PATCH v3 10/10] vnc: allow specifying a custom ACL object name

2016-03-23 Thread Daniel P. Berrange
On Tue, Mar 22, 2016 at 03:38:14PM -0600, Eric Blake wrote: > On 03/10/2016 11:59 AM, Daniel P. Berrange wrote: > > The VNC server has historically had support for ACLs to check > > both the SASL username and the TLS x509 distinguished name. > > The VNC server was responsible for creating the initi

Re: [Qemu-devel] [PATCH v3 10/10] vnc: allow specifying a custom ACL object name

2016-03-22 Thread Eric Blake
On 03/10/2016 11:59 AM, Daniel P. Berrange wrote: > The VNC server has historically had support for ACLs to check > both the SASL username and the TLS x509 distinguished name. > The VNC server was responsible for creating the initial ACL, > and the client app was then responsible for populating it

[Qemu-devel] [PATCH v3 10/10] vnc: allow specifying a custom ACL object name

2016-03-10 Thread Daniel P. Berrange
The VNC server has historically had support for ACLs to check both the SASL username and the TLS x509 distinguished name. The VNC server was responsible for creating the initial ACL, and the client app was then responsible for populating it with rules using the HMP 'acl_add' command. This is not s