
Nexus-Q Core PQC Open Source 4.1.0
A post-quantum cryptographic security engine. It is a library first: a Rust core that does all the cryptography, with a command line, an HTTP server and language SDKs layered on top. It is meant to be embedded in applic…
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
A post-quantum cryptographic security engine. It is a library first: a Rust core that does all the cryptography, with a command line, an HTTP server and language SDKs layered on top. It is meant to be embedded in applications and servers that need to protect secrets for the long term.
Data
Authenticated encryption of files and streams, with envelope encryption (format F-02) so payloads are protected under a key that is itself protected.
Keys
The full key lifecycle: generation, rotation, revocation and destruction, stored in an encrypted vault (format F-01) with atomic writes.
Identities
Digital signatures, signature verification, identity rotation and revocation, and signed verifiable credentials.
Large quantum computers would break the public-key schemes in wide use today (RSA, elliptic curves), and data recorded now could be decrypted later. NEXUS-Q uses the NIST-standardized lattice algorithms ML-KEM and ML-DSA, and pairs the key exchange with classical X25519 as a hybrid.
We do not invent cryptography. Every primitive is a standardized algorithm implemented by a maintained library. Deviations need a written architecture decision record. The project also states plainly that it does not claim every dependency has been independently audited.
Every operation goes through the same building blocks. Policy decides who may act, the vault guards the keys, and security-relevant events are written to an audit log that detects tampering.
A password goes through Argon2id to unlock the encrypted vault. The vault holds keys at rest and is written atomically.
Generate, rotate, revoke and destroy keys. Secrets are zeroized in memory when they are no longer needed.
Hybrid ML-KEM + X25519 for key exchange, AES-256-GCM or ChaCha20-Poly1305 for data, Ed25519, ML-DSA-65 or SLH-DSA for signatures.
A deny-by-default policy engine decides which actions are allowed before they happen.
An HMAC-authenticated audit log with rollback anchoring makes tampering and truncation detectable.
The core is a Rust library. The CLI, the server and the SDKs are thin layers on top and contain no cryptography of their own.
Provider traits exist for software, TPM, HSM, Secure Element and RISC-V. Hardware isolation is only claimed when a provider is implemented and tested. The default software backend does not provide it.
The threat model and the cryptographic rules were written before the code, and they are part of the repository.
A Cargo workspace of five Rust crates, plus bindings for other languages and a reproducible benchmark arena.
Linux x86_64 and aarch64, Android/Termux aarch64, and RISC-V (riscv64gc) with a verified build.
Rust 1.85 or newer (edition 2024) and Git. SDK toolchains are only needed for the binding you build.
Encrypted vault, envelope format, backup bundles and a storage database, all with documented formats.
Request IDs, aggregate metrics, health and readiness probes. Secrets are kept out of logs.
The core is only allowed to use six families of primitives. Anything outside them, such as raw RSA or custom MACs, is forbidden by the project's own rules.
Planned algorithms are never described as available until they are implemented and tested. The reference document is docs/CRYPTOGRAPHY.md.
NEXUS-Q is not a performance leader, and the project says so. The numbers below come from the repository's own benchmark records. They are the baseline the next versions are measured against.
V1, V2 and V3 are engineering version lines, not certifications. A GitHub release here does not mean an audit, a certification, production readiness or publication to a package registry.
The frozen engineering baseline: crypto core, vault, keys, identities, policy, audit log, CLI, server and SDKs. Its Arena result showed NEXUS-Q slower than the fastest implementations, which became the main target.
Correctness, interoperability, security fuzzing, backend strategy and release gates. The final record claims no performance improvement over V1, and the performance question stayed open.
Hardened implementation, reproducible Arena, corrected benchmark sampling and retained evidence archive with SHA-256 manifest.
Stable line release: the native backend passed the 1.5× median-and-p95 gates and PR #55 wires it into nexusq-core behind an explicitly opt-in feature. Default builds, the CLI and SDKs still use RustCrypto; the native path is opt-in only.
Cryptographic software earns trust slowly. This is the project's own statement of its current assurance level.
Found a vulnerability? Report it privately through GitHub Security Advisories, not a public issue. See SECURITY.md.
You need Rust 1.85 or newer. Linux and Android/Termux are the environments exercised most.
clone and build the workspace
git clone https://github.com/lecodev-26/nexus-q cd nexus-q cargo build --workspace --release
2 · Create a vault
Copy./target/release/nexusq vault create ./example.nqv ./target/release/nexusq vault status ./example.nqv ./target/release/nexusq health
3 · Generate a key
Copy./target/release/nexusq key generate ./example.nqv
--algorithm ed25519 --purpose sign
--password-file ./password.txt
./target/release/nexusq key list ./example.nqv
4 · Encrypt and decrypt data
Copy./target/release/nexusq data encrypt ./example.nqv
--key-id <key-id> ./secret.txt
./target/release/nexusq data decrypt ./example.nqv
./secret.txt.nqx ./secret.out
Prefer --password-file over typing a password on the command line, and never commit that file. The full command list is in the CLI guide. Server setup is in docs/SERVER.md.
NEXUS-Q is built in the open and is still young. The most useful help right now is scrutiny: more eyes, more hardware and more honest measurements. Some of these need no cryptography background.
Reproduce the benchmark numbers on your own CPU and share what you find in an issue. Differences between machines affect reproducibility; treat local results as observations, not official gate evidence. Start with arena/README.md.
Read the threat model and the security model, and tell us what is missing or wrong. A gap in the reasoning is worth more than praise.
Build the workspace and run the tests on Linux, Android/Termux or RISC-V, and report anything that fails or behaves differently.
The native backend is experimental and opt-in: PR #55 wires it into nexusq-core behind an explicit feature flag, but the default build, the CLI and the SDKs still use RustCrypto, and the feature is not enabled by default anywhere. Independent external audit is still open.
Found a vulnerability? Please report it privately through GitHub Security Advisories, not in a public issue. See SECURITY.md.
Everything below lives in the repository. Start with the user guide, then go as deep as you need.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。