On Thu, Feb 21, 2013 at 05:20:06AM -0500, Marc-André Lureau wrote:
>
>
> - Mensaje original -
> > On Wed, Feb 20, 2013 at 05:34:07PM +0100, Marc-André Lureau wrote:
> > > In some cases, source and destinations may have different channel
> > > encryption. We need to swap tls state too duri
- Mensaje original -
> On Wed, Feb 20, 2013 at 05:34:07PM +0100, Marc-André Lureau wrote:
> > In some cases, source and destinations may have different channel
> > encryption. We need to swap tls state too during seamless
> > migration.
>
> Are we fine with going from encrypted to non-en
On Wed, Feb 20, 2013 at 05:34:07PM +0100, Marc-André Lureau wrote:
> In some cases, source and destinations may have different channel
> encryption. We need to swap tls state too during seamless migration.
Are we fine with going from encrypted to non-encrypted during migration?
Christophe
pgpef
ACK.
On 02/20/2013 05:34 PM, Marc-André Lureau wrote:
In some cases, source and destinations may have different channel
encryption. We need to swap tls state too during seamless migration.
https://bugzilla.redhat.com/show_bug.cgi?id=855870
---
gtk/spice-channel.c | 1 +
1 file changed, 1 ins
In some cases, source and destinations may have different channel
encryption. We need to swap tls state too during seamless migration.
https://bugzilla.redhat.com/show_bug.cgi?id=855870
---
gtk/spice-channel.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gtk/spice-channel.c b/gtk/spice-cha
