lkml.org 
[lkml]   [2016]   [Jan]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: PKCS#7 parser and MS SpcSpOpusInfo OID
From
On Mon, Jan 18, 2016 at 3:54 PM, Juerg Haefliger <juergh@gmail.com> wrote:
> Hi,
>
> The pkcs7 kernel parser currently checks for the following AuthAttrs
> (in pkcs7_sig_note_set_of_authattrs()):
>
> (ctx->msg->data_type == OID_msIndirectData &&
> !test_bit(sinfo_has_ms_opus_info, &sinfo->aa_set))
>
> This check passes for an MS signtool signed kernel but not for an sbsign
> signed kernel. The sbsign'ed kernel signature doesn't contain an SpcSpOpusInfo
> structure.
>
> signtool signature:
> $ dumpasn1 signtool.sig | grep '1 3 6 1 4 1 311'
> : spcIndirectDataContext (1 3 6 1 4 1 311 2 1 4)
> : spcPEImageData (1 3 6 1 4 1 311 2 1 15)
> : spcSpOpusInfo (1 3 6 1 4 1 311 2 1 12)
> : spcIndirectDataContext (1 3 6 1 4 1 311 2 1 4)
> : spcStatementType (1 3 6 1 4 1 311 2 1 11)
> : individualCodeSigning (1 3 6 1 4 1 311 2 1 21)
>
> sbsign signature:
> $ dumpasn1 sbsign.sig | grep '1 3 6 1 4 1 311'
> : spcIndirectDataContext (1 3 6 1 4 1 311 2 1 4)
> : spcPEImageData (1 3 6 1 4 1 311 2 1 15)
> : spcIndirectDataContext (1 3 6 1 4 1 311 2 1 4)
>
> Is the check too restrictive or is sbsign doing something wrong? What am I
> missing?

Addressed here: https://lkml.org/lkml/2016/1/18/331


> Thanks
> ...Juerg
>
> --
> Juerg Haefliger
> Hewlett Packard Enterprise

--
Juerg Haefliger
Hewlett Packard Enterprise

\
 
 \ /
  Last update: 2016-01-25 11:21    [W:0.130 / U:0.828 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site