On 08/01/2016 10:14 AM, Daniel P. Berrange wrote:
> On Mon, Aug 01, 2016 at 10:00:05AM -0600, Jim Fehlig wrote:
>> On 08/01/2016 03:13 AM, Daniel P. Berrange wrote:
>>> On Fri, Jul 29, 2016 at 02:16:16PM -0600, Jim Fehlig wrote:
I've noticed the behavior described by this LSN with libvirt+Xen.
On Mon, Aug 01, 2016 at 10:00:05AM -0600, Jim Fehlig wrote:
> On 08/01/2016 03:13 AM, Daniel P. Berrange wrote:
> > On Fri, Jul 29, 2016 at 02:16:16PM -0600, Jim Fehlig wrote:
> >> I've noticed the behavior described by this LSN with libvirt+Xen. Config
> >> containing allows any client to
> >> co
On 08/01/2016 03:13 AM, Daniel P. Berrange wrote:
> On Fri, Jul 29, 2016 at 02:16:16PM -0600, Jim Fehlig wrote:
>> I've noticed the behavior described by this LSN with libvirt+Xen. Config
>> containing allows any client to
>> connect with no authentication check. I asked about this on the Xen secu
On Fri, Jul 29, 2016 at 02:16:16PM -0600, Jim Fehlig wrote:
> I've noticed the behavior described by this LSN with libvirt+Xen. Config
> containing allows any client to
> connect with no authentication check. I asked about this on the Xen security
> list and was told that "libxl interprets an empt
I've noticed the behavior described by this LSN with libvirt+Xen. Config
containing allows any client to
connect with no authentication check. I asked about this on the Xen security
list and was told that "libxl interprets an empty password in the caller's
configuration to mean that passwordless a
