mcarrickscott commented on PR #95: URL: https://github.com/apache/incubator-milagro-crypto-c/pull/95#issuecomment-1451760475
Amen to that. As an aIternative and to avoid sleepless nights I could write a very very short function that confirms that the compiler is interpreting undefined behaviour as I expect it to, execute it on start-up, and refuse to run if it detects a problem. Mike On Thu, Mar 2, 2023 at 2:21 PM Matthias Görgens ***@***.***> wrote: > Thanks for the discussion. > > If you treat undefined behaviour in a cryptographic library as not-a-bug, > there's nothing further I can do here. > > I hope you'll never change the compiler version or any compiler flags, and > that the compiler will always produce the native code you pray for, and > that the code produce won't be exploited by adversaries with specially > crafted input. > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-milagro-crypto-c/pull/95#issuecomment-1451632547>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAU3ZDXUPUPP4XCY7CJGTTTW2BYCDANCNFSM6AAAAAATEDLYUI> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
