[Spice-commits] Changes to 'spice.v36'

[Gerd Hoffmann]

New branch 'spice.v36' available with the following commits:
commit d1c3a125e407222e9abb289ce6569dd8794446c2
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Tue May 17 10:48:14 2011 +0200

    spice: require spice 0.6.0 or newer.
    
    This patch raises the minimum required spice version to 0.6.0 and drops
    a few ifdefs.
    
    0.6.0 is the first stable release with the current libspice-server API,
    there shouldn't be any 0.5.x development versions deployed any more.
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit e57df931feeb15c0984a5f2d6fb2de631e0f8925
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Tue May 17 10:40:43 2011 +0200

    qemu-config: comment spell fix
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 61c30ca6a7e963efc22afa6278895f108fc7daba
Author: Marc-André Lureau <marcandre.lureau at gmail.com>
Date:   Tue May 17 10:40:33 2011 +0200

    spice: add SASL support
    
    Turn on SASL support by appending "sasl" to the spice arguments, which
    requires that the client use SASL to authenticate with the spice.  The
    exact choice of authentication method used is controlled from the
    system / user's SASL configuration file for the 'qemu' service. This
    is typically found in /etc/sasl2/qemu.conf. If running QEMU as an
    unprivileged user, an environment variable SASL_CONF_PATH can be used
    to make it search alternate locations for the service config.  While
    some SASL auth methods can also provide data encryption (eg GSSAPI),
    it is recommended that SASL always be combined with the 'tls' and
    'x509' settings to enable use of SSL and server certificates. This
    ensures a data encryption preventing compromise of authentication
    credentials.
    
    It requires support from spice 0.8.1.
    
    [ kraxel: moved spell fix to separate commit ]
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit bd8f0d91dd0357f63e00f754b6bd157b0afc455e
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Mon May 16 09:28:58 2011 +0200

    qxl: add to the list of devices which disable the default vga
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 041180f7aef28191f12ca86a23185fdd715557f5
Author: Hans de Goede <hdegoede at redhat.com>
Date:   Sun Mar 27 16:43:54 2011 +0200

    spice: add option for disabling copy paste support
    
    Some people want to be able disable spice's guest <-> client copy paste support
    because of security considerations.
    
    [ kraxel: drop old-version error message ]

commit 5ea8d060e86edaacd00cb9ee1e10e0595441af19
Author: Hans de Goede <hdegoede at redhat.com>
Date:   Tue Mar 22 16:28:41 2011 +0100

    spice-qemu-char: Fix flow control in client -> guest direction
    
    In the old spice-vmc device we used to have:
    last_out = virtio_serial_write(&svc->port, p, MIN(len, VMC_MAX_HOST_WRITE));
    if (last_out > 0)
       ...
    
    Now in the chardev backend we have:
    last_out = MIN(len, VMC_MAX_HOST_WRITE);
    qemu_chr_read(scd->chr, p, last_out);
    if (last_out > 0) {
       ...
    
    Which causes us to no longer detect if the virtio port is not ready
    to receive data from us. chardev actually has a mechanism to detect this,
    but it requires a separate call to qemu_chr_can_read, before calling
    qemu_chr_read (which return void).
    
    This patch uses qemu_chr_can_read to fix the flow control from client to
    guest.
    
    Signed-off-by: Hans de Goede <hdegoede at redhat.com>