Fix for using the correct info for PIN/PUK (before they were switched).

This commit is contained in:
Zoltan Kelemen 2020-07-04 11:57:06 +02:00 committed by Frank Morgner
parent e80906d973
commit 555cb73615
1 changed files with 8 additions and 8 deletions

View File

@ -632,16 +632,16 @@ int sc_pkcs15_unblock_pin(struct sc_pkcs15_card *p15card,
data.puk_reference = pukref;
data.pin1.data = puk;
data.pin1.len = puklen;
data.pin1.pad_char = auth_info->attrs.pin.pad_char;
data.pin1.min_length = auth_info->attrs.pin.min_length;
data.pin1.max_length = auth_info->attrs.pin.max_length;
data.pin1.pad_length = auth_info->attrs.pin.stored_length;
data.pin1.pad_char = puk_info->attrs.pin.pad_char;
data.pin1.min_length = puk_info->attrs.pin.min_length;
data.pin1.max_length = puk_info->attrs.pin.max_length;
data.pin1.pad_length = puk_info->attrs.pin.stored_length;
data.pin2.data = newpin;
data.pin2.len = newpinlen;
data.pin2.pad_char = puk_info->attrs.pin.pad_char;
data.pin2.min_length = puk_info->attrs.pin.min_length;
data.pin2.max_length = puk_info->attrs.pin.max_length;
data.pin2.pad_length = puk_info->attrs.pin.stored_length;
data.pin2.pad_char = auth_info->attrs.pin.pad_char;
data.pin2.min_length = auth_info->attrs.pin.min_length;
data.pin2.max_length = auth_info->attrs.pin.max_length;
data.pin2.pad_length = auth_info->attrs.pin.stored_length;
if (auth_info->attrs.pin.flags & SC_PKCS15_PIN_FLAG_NEEDS_PADDING)
data.flags |= SC_PIN_CMD_NEED_PADDING;