Dear Jeffrey, OK then, I'll give it another shot. What I need to do is avoid the dll altogether, include just the necessary headers, expressly build in any actually required functions, and especially swear off any pipelining so i can isolate problem points.
Thank you again for your gracious help. Peace, Pen On Friday, September 24, 2021 at 9:22:31 AM UTC-7 Jeffrey Walton wrote: > On Friday, September 24, 2021 at 12:16:22 PM UTC-4 activis...@gmail.com > 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 cryptopp-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/cryptopp-users/4e8a7566-65d5-4a60-9e2d-fcf152e992c7n%40googlegroups.com.
