livebe01

> > Do you believe your update to SHAKE will affect cSHAKE and KMAC validation results for the similar case of non-byte oriented outputs? > > The change we made...

Hi @davyrouillard, @dspdon, we do apologize for not being able to give this attention sooner. This task as well as the related https://github.com/usnistgov/ACVP-Server/issues/352 issue are assigned to @jbrock24 and he...

Sure. Our plan is to have a fix for this issue included in our next release, v1.1.0.38. We'd like to have the v1.1.0.38 release on Demo before Thanksgiving.

Thank you! Yes, we believe we have this fixed. But we're still hashing out https://github.com/usnistgov/ACVP-Server/issues/352. I assume that both this issue and #352 are preventing you from testing particular algorithm...

Great, the fix for this issue is ready. It will be included in our next Demo deployment. It missed the v1.1.0.38 release that went to Demo on Tuesday, but if...

Attached are SHAKE-128 and SHAKE-256 test vectors that were produced using our updated testing. Feel free to run the tests through your implementation to confirm that we're getting the same...

Great, thanks for doing that @dspdon. We needed to put together a hotfix for the ACVTS v1.1.0.38 release and it was pretty simple to add this to it. The fix...

Hi @dspdon. Eck, I really thought we had this one worked out. Since this issue only effects the VOT cases where "outLen % 8 > 0" and we're pretty sure...

[These](https://github.com/usnistgov/ACVP/pull/1599) changes have been made to the symmetric spec.

Hi @dspdon, for #1, we believe that the ivLen should always be 104 bits. Do you disagree?