Again Parity Error

Oct 12, 2010 at 12:42 PM

Hi nickntg,

Your are fix A4 command and they are work fine.

But when I try to get Key Check Value by BU command I again receive parity error message 0000BV10.

Commands:

For generating keys

Generate key from component:
0000A2002UComponent1
0000A2002UComponent2
0000A42002U

Get KCV
0000BU001

Command events look like

=== [A2], starts 15:32:19.444 =======
[Key,Value]=[Key Scheme LMK,U]
[Key,Value]=[Key Type,002]

Key generated (clear): 4CD6DABFD9F2CB73DC07BF91769113DC
Key generated (LMK): UF1D820C0C41E44D1838E695384A01421
=== [A2],   ends 15:32:19.444 =======

=== [A2], starts 15:32:19.444 =======
[Key,Value]=[Key Scheme LMK,U]
[Key,Value]=[Key Type,002]

Key generated (clear): E5C116C219401C29DC754FA42AF708DA
Key generated (LMK): U549E7358D2AF3680C8AB5C8EAF4A28BC
=== [A2],   ends 15:32:19.444 =======

=== [A4], starts 15:32:19.460 =======
[Key,Value]=[Key Component #1,F1D820C0C41E44D1838E695384A01421]
[Key,Value]=[Key Component #2,549E7358D2AF3680C8AB5C8EAF4A28BC]
[Key,Value]=[Key Component Scheme #1,U]
[Key,Value]=[Key Component Scheme #2,U]
[Key,Value]=[Key Scheme (LMK),U]
[Key,Value]=[Key Type,002]
[Key,Value]=[Number of Components,2]

Component 1 (clear): 4CD6DABFD9F2CB73DC07BF91769113DC
Component 2 (clear): E5C116C219401C29DC754FA42AF708DA
Key (clear): A917CC7DC0B2D75A0072F0355C661B06
Check value: 7F781E
=== [A4],   ends 15:32:19.460 =======

=== [BU], starts 15:32:23.960 =======
[Key,Value]=[Key,209EB830EC757B8837A881995C60940A]
[Key,Value]=[Key Length Flag,1]
[Key,Value]=[Key Scheme,U]
[Key,Value]=[Key Type Code,00]

=== [BU],   ends 15:32:23.960 =======

Maybe same situation like with A4 command?

 

PS my knowledge in VB is zero

Coordinator
Oct 12, 2010 at 4:46 PM

The A4 command generates a key of type 002, which is a PVK/TPK/TMK and is encrypted under the LMK pair 14-15. So in the BU command you should set the key type code to 02.

However, like before, you found another problem. The A4 command does not force odd parity on the generated key. In your case you should have gotten a key value of A816CD7CC1B3D65B0173F1345D671A07 instead of A917CC7DC0B2D75A0072F0355C661B06, so another small fix is in order for the A4 command. I'll upload the fix in a few minutes and will post back.

Coordinator
Oct 12, 2010 at 4:52 PM

Please try out the 55957 changeset. Along with changing the type code to 02, it should fix your problem.

Thanks again for taking the time to post about the problems you encounter.

Oct 12, 2010 at 5:05 PM

Yes! Problem fixed.

Many thanks for your program.

Coordinator
Oct 12, 2010 at 5:19 PM

You're very welcome. Again, I appreciate your taking the time to post the problem so it can get fixed.