1 Reply by jasonstathemSuperHero

(5 replies, posted in wolfSSL)

Oh yeah, one more thing.

If local variables (i.e. "allocated" on stack) are used during key generation, is it possible to do something with them?

Does wolfSSL have option to zero local variables after their usage?

Though i examined bignum struct implementation and found "dp" pointer field (to hold number data i think). Does it mean even if bignum variable is created statically, it uses dynamic memory all the same?

Go to forum: wolfSSL

2 Reply by jasonstathemSuperHero

(5 replies, posted in wolfSSL)

dgarske, yeah! Genius idea, it feels a little hacky.

Thank you!

Go to forum: wolfSSL

3 Topic by jasonstathemSuperHero

(5 replies, posted in wolfSSL)

Hey!

I know wolfSSL gives the ability to override wolfSSL_Free with wolfSSL_SetAllocators.
But i cant understand. Why wolfSSL_Free is defined in this form:

void wolfSSL_Free(void* ptr)

rather than in this:

void wolfSSL_Free(void* ptr, size_t size) //added 'size' parameter

?

My custom function is unabe to determine how many zeroes to write in memory.

What can i do with this?

Thanks for reply:)

Go to forum: wolfSSL