q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
THE JOURNEY THROUGH TIME

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Shirley Chisholm — Unbought and Unbossed

In 1968 Shirley Chisholm became the first Black woman elected to the United States Congress. In 1972 she launched a campaign for the Democratic presidential nomination, breaking another political barrier.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

Simple Protocol for Independent Computing Environments

SPICE
Original authorQumranet
DeveloperRed 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; 4 years ago (2022-10-12)[2]
  • spice-gtk: 0.41 / July 4, 2022; 4 years ago (2022-07-04)[3]
Written inC, C++
Operating systemLinux, Windows, Android (Client)
TypeServer, client
LicenseGPL, LGPL and BSD
Websitespice-space.org

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]

Security

[edit]

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

[edit]

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, 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

[edit]

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

[edit]

References

[edit]
  1. ^ "spice 0.14.4 release". gitlab.freedesktop.org. Retrieved 2022-10-24.
  2. ^ "spice 0.15.1 release". gitlab.freedesktop.org. Retrieved 2022-10-24.
  3. ^ "spice-gtk 0.41 release". gitlab.freedesktop.org. Retrieved 2022-10-24.
  4. ^ "Red Hat open-sources SPICE". Red Hat. 9 December 2009. Retrieved 2013-10-25.
  5. ^ "Project website". spice-space.org. Retrieved 2019-12-25.
  6. ^ "spice-protocol GIT repository". cgit.freedesktop.org. Retrieved 2013-10-25.
  7. ^ "spice/spice". cgit.freedesktop.org. Retrieved 2023-01-05.
  8. ^ "spice-gtk GIT repository". cgit.freedesktop.org. 2013-10-10. Retrieved 2013-10-25.
  9. ^ "spice-html5 GIT repository". cgit.freedesktop.org. Retrieved 2013-10-25.
  10. ^ websockify on GitHub
  11. ^ "QEMU/KVM Virtual Machines". pve.proxmox.com. Retrieved 2023-09-18.
  12. ^ "XSpice README". cgit.freedesktop.org. Retrieved 2013-10-25.
[edit]

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

No preview image
Wikipedia

Simple Protocol for Independent Computing Environments

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.

MORE →
No preview image
Wikipedia

Post Office Protocol

In computing, the Post Office Protocol (POP) is an application-layer Internet standard protocol used by e-mail clients to retrieve e-mail from a mail server. Today, POP version 3 (POP3) is the most commonly used version. Together with IMAP, it is one of the most common protocols for email retrieval.

MORE →
No preview image
Wikipedia

SSH File Transfer Protocol

In computing, the SSH File Transfer Protocol, also known as Secure File Transfer Protocol (SFTP), is a network protocol that provides file access, file transfer, and file management over any reliable data stream. It was designed by the Internet Engineering Task Force (IETF) as an extension of the Secure Shell protocol (SSH) version 2.0 to provide secure file transfer capabilities, and is seen as a replacement of File Transfer Protocol (FTP) due to superior security. The IETF Internet Draft states that, even though this protocol is described in the context of the SSH-2 protocol, it could be used in a number of different applications, such as secure file transfer over Transport Layer Security (TLS) and transfer of management information in VPN applications. This protocol assumes that it is run over a secure channel, such as SSH, that the server has already authenticated the client, and that the identity of the client user is available to the protocol. The official URI scheme is sftp.

MORE →
No preview image
Wikipedia

IPsec

In computing, Internet Protocol Security (IPsec) is a secure network protocol suite that authenticates and encrypts packets of data to provide secure encrypted communication between two computers over an Internet Protocol network. It is used in virtual private networks (VPNs). IPsec includes protocols for establishing mutual authentication between agents at the beginning of a session and negotiation of cryptographic keys to use during the session. IPsec can protect data flows between a pair of hosts (host-to-host), between a pair of security gateways (network-to-network), or between a security gateway and a host (network-to-host). IPsec uses cryptographic security services to protect communications over Internet Protocol (IP) networks. It supports network-level peer authentication, data origin authentication, data integrity, data confidentiality (encryption), and protection from replay attacks.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

Which heavyweight champion was known as the “Brown Bomber”?

Joe Louis.