livebe01

Hi @v-roackerman, we just deployed the fix for this issue to Demo as part of the [v1.1.0.36](https://github.com/usnistgov/ACVP-Server/releases/tag/v1.1.0.36) release. Are you be able to test it to confirm? Thank you.

Okay. It was a very straightforward fix. Changing a 256 to a 255. Ben On Oct 7, 2024, at 1:10 PM, v-roackerman ***@***.***> wrote: It is rare that I see...

The fix for this issue has been deployed to ACVTS Prod as part of the [v1.1.0.36](https://github.com/usnistgov/ACVP-Server/releases/tag/v1.1.0.36) release.

The fix for this is on Demo in release [v1.1.0.41](https://github.com/usnistgov/ACVP-Server/releases/tag/v1.1.0.41).

As of 11/12/25, the fix for this is on Prod in release [v1.1.0.41](https://github.com/usnistgov/ACVP-Server/releases/tag/v1.1.0.41).

@jvdsn @celic I'm thinking it may make sense to remove the XECDH KeyGen and KeyVer testing. KeyGen effectively gets tested by the SSC tests.

@celic @jvdsn right now, the XECDH SSC testing provides the server's public key in the prompt for each test case. In the response, the IUT provides its public key along...

> > @celic @jvdsn right now, the XECDH SSC testing provides the server's public key in the prompt for each test case. In the response, the IUT provides its public...

> @livebe01 in that case, KeyGen and KeyVer would remain though, right? Since then KeyGen wouldn't be covered by SSC anymore I guess I don't understand why you implemented KeyGen...

@livebe01 keys used by X25519 and X448 are not (should not) be used for any other cryptographic schemes. The reason why I added KeyGen and KeyVer was just for consistency...