Closed MarkSimontonOfCG closed 5 months ago
Our DER encoding process (the DER encoding method) does:
06 09 60 86 48 01 65 03 04 01 05
, which is the OID for AES-128-KW
.data
.30
|| LEN
(of DATA) || OID
|| COUNTER
|| DATA
This is how they are all processed and created, please let me know if you have any other questions.
so as I read your response data = PartyU || PartyV || PubInfo || PrivInfo this implies there is no DER HEADER for the data internal parts, is that correct?
environment Demo
testSessionId 454282
vsId 1944424
Algorithm registration
Endpoint in which the error is experienced NA
Expected behavior The MS-ACVP generated derivedKey should match the Demo server Derived key
Additional context Add any other context about the problem here. am including 2 examples of where the test code I have key material does not match the output from the Demo server. I believe the problemis in how my code is prepending the TAG + LENGTH header to the value for constructed types; but I don't know what the difference is if someone could provide the matching values to those listed here I would be able to finish this test.
some general observations, key-encryption-key generated for input that only includes ZZ | OtherInfo(OID, counter), works every time. If the key material, includes optional material with maximum length >= 464 bits the key-encryption-key, do not match.
TEST CASE 4 SUSPECTED BYTES
30 82 01 03
30 = APPLICATION | SEQUENCE 82 = VALUE > 128 BYTES, 2 BYTES 0103 = 259 BYTESTEST CASE 4 SUSPECTED BYTES
30 82 01 03
30 = APPLICATION | SEQUENCE 82 = VALUE > 128 BYTES, 2 BYTES 0103 = 259 BYTESsession ID 454282, vecorSetID = 1944424 t0 expected
msacvp-results
Details
Test Case 4 Expected
msacvp-results
Details