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

Hmac separate #16

Merged
merged 1 commit into from
Mar 5, 2024
Merged

Hmac separate #16

merged 1 commit into from
Mar 5, 2024

Conversation

sosthene-nitrokey
Copy link
Contributor

@sosthene-nitrokey sosthene-nitrokey commented Mar 4, 2024

Built on top of #15

This PR stops depending on trussed-staging for the never-merged HMACSHA256P256 extension and uses a custom backend instead (https://github.com/Nitrokey/trussed-hmacsha256p256)

@robin-nitrokey
Copy link
Member

As the extension is only intended to be used with this crate as a workaround, we could also put it directly into this repository. That would probably be easier to maintain.

@sosthene-nitrokey
Copy link
Contributor Author

Right, that's probably a better idea indeed.

@sosthene-nitrokey sosthene-nitrokey force-pushed the hmac-separate branch 3 times, most recently from f1b25ef to 183524b Compare March 4, 2024 14:22
@sosthene-nitrokey
Copy link
Contributor Author

I moved the backend here.

Copy link
Member

@robin-nitrokey robin-nitrokey left a comment

Choose a reason for hiding this comment

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

LGTM, just some outdated lines in the Cargo.toml.

Cargo.toml Outdated Show resolved Hide resolved
Cargo.toml Outdated Show resolved Hide resolved
Cargo.toml Outdated Show resolved Hide resolved
@sosthene-nitrokey
Copy link
Contributor Author

Should we tag with this PR or with main also?

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.

3 participants