[PR #527] Add krypteia to no-std WIP crates #12918

New Issue

GiteaMirror · 2026-07-14T03:27:54-05:00

GiteaMirror commented

2026-07-14 03:27:54 -05:00

📋 Pull Request Information

Original PR: https://github.com/rust-embedded/awesome-embedded-rust/pull/527
Author: @cslashm
Created: 6/26/2026
Status: 🔄 Open

Base: master ← Head: add-krypteia

📝 Commits (1)

5517d49 Add krypteia to no-std WIP crates

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

This adds krypteia, a pure-Rust no_std cryptography workspace, to the no-std crates section.

What it is. Post-quantum (FIPS 203/204/205 — ML-KEM, ML-DSA, SLH-DSA) and classical (RSA, ECC, EdDSA, X25519/X448, AES, ChaCha20-Poly1305, hashes, MACs) primitives. Embedded is a first-class design goal, not an afterthought: no_std, zero runtime dependencies (std/core/alloc only), explicit RAM/stack budgets, written constant-time from the first commit.

Honest maturity status — why I'm sharing it at 0.1 rather than later. It builds and runs no_std for the embedded targets (thumbv6m / thumbv7em Cortex-M, riscv32imc / imac), and the test + side-channel suites pass — but so far validation is under emulation (qemu-user + bare-metal qemu-system), and it's fully functional on host. It has not yet run on physical silicon: the first hardware bring-up (an ESP32-C3 / RISC-V sample) is on the near-term roadmap. Side-channel countermeasures are implemented and host-verified (ctgrind / dudect); on-target power/EM measurement is future work.

So it's a 0.1, but deliberately mature enough to test and to invite early feedback. I'd rather get architecture / API / requirements input from the embedded community now, while the design can still move, than once it's set in stone — remarks on targets, memory model, feature gating, ergonomics are all very welcome.

On AI assistance. Marked 🤖 per the list convention: part of the work is AI-assisted, tracked openly via Co-Authored-By git trailers. Correctness and constant-timeness are decided by tools (NIST ACVP / Wycheproof, ctgrind, dudect), not by the model — not vibe-coded.

Pre-1.0, unaudited, structured toward a lab-class evaluation.

Docs: https://krypteia-rs.dev/
Source: https://codeberg.org/cslashm/krypteia

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/rust-embedded/awesome-embedded-rust/pull/527 **Author:** [@cslashm](https://github.com/cslashm) **Created:** 6/26/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `add-krypteia` --- ### 📝 Commits (1) - [`5517d49`](https://github.com/rust-embedded/awesome-embedded-rust/commit/5517d49dff7c93bb52f29dac88b2221d6ab31d45) Add krypteia to no-std WIP crates ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description This adds krypteia, a pure-Rust no_std cryptography workspace, to the no-std crates section. What it is. Post-quantum (FIPS 203/204/205 — ML-KEM, ML-DSA, SLH-DSA) and classical (RSA, ECC, EdDSA, X25519/X448, AES, ChaCha20-Poly1305, hashes, MACs) primitives. Embedded is a first-class design goal, not an afterthought: no_std, zero runtime dependencies (std/core/alloc only), explicit RAM/stack budgets, written constant-time from the first commit. Honest maturity status — why I'm sharing it at 0.1 rather than later. It builds and runs no_std for the embedded targets (thumbv6m / thumbv7em Cortex-M, riscv32imc / imac), and the test + side-channel suites pass — but so far validation is under emulation (qemu-user + bare-metal qemu-system), and it's fully functional on host. It has not yet run on physical silicon: the first hardware bring-up (an ESP32-C3 / RISC-V sample) is on the near-term roadmap. Side-channel countermeasures are implemented and host-verified (ctgrind / dudect); on-target power/EM measurement is future work. So it's a 0.1, but deliberately mature enough to test and to invite early feedback. I'd rather get architecture / API / requirements input from the embedded community now, while the design can still move, than once it's set in stone — remarks on targets, memory model, feature gating, ergonomics are all very welcome. On AI assistance. Marked 🤖 per the list convention: part of the work is AI-assisted, tracked openly via Co-Authored-By git trailers. Correctness and constant-timeness are decided by tools (NIST ACVP / Wycheproof, ctgrind, dudect), not by the model — not vibe-coded. Pre-1.0, unaudited, structured toward a lab-class evaluation. Docs: https://krypteia-rs.dev/ Source: https://codeberg.org/cslashm/krypteia --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-07-14 03:27:54 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-embedded-rust#12918