Skip to content

Conversation

@emostov
Copy link
Contributor

@emostov emostov commented Jan 21, 2026

Summary & Motivation (Problem vs. Solution)

Spec updates for versioned quorum key secrets

Builds on #598
#611 builds on this

@emostov emostov requested a review from a team as a code owner January 21, 2026 00:34
@emostov emostov force-pushed the zeke/key-spec-2 branch 2 times, most recently from 825d505 to 7cd8ff0 Compare January 21, 2026 02:00
@emostov emostov changed the title Add P256 secret format specification 2/3 Add QOS Key V1 secret format specification 2/3 Jan 21, 2026
Base automatically changed from zeke/key-spec to main January 24, 2026 19:05
@emostov emostov force-pushed the zeke/key-spec-2 branch 2 times, most recently from 4003203 to 05d5a9d Compare January 25, 2026 20:15
```
┌─────────┬───────────────────┬───────────────────┬──────────────--------┐
│ version │ hpke_public │ sign_public │ aes_gcm_256_key_id │
│ 1 byte │ 65 bytes (SEC1) │ 65 bytes (SEC1) │ 32 bytes │
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was debating making these compressed for readability, but it introduced a decompression bug vector for clients and we can use the fingerprint for anytime readability is an issue

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.

2 participants