Re: [Qemu-devel] [PATCH v1 20/22] migration: support TLS encryption with TCP migration backend

2016-02-15 Thread Daniel P. Berrange
On Fri, Feb 12, 2016 at 05:25:31PM +, Daniel P. Berrange wrote: > On Fri, Feb 12, 2016 at 05:09:52PM +, Dr. David Alan Gilbert wrote: > > * Daniel P. Berrange (berra...@redhat.com) wrote: > > > This extends the TCP migration backend so that it can make use > > > of QIOChannelTLS to provide

Re: [Qemu-devel] [PATCH v1 20/22] migration: support TLS encryption with TCP migration backend

2016-02-12 Thread Dr. David Alan Gilbert
* Daniel P. Berrange (berra...@redhat.com) wrote: > This extends the TCP migration backend so that it can make use > of QIOChannelTLS to provide transparent TLS encryption. To > trigger enablement the URI on the incoming and outgoing sides > should have 'tls-creds=ID' appended, eg > >

Re: [Qemu-devel] [PATCH v1 20/22] migration: support TLS encryption with TCP migration backend

2016-02-12 Thread Daniel P. Berrange
On Fri, Feb 12, 2016 at 05:09:52PM +, Dr. David Alan Gilbert wrote: > * Daniel P. Berrange (berra...@redhat.com) wrote: > > This extends the TCP migration backend so that it can make use > > of QIOChannelTLS to provide transparent TLS encryption. To > > trigger enablement the URI on the

[Qemu-devel] [PATCH v1 20/22] migration: support TLS encryption with TCP migration backend

2016-01-12 Thread Daniel P. Berrange
This extends the TCP migration backend so that it can make use of QIOChannelTLS to provide transparent TLS encryption. To trigger enablement the URI on the incoming and outgoing sides should have 'tls-creds=ID' appended, eg tcp:$HOST:$PORT,tls-creds=ID where ID is the object identifier of a