Skip to content

Releases

qkd-stub v0.4.0

qkd-stub v0.4.0 Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 09 Oct 11:59
v0.4.0
22eb1d1

Standalone Windows provisioning

The first published release of qkd-stub includes a signed, standalone Windows
x64 executable. No OpenSSL, Python, Rust, or source checkout is required to
configure and test endpoints. The C runtime is statically linked.

Start here

Download qkd-stub.exe below. demo init creates a qkd-demo directory in the current working directory
(change it with --dir) and refuses to run if it already exists. It holds test
credentials, including private keys and the shared PSK, so run it from a private
location. configure likewise creates qkd-stub-data in the working directory.

In PowerShell:

.\qkd-stub.exe demo init
.\qkd-stub.exe --config qkd-demo/a.toml serve

Run .\qkd-stub.exe --config qkd-demo/b.toml serve in a second terminal, then
.\qkd-stub.exe demo verify in a third. Verification checks matching keys in
both directions over certificate-authenticated HTTPS. Stop with Ctrl-C.

For device-style provisioning with your organization's CA:

.\qkd-stub.exe configure

The wizard saves configuration, generates a local private key and CSR, and can
resume after your CA signs the request. check reports missing or invalid setup;
serve starts the saved configuration.

Included

  • Scriptable CSR generation and signed-certificate installation, including key
    matching and supplied-chain validation. Renewal reuses the existing key.
  • Client CA trust management, certificate inspection, PSK generation/import,
    and SAE registry commands.
  • Atomic file writes, overwrite protection for PSKs/CSR outputs, and private
    data directories (Windows owner/SYSTEM ACLs; Unix 0700/0600).
  • Executable-only demo generation and mTLS round-trip verification.
  • Existing flag-only server invocation and --inspect-cert remain supported.
  • Linux and native Windows CI, including provisioning and real HTTPS tests.

This is a software QKD API simulator. Matching keys are derived from a shared
PSK; it does not implement physical QKD or provide information-theoretic security
or forward secrecy. CSR private keys are software-stored, not hardware-backed.

Setup guide ·
Windows guide ·
Security assumptions

The executable is Authenticode-signed and timestamped. qkd-stub.exe.sha256
contains the SHA-256 checksum of the signed executable.

Assets 4
Loading