Skip to content

feat: add rind crypto and TLS backends (fork CI run) - #1

Draft
kixelated wants to merge 2 commits into
mainfrom
crypto-rind
Draft

kixelated wants to merge 2 commits into
mainfrom
crypto-rind

Conversation

@kixelated

Copy link
Copy Markdown
Owner

Fork-internal draft so llrt's own CI runs the crypto-rind / tls-rind matrix entries before anything is proposed to awslabs/llrt. Not for merge here.

Tracked by moq-dev/rind#472.

  • refactor(crypto): providers hash the message they sign or verify, so a backend that only signs messages (rind signs and verifies only digests it computed) can implement the trait.
  • feat: crypto-rind provider, tls-rind via rind-rustls, CI matrix entries mirroring graviola, docs, RSA tests moved from 1024-bit to 2048-bit keys.

(Written by Claude Opus 5.5 with high)

🤖 Generated with Claude Code

kixelated and others added 2 commits November 7, 2026 01:27
A backend whose API signs messages, not digests, can then implement the
signature methods.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`crypto-rind` implements the crypto provider with rind, a pure-Rust
library whose arithmetic comes from s2n-bignum, libcrux, and
fiat-crypto, and `tls-rind` configures rustls with rind-rustls.

rind refuses what it does not support instead of falling back, so
`subtle.supports()` reports what it refuses: RSA key generation outside
2048 to 8192 bits or with an exponent other than 65537, and ECDSA with
SHA-1. The RSA tests now use 2048-bit keys, which every backend
generates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant