-
Notifications
You must be signed in to change notification settings - Fork 10
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
refactor!: Move crypto operations into a trait. #127
refactor!: Move crypto operations into a trait. #127
Conversation
b95cea2
to
95ddb6d
Compare
There are still quite a few instances of default_crypto() around that eventually should be relegated to tests and example only. The most prominent leftovers are in lib/src/lib.rs that is not generic yet -- but that is probably easier to do once the C API is in the freezer. |
95ddb6d
to
b957e68
Compare
Ready from my PoV -- please review. This would then be a sensible base for the big typestating bout. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, just left a minor comment below.
Just to note, I am having trouble with installing and running [hax] on my computer, to run against this PR. I am on it, but the build takes time (and fails after a lot o fime). Once I solve that and the fstar generation works, I would be happy to merge this PR. |
I was finally able to install and run There are still some errors but they were already present at the previous implementation, i.e., the only complaints are due to the recursive order of some elements in the Details
|
@malishav I am ok with merging this. Do you wish to provide any input? |
This allows pushing back the edhoc-crypto ("the default implementation that is selected statically, making all implementations possible dependencies") into the dev-dependencies. Follow-up-for: openwsn-berkeley#127
This allows pushing back the edhoc-crypto ("the default implementation that is selected statically, making all implementations possible dependencies") into the dev-dependencies. The crypto-* features are removed from edhoc-rs; testing depends on edhoc-crypto being pulled in in parallel to the test, and a feature selected on that. Follow-up-for: openwsn-berkeley#127
This is a reroll of #103, which has become quite inconvenient to merge.
As a practical difference, the functions that used to be moved into a CryptoExt trait now just take a crypto first argument -- not much of an ergonomics setback, but easier to understand code.