Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Towards crypto & method agility: API updates, new buffer, new credential struct #284

Merged
merged 31 commits into from
Aug 2, 2024

Conversation

geonnave
Copy link
Collaborator

@geonnave geonnave commented Jun 4, 2024

Still very early stage.

@geonnave
Copy link
Collaborator Author

So far this PR includes:

  • updates in the API
    • support for setting different methods and crypto suites (even though only one is supported for now)
    • a separate function for setting identity (private key + credential)
  • a new buffer struct that is parameterizeable via const generics
  • a new credential struct that supports CCS's that hold asymmetric and symmetric keys
  • improved handling of ID_CRED_x, including support for kids longer than 1 byte

Next steps are to update the examples and C/Python wrappers, then merge on main and continue the agility work on a new PR.

@geonnave geonnave marked this pull request as ready for review July 31, 2024 09:19
@geonnave geonnave changed the title Add crypto & method agility Towards crypto & method agility: API updates, new buffer, new credential strucr Aug 2, 2024
@geonnave geonnave changed the title Towards crypto & method agility: API updates, new buffer, new credential strucr Towards crypto & method agility: API updates, new buffer, new credential struct Aug 2, 2024
@geonnave geonnave requested a review from malishav August 2, 2024 08:52
@geonnave
Copy link
Collaborator Author

geonnave commented Aug 2, 2024

@malishav just asked for a review, mostly interested in an ack about the changeset (in comment above).

One point I have is that the Symmetric key type would not need to live in main, but not keeping it in main means having to keep another version of the code just for that, which in my opinion is not worth it.

@geonnave
Copy link
Collaborator Author

geonnave commented Aug 2, 2024

Also, regarding actual crypto agility, I will leave for another PR since this one is already big enough...

Copy link
Contributor

@malishav malishav left a comment

Choose a reason for hiding this comment

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

I went briefly over the PR, it is massive, congrats on pulling this off! I am happy if you merge this!

@geonnave geonnave merged commit b82451d into openwsn-berkeley:main Aug 2, 2024
31 checks passed
@geonnave geonnave deleted the crypto-method-agility branch August 2, 2024 11:36
geonnave added a commit to geonnave/lakers that referenced this pull request Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants