Skip to content

Key schedule security proofs -- fork#144

Closed
cmester0 wants to merge 10 commits into
cryspen:key-schedule-securityfrom
cmester0:key-schedule-security
Closed

Key schedule security proofs -- fork#144
cmester0 wants to merge 10 commits into
cryspen:key-schedule-securityfrom
cmester0:key-schedule-security

Conversation

@cmester0

@cmester0 cmester0 commented Mar 4, 2025

Copy link
Copy Markdown
Contributor

This PR addresses [...] described in issue #.

Type of change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation
  • Automation

Motivation and Context

Changes

Checklist

  • I have linked an issue to this PR
  • I have described the changes
  • I have read and understood the code of conduct, contribution guidelines, and contributor license agreement
  • I have added tests for all changes
  • I have tested that all tests pass locally and all checks pass
  • I have updated documentation if necessary

Fixes #

@cmester0
cmester0 requested a review from a team as a code owner March 4, 2025 16:44
@cmester0
cmester0 changed the base branch from main to key-schedule-security March 4, 2025 16:44
@cmester0
cmester0 marked this pull request as draft March 4, 2025 16:54
@cmester0 cmester0 changed the title Key schedule security proofs Key schedule security proofs -- fork Mar 18, 2025
@franziskuskiefer
franziskuskiefer removed the request for review from a team August 1, 2025 05:52
@jschneider-bensch

Copy link
Copy Markdown
Collaborator

Closing in favor of #148, which contains all these changes.

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