CHUID: fix the encoding of the FASC-N data element in the CHUID
This is the hard-coded FASC-N field being used by yubico-piv-tool [9999-9999-999999-0-1-0000000000300001] S9999F9999F999999F0F1F0000000000300001E It should be encoded as this sequence of 5-bit values 11010 (SS) 10011 10011 10011 10011 (9999) 10110 (FS) 10011 10011 10011 10011 (9999) 10110 (FS) 10011 10011 10011 10011 10011 10011 (999999) 10110 (FS) 00001 (0) 10110 (FS) 10000 (1) 10110 (FS) 00001 00001 00001 00001 00001 00001 00001 00001 00001 00001 (0000000000) 11001 (3) 00001 00001 00001 00001 (0000) 10000 (1) 11111 (ES) 01011 (LRC) This packs into this 25-byte (200-bit) sequence of hex bytes: d4 e7 39 da 73 9c ed 39 ce 73 9d 83 68 58 21 08 42 10 84 21 c8 42 10 c3 eb
This commit is contained in:
+2
-2
@@ -57,8 +57,8 @@
|
||||
*/
|
||||
const uint8_t CHUID_TMPL[] = {
|
||||
0x30, 0x19, 0xd4, 0xe7, 0x39, 0xda, 0x73, 0x9c, 0xed, 0x39, 0xce, 0x73, 0x9d,
|
||||
0x83, 0x68, 0x58, 0x21, 0x08, 0x42, 0x10, 0x84, 0x21, 0x38, 0x42, 0x10, 0xc3,
|
||||
0xf5, 0x34, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
|
||||
0x83, 0x68, 0x58, 0x21, 0x08, 0x42, 0x10, 0x84, 0x21, 0xc8, 0x42, 0x10, 0xc3,
|
||||
0xeb, 0x34, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
|
||||
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x35, 0x08, 0x32, 0x30, 0x33, 0x30, 0x30,
|
||||
0x31, 0x30, 0x31, 0x3e, 0x00, 0xfe, 0x00,
|
||||
};
|
||||
|
||||
Reference in New Issue
Block a user