On Fri, Feb 16, 2018 at 11:13:06AM +0100, marcandre.lureau@xxxxxxxxxx wrote: > From: Marc-André Lureau <marcandre.lureau@xxxxxxxxxx> > > spice:// has a weird scheme encoding, where it can accept both plain > and tls ports with URI query parameters. However, it's not very > convenient nor very common to use (who really want to mix plain & tls > channels?). Is it worth formally deprecating the mixing of plain & tls on a per channel basis in QEMU ? The idea that you can be secure, and yet still have some channels plain text is really dubious and promotes dangerous practice to users. > > Instead, let's introduce the more readable form spice+tls://host:port > This form will not accept 'port' or 'tls-port' query string parameter. > > Signed-off-by: Marc-André Lureau <marcandre.lureau@xxxxxxxxxx> 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 :| _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel