Hi Kaleb,
thanks for reply, that is encouraging
You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → Posts by pal
Pages 1
Hi Kaleb,
thanks for reply, that is encouraging
Hi Kaleb,
It looks like you are talking past each other, maybe choice of "stream" wording is confusing. It refers here not to distinction between stream/block ciphers but to processing data chunks as they arrive without buffering full file in memory(which can be of any size and we can't change cipher mode or framing or anything else because we have to interoperate with existing implementations). I.e. we would like to see API which can be used in chunked fashion, like { init, update, update, ..., finish }, not current function which handles all data in one go.
I'm pretty sure intermediate resources needed for this are constant and consist of two counter blocks and one hash block, i.e. 48 bytes.
You could look for inspiration here https://stackoverflow.com/questions/121 … 2#13045182
Take note of while loops. It doesn't loop over AAD portion, but it is both supported by OpenSSL and not required in our case(because its size is small).
Pages 1
wolfSSL - Embedded SSL Library → Posts by pal
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.017 seconds (96% PHP - 4% DB) with 5 queries