At the point where you realize you have for maybe years only been looking at the top bit of every byte in CRYPTO_memcmp, don’t you maybe just retire the PA-RISC port?
Yeah seriously. There's no need for whst should be portable sw to drop any api-conforming target, but drop the damn asm. It's a liability.
-
-
My take-away from this thread was the real missing piece is a good test that covers this. Then I looked at our tests and we would have caught this, but not a similar error with the MSB. Added an inelegant but functional exhaustive test case:https://github.com/awslabs/s2n/pull/762 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.