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

Add support for large messages #9

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add support for large messages #9

wants to merge 1 commit into from

Conversation

evilrix
Copy link

@evilrix evilrix commented Aug 24, 2015

Rather than having to verify a whole memory buffer in one go, allow chunks of
memory to be processed using begin, update and end verify functions. The begin
function starts a new verify process, returning an opaque context handle. The
update function can then be called multiple times with this context and blocks
of memory to process memory in chuncks. Finally the end function is called with
the context to end the verify process and get the result.

@immesys
Copy link

immesys commented Aug 24, 2015

This is very useful, I added my own variant of this when I started using ed25519. I know reviewing crypto contributions is a pain but it would be nice to have this out the box.

Rather than having to verify a whole memory buffer in one go, allow chunks of
memory to be processed using begin, update and end verify functions. The begin
function starts a new verify process, returning an opaque context handle. The
update function can then be called multiple times with this context and blocks
of memory to process memory in chuncks. Finally the end function is called with
the context to end the verify process and get the result.
@ghost
Copy link

ghost commented Sep 13, 2016

thanks for the pr, I'll patch my source tree

@paulocoutinhox
Copy link

Hi,

It can be used inside a ESP8266 12F or Arduino or Both?

Thanks.

@rdebath
Copy link

rdebath commented Apr 26, 2017

If you're signing large amounts of data are you supposed to generate a SHA512 of the data you want to sign and then sign that 512 bit hash? Do the same (calculate the SHA512 of the input) then verify the hash at the other end.

If so the facilities for that already exist in the library, ie the SHA512 can be fed in blocks.

It should also be faster for signing as you only have to scan the file once, verifying the signature will, of course be exactly the same speed.

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.

None yet

4 participants