-
Notifications
You must be signed in to change notification settings - Fork 484
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
OQS_SHA*_sha***_ API does not support arbitrary length updates #1606
Comments
This change could be added to "Make low-level crypto algorithms implementation switchable #1599" |
@dstebila : What was the reason to add this issue to the 0.10.0 milestone? OK to postpone this to 0.11.0 such as to bring the 0.10.0 milestone to completion/"RC-readiness"? |
This was needed to implement LMS. Since that work is slated for a later release, I think it's safe to do the same here. |
Completed (for SHA256) in #1650. |
For example
OQS_SHA2_sha256_inc_blocks(OQS_SHA2_sha256_ctx *state, const uint8_t *in, size_t inblocks)
This makes an assumption that all the data is present at the time of processing and thus can be broken up into blocks. This also does not easily allow parse and update processing of arbitrary fields.
The proposal would be to add a new API to support this.
OQS_SHA*_sha***_inc(OQS_SHA2_sha***_ctx *state, const uint8_t *in, size_t in_len)
The text was updated successfully, but these errors were encountered: