livebe01
livebe01
Sure, this is something we can look at. I'm thinking it'd be quicker to update the documentation to match the behavior than to update the behavior to match the documentation.
You're right. Very straightforward. We'll get this fixed.
SaltLen should also not be showing up in the prompt for pkcs1v1.5...
The fix for this issue has been deployed to ACVTS Demo 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 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.
Thanks @sim-nvidia. How many bits does your implementation allow for the exponent?
Hi @xnox, can you link the draft D.S IG you're referring to? The draft @celic and I consulted states that an approved key combiner is required per SP 800-227. Our...
Hi @jwesevic-atsec. Sure, what you're saying makes sense. Can you point us to some examples where multiple certs have been needed on account of this issue?
Thanks @jwesevic-atsec. For NVIDIA Security Engine, what values does it support for customKeyInLength?
Thanks @jwesevic-atsec. This would be a very simple change when we write a new testing revision for the SP 800-108 KDF algorithm. Until then, we'd be happy to work with...