Simple Protocol for Independent Computing Environments

SPICEOriginal author(s)| Qumranet

|

Developer(s)| Red Hat
Stable release|

* spice-protocol: 0.14.4 / February 10, 2022; 4 years ago (2022-02-10)[1]
* spice: 0.15.1 / October 12, 2022; 3 years ago (2022-10-12)[2]
* spice-gtk: 0.41 / July 4, 2022; 4 years ago (2022-07-04)[3]

Written in| C, C++
Operating system| Linux, Windows, Android (Client)
Type| Server, client
License| GPL, LGPL and BSD
Website| spice-space.org
Internet protocol suite

Application layer

* BGP
* DHCP
* DNS
* FTP
* HTTP
* HTTPS
* IMAP
* LDAP
* MGCP
* MQTT
* NNTP
* NTP
* POP
* ONC/RPC
* RTP
* RTSP
* RIP
* SIP
* SMTP
* SNMP
* SSH
* Telnet
* TLS/SSL
* XMPP
* more...

Transport layer

* TCP
* UDP
* DCCP
* SCTP
* RSVP
* QUIC
* more...

Internet layer

* IP
* IPv4
* IPv6
* ICMP
* ICMPv6
* ECN
* IGMP
* IPsec
* more...

Link layer

* ARP
* NDP
* OSPF
* Tunnels
* L2TP
* PPP
* MAC
* Ethernet
* Wi-Fi
* DSL
* ISDN
* FDDI

* more...

* v
* t
* e

In computing, SPICE (the Simple Protocol for Independent Computing Environments) is a remote-display system built for virtual environments which allows users to view a computing "desktop" environment – not only on its computer-server machine, but also from anywhere on the Internet – using a wide variety of machine architectures.

Qumranet originally developed SPICE using a closed-source codebase in 2007. Red Hat, Inc acquired Qumranet in 2008, and in December 2009 released the code under an open-source license and made the protocol an open standard.[4][5]

## Contents

* 1 Security
* 2 Implementations
* 3 Applications
* 4 See also
* 5 References
* 6 External links

## Security

A SPICE client connection to a remote desktop server consists of multiple data channels, each of which is run over a separate TCP or UNIX socket connection. A data channel can be designated to operate in either clear-text, or TLS modes, allowing the administrator to trade off the security level vs performance. The TLS mode provides strong encryption of all traffic transmitted on the data channel.

In addition to encryption, the SPICE protocol allows for a choice of authentication schemes. The original SPICE protocol defined a ticket based authentication scheme using a shared secret. The server would generate an RSA public/private keypair and send its public key to the client. The client would encrypt the ticket (password) with the public key and send the result back to the server, which would decrypt and verify the ticket. The current SPICE protocol also allows for use of the SASL authentication protocol, thus enabling support for a wide range of admin configurable authentication mechanisms, in particular Kerberos.

## Implementations

While only one server implementation exists, several programmers have developed new implementations of the SPICE client-side since the open-sourcing of SPICE.

spice-protocol
The spice-protocol module[6] defines the SPICE wire protocol formats. This is made available under the BSD license, and is portable across the Linux and Windows platforms.
spice
The spice module[7] provides the reference implementation for the server side of the SPICE protocol. The server is provided as a dynamic library which can be linked to any application wishing to expose a SPICE server. As of 2013[update], QEMU uses this to provide a SPICE interface for virtual machines. The spice codebase is available under the LGPL v2+ license.
A client part of the spice codebase named spicec was removed in December 2014.
spice-gtk
The spice-gtk module[8] implements a SPICE client using the GObject type system and the GTK widget toolkit. This comprises a low-level library, spice-client-glib, which implements the client protocol code, and a high-level set of widgets which provide a graphical client capability using GTK. This is made available under the LGPLv2+ license, and is portable across the Linux, OS X and Windows platforms.
spice-html5
The spice-html5 module[9] implements a SPICE client that uses JavaScript and is intended to run inside a web browser supporting HTML5. While it implements the SPICE protocol, it cannot talk directly to a regular SPICE server. It must connect to the server indirectly via WebSocket proxy.[10] This is made available under a combination of the GPLv3+ and LGPLv3+ licenses.

