Re: Fixing confirmed memory leaks in CryptoPP?

On Friday, September 24, 2021 at 12:16:22 PM UTC-4 [email protected] 
wrote:

> I have already foregone the use of dynamic thread creation for similar 
> reasons.  That is, after program initialization no new threads are ever 
> created.  All I need now are the bare bones functions standing alone to 
> sign, and then verify a message using ECDSA SHA 256 with secp256k1 keys.
>

https://www.cryptopp.com/wiki/Elliptic_Curve_Digital_Signature_Algorithm 
and https://www.cryptopp.com/wiki/Wrapper_DLL

This is just pure math isn't it?  And if verifiers, string sinks, or 
> whatever have to be allocated as "new," why cannot they be cleanly freed 
> after use in scope? 
>

https://www.cryptopp.com/wiki/Pipelining#Ownership

Jeff

-- 
You received this message because you are subscribed to the Google Groups "Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/cryptopp-users/dd806d01-67a9-417c-9236-f6af44ad47e0n%40googlegroups.com.