wycheproof VS jdk17u

I failed to notice the relevant Wycheproof test vectors because they weren’t listed on the front page (they still aren’t).

When I wrote the Monocypher cryptographic library, I didn't really know how to write serous tests. With some help, I eventually got something pretty good, with 100% code and path coverage, that test every possible input lengths as well as obscure corner cases I stole from various places (most notably Whycheproof).

"GitHub - google/wycheproof: Project Wycheproof tests crypto libraries against known attacks." https://github.com/google/wycheproof

Thankfully, Curve25519 is much easier to implement, with much fewer death traps than short Weierstraß curves. For X25519, just follow DJB’s advice from ECC Hacks https://www.youtube.com/watch?v=vEt-D8xZmgE and make sure your arithmetic is up to snuff (constant time arithmetic is actually the hard part, by default I strongly suggest you steal it from the ref10 implementation).

For EdDSA, just follow the relevant explicit formulas, avoid clever (but dangerous) tricks such as converting to Montgomery form and back, and test with Wycheproof’s Ed25519 test vectors. https://github.com/google/wycheproof/blob/master/testvectors...

Have you tested all your applicable components against the Wycheproof test vectors and passed?

I wouldn't have been surprised if that was the case - Java Strings are immutable, there's no need to copy data that is already there. But apparently it isn't. Each constructed string seems to be getting its own byte array. Please provide a source if you disagree.

The majority of the work on 8u, 11u, 17u releases happens in OpenJDK upstream, in so called JDK Updates Projects, by engineers from the interested JDK vendors. You can get a peek who does this kind of work from the repository histories, for example the most recent 11.0.13 is done by engineers from Red Hat (including yours truly), SAP, Azul, Microsoft, BellSoft, Tencent, Amazon, Alibaba, IBM, ARM, Google.