forked from Minki/linux
pefile: Handle pesign using the wrong OID
The pesign utility had a bug where it was using OID_msIndividualSPKeyPurpose instead of OID_msPeImageDataObjId - so allow both OIDs. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Acked-by: Vivek Goyal <vgoyal@redhat.com>
This commit is contained in:
parent
4c0b4b1d1a
commit
dd7d66f21b
|
@ -58,7 +58,13 @@ int mscode_note_content_type(void *context, size_t hdrlen,
|
||||||
return -EBADMSG;
|
return -EBADMSG;
|
||||||
}
|
}
|
||||||
|
|
||||||
if (oid != OID_msIndividualSPKeyPurpose) {
|
/*
|
||||||
|
* pesign utility had a bug where it was putting
|
||||||
|
* OID_msIndividualSPKeyPurpose instead of OID_msPeImageDataObjId
|
||||||
|
* So allow both OIDs.
|
||||||
|
*/
|
||||||
|
if (oid != OID_msPeImageDataObjId &&
|
||||||
|
oid != OID_msIndividualSPKeyPurpose) {
|
||||||
pr_err("Unexpected content type OID %u\n", oid);
|
pr_err("Unexpected content type OID %u\n", oid);
|
||||||
return -EBADMSG;
|
return -EBADMSG;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue
Block a user