-
Notifications
You must be signed in to change notification settings - Fork 211
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
Add unwrapKey to typescript interface #5792
Add unwrapKey to typescript interface #5792
Conversation
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
beejones/add-unwrap-in-typescript@78304 aka 20231102.11 vs main ewma over 20 builds from 77958 to 78284 Click to see tablemain
beejones/add-unwrap-in-typescript
|
@beejones thank you for adding the C++ implementation. It needs testing too, a good starting point is the test for wrapKey: CCF/tests/js-modules/modules.py Line 549 in 115d1af
That currently does the unwrapping in Python (which I suggest you leave in), but you could for each variant unwrap with an endpoint calling the new function and make sure the results match. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
@beejones thank you for adding the tests, the PR looks good. There's just one thing: the scrubbing of private keys from the heap isn't quite right and scrubs caller input rather than the temporary copies created inside the call. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
@beejones can you merge main into your branch please? There's usually a button to do this on the PRs, I am not sure why it doesn't appear on yours. This is necessary so that the CI runs on what main would contain post-PR-merge, including all recent commits, and is automatically enforced. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Added unwrapKey to ccfcrypto.
Make sure unit tests use the new unwrapKey function