The repository or configuration that created this release differ from a previous release. View details.
This release is a pre-release and may not be stable for production use.
kerbside-proxy
The Kerbside SPICE proxy: an inspection-first TLS relay between SPICE
clients and hypervisors, authorised via the Kerbside gRPC control
service. It is the Rust replacement for the original Python SPICE proxy
in kerbside.
This package ships a single compiled binary, kerbside-proxy. It is
published to PyPI as a separate package from the pure-Python kerbside
package and is an exact-version dependency of it, so pip install kerbside installs a matching proxy and puts kerbside-proxy on PATH.
The kerbside daemon supervises the binary as a child process; you do
not normally run kerbside-proxy directly.
Building from source
The crate lives at rust/kerbside-proxy/ in the kerbside repository.
Its build.rs compiles the gRPC contract from
../../kerbside/rpc/kerbside.proto, so a build must run with the
repository root available (see the crate Makefile, which wraps the
build in Docker and mounts the repo root). To build a wheel:
pip install maturin
maturin build --release # run from rust/kerbside-proxy/
See How the binary gets there:
packaging
for the packaging and release design, Packaging and
release for what
matters while developing, and ../../RELEASE-SETUP.md for the release
infrastructure setup (PyPI trusted publishing and signing).
Licence
Apache-2.0. See the LICENSE file at the repository root.
1 maintainer
Metadata
1 maintainer
Release files for kerbside-proxy 0.8.1.dev10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kerbside_proxy-0.8.1.dev10-py3-none-manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64 | Details |
| kerbside_proxy-0.8.1.dev10-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details |
Total release size: 5.8 MB
Release files / kerbside_proxy-0.8.1.dev10-py3-none-manylinux_2_28_x86_64.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | kerbside_proxy-0.8.1.dev10-py3-none-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
80347b5210aef69d1bba91342c95f157a09332b921e769fbf603ef8b9c545622
|
|
BLAKE2b-256 checksum How to use checksums |
e7c073f4afe5e86a9dca3a1a6b4cb1714057d2a42ae74ee3717984c68ce38c80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / kerbside_proxy-0.8.1.dev10-py3-none-manylinux_2_28_aarch64.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | kerbside_proxy-0.8.1.dev10-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
19307dd2a9aeb3253b41244a120ad781f16f8c558124d2a34640b2c7dddc9c76
|
|
BLAKE2b-256 checksum How to use checksums |
80c0f05bf28994abd4259ee8a47a1ed7c79485c178ad2f9169b716cc38f725f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for kerbside-proxy 0.8.1.dev10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Change of provenance
The configuration that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Configuration
- Removed 0.8.0 release.yml
- Added 0.8.1.dev10 dev-proxy-wheel.yml
Attestation for kerbside_proxy-0.8.1.dev10-py3-none-manylinux_2_28_x86_64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
