livebe01

Hi @arthurTheAardvark, I took a look at the askdfvs.pdf document that you referenced as well as the last available version of CAVS. It appears that there used to be an...

I’d like to have it out in the next 30 days, but given scheduled leave, ICMC coming up, and the number of lab audits we have lined up, it may...

Hi @jvdsn, thank you for mentioning this. 1. I believe that the idea of Table 1 was to line up w/ Table 2 of SP 800-90Ar1 which references SP 800-57...

Hi @jvdsn, another note on #3. The purpose of listing the maximum security strengths is to aid in calculating the minimums to use for the items in Table 3. Currently,...

This change is on Demo in release [v1.1.0.26](https://github.com/usnistgov/ACVP-Server/releases/tag/v1.1.0.26)

Thanks for persisting on this one @locksmithone! Hopefully [this](https://github.com/usnistgov/ACVP/commit/19f1dbc16b808509c7d12f9c30332ee307369443) change to the definition of the dataUnitLen registration property helps.

I believe at least some of these issues have been addressed, e.g., encoding, pattern, and hmacAlg

@jbrock24 it could be worth trying the [registration](https://github.com/usnistgov/ACVP/issues/1350#issuecomment-1170008290) in question against Demo again to see if the behavior still presents as there were a number of updates to XTS 2.0...

Ah, have you tried this registration with `"dataUnitLenMatchesPayload":true`? I see that the dataUnitLen matches the payloadLen in this instance.

Ah, setting `dataUnitLenMatchesPayloadLen` to true doesn't literally cause the 1.0 code to be accessed. But setting `dataUnitLenMatchesPayloadLen` to true is roughly equivalent to getting a vector set from the 1.0...