Skip to main content

Nubwen Rust Shell

Windows x64 command-line tools for source-integrated Rust/C/C++ protection builds. The wheel contains the verified native CLI, static runtime, C header and CMake helper. It does not run an installer or download executables during pip install.

This is a development release. Commercial acceptance, Authenticode signing and VMProtect/AI-resistance equivalence are not established. Existing licensing and protection configuration are required; this is not an arbitrary EXE repacker.

# Install from public PyPI; no private registry credentials are required.
python -m pip install --no-deps nubwen-rust-shell==0.2.0
rust-shell --version
rust-shell-package --home

Run in an x64 Visual Studio developer environment with the Windows SDK, PowerShell 7, pinned Rust 1.97.1 and LLVM 22.1.6:

# Explicit optional setup; this downloads SHA-256-pinned LLVM beside the package.
rust-shell-package --setup-toolchain --install-rust
$env:RUSTUP_TOOLCHAIN = '1.97.1'
rust-shell doctor
rust-shell cargo-build --config rust-shell.toml --manifest-path Cargo.toml --bin app --static-crt

An existing LLVM cache can be selected through RSH_LLVM_BIN instead. The package uses the native CLI's existing version checks and leaves the caller's working directory and arguments intact. Every command verifies the installed payload's hashes before execution and returns the native program's exit code.

Rust applications must already integrate the matching Rust SDK and protection markers. The Rust SDK/VM source workspace is deliberately not distributed in this wheel; existing product repositories can retain their authorized SDK copy. rust-shell-package prints JSON paths for the native CLI, server, static runtime, C header, CMake helper and original release manifest. CMake and long-running server processes should use those native executable paths directly.

For a private registry, use only its --index-url, not --extra-index-url, and install a fixed version with --require-hashes. Supply authentication through the runner's protected pip/netrc/keyring configuration, never credentials in a committed URL. Private keys, content keys, licensing caches and build reports must not be included in release artifacts.

Version 0.2.0 requires a separate integrity signing key, an embedded integrity_public_key, signed .rsh-integrity.json sidecars beside final EXE/DLLs, and host checkpoints before publishing results or committing side effects. CMake targets must call rust_shell_finalize; see the included docs/integrity.md. Existing products must rebuild with the matching SDK. Offline licensing is retained.

Synchronous whole-image checks have substantial overhead for hot protected functions. The local synthetic candidate measured about 15.6 ms p50 for one protected call per request and 512.6 ms for 100 calls with one client. This is not a product performance promise. Simultaneous wrapper/checkpoint patches and changes restored between checkpoints remain outside the demonstrated refusal cases.

Metadata

Release files for nubwen-rust-shell 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for nubwen-rust-shell 0.2.0
File Interpreter ABI Platform Actions
nubwen_rust_shell-0.2.0-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details for nubwen_rust_shell-0.2.0-py3-none-win_amd64.whl

Release files / nubwen_rust_shell-0.2.0-py3-none-win_amd64.whl

Download URL nubwen_rust_shell-0.2.0-py3-none-win_amd64.whl
Size 9.2 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
b83daf5cfb677cbb084aef597e961a83f84ada7a49348a0a30e54f0645444b2a
BLAKE2b-256 checksum
How to use checksums
917b3e6a2825a78b275c6b8b331e1155a9d44557d536ac6e9aa024323974e363
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.9

Security for nubwen-rust-shell 0.2.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page