## Applications

The SPICE protocol originated to provide improved remote desktop capabilities in a fork of the KVM codebase.

QEMU/KVM
The QEMU maintainers merged support for providing SPICE remote desktop capabilities for all QEMU virtual machines in March 2010. The QEMU binary links to the spice-server library to provide this capability and implements the QXL paravirtualized framebuffer device to enable the guest OS to take advantage of the performance benefits the SPICE protocol offers. The guest OS may also use a regular VGA card, albeit with degraded performance as compared to QXL.[11]
Xspice
The X.Org Server driver for the QXL framebuffer device includes a wrapper script,[12] which makes it possible to launch a Xorg server whose display is exported via the SPICE protocol. This enables use of SPICE in a remote desktop environment, without requiring QEMU/KVM virtualization.
virt-viewer
The `virt-viewer` program uses the spice-gtk client library to connect to virtual machines using SPICE, as an alternative to its previous support for VNC.
oVirt
SPICE is integrated into oVirt private cloud management software, allowing users to connect to virtual machines through SPICE.

## See also

* Red Hat Virtualization
* HP Remote Graphics Software

## References

1. ↑ "spice 0.14.4 release". gitlab.freedesktop.org. https://gitlab.freedesktop.org/spice/spice-protocol/-/releases/v0.14.4.
2. ↑ "spice 0.15.1 release". gitlab.freedesktop.org. https://gitlab.freedesktop.org/spice/spice/-/releases/v0.15.1.
3. ↑ "spice-gtk 0.41 release". gitlab.freedesktop.org. https://gitlab.freedesktop.org/spice/spice-gtk/-/releases/v0.41.
4. ↑ "Red Hat open-sources SPICE". Red Hat. 9 December 2009. https://www.redhat.com/about/news/press-archive/2009/12/spice-os.
5. ↑ "Project website". spice-space.org. https://www.spice-space.org/.
6. ↑ "spice-protocol GIT repository". cgit.freedesktop.org. http://cgit.freedesktop.org/spice/spice-protocol/tree/spice.
7. ↑ "spice/spice". https://cgit.freedesktop.org/spice/spice/.
8. ↑ "spice-gtk GIT repository". cgit.freedesktop.org. 2013-10-10. http://cgit.freedesktop.org/spice/spice-gtk/.
9. ↑ "spice-html5 GIT repository". cgit.freedesktop.org. http://cgit.freedesktop.org/spice/spice-html5/.
10. ↑ on GitHub
11. ↑ "QEMU/KVM Virtual Machines". https://pve.proxmox.com/pve-docs-7/chapter-qm.html.
12. ↑ "XSpice README". cgit.freedesktop.org. http://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/tree/README.xspice.

## External links

* Official website
* SPICE protocol

* v
* t
* e

Red Hat

Major products|

* Red Hat Enterprise Linux
* Directory Server
* Cluster Suite
* GFS2
* WildFly (JBoss)
* Fedora
* Virtual Machine Manager
* Anaconda
* ABRT
* Ceph
* GlusterFS
* yum
* RPM
* Satellite
* CloudForms
* SPICE
* Ansible
* CentOS

Services|

* RHN
* OpenShift

Projects|

* Fedora Project
* FreeOTP
* Spacewalk

Defunct|

* Red Hat Linux
* Red Hat Database
* Fedora Legacy
* Mugshot

Important people|

* Jim Whitehurst
* Matthew Szulik
* Bob Young
* Marc Ewing
* Michael Tiemann

Mergers and acquisitions|

* Mergers and acquisitions
* C2Net
* Cygnus Solutions
* Inktank Storage
* JBoss
* MetaMatrix
* Qumranet

Related|

* Red Hat Certification Program
* Red Hat Enterprise Linux derivatives

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Simple Protocol for Independent Computing Environments. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Simple_Protocol_for_Independent_Computing_Environments&oldid=4230679"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template