Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Dave Young <dyoung@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	kexec@lists.infradead.org, xlpang@redhat.com, vgoyal@redhat.com,
	pjones@redhat.com
Subject: Re: Kexec_file_load failed with "Missing required AuthAttr"
Date: Fri, 15 Jan 2016 16:12:49 +0800	[thread overview]
Message-ID: <20160115081249.GA19487@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <20160107052507.GA12900@dhcp-128-65.nay.redhat.com>

Ccing Peter Jones for pesign possible issues. 

On 01/07/16 at 01:25pm, Dave Young wrote:
> Hi,
> 
> I saw the warning "Missing required AuthAttr" when testing kexec, known issue?
> Idea about how to fix it?
> 
> The kernel is latest linus tree plus sevral patches from Toshi to cleanup io resource structure.
> 
> in function pkcs7_sig_note_set_of_authattrs():
>         if (!test_bit(sinfo_has_content_type, &sinfo->aa_set) ||
>             !test_bit(sinfo_has_message_digest, &sinfo->aa_set) ||
>             (ctx->msg->data_type == OID_msIndirectData &&
>              !test_bit(sinfo_has_ms_opus_info, &sinfo->aa_set))) {
>                 pr_warn("Missing required AuthAttr\n");
>                 return -EBADMSG;
>         }
> 
> The third condition below is true:
> (ctx->msg->data_type == OID_msIndirectData &&
>              !test_bit(sinfo_has_ms_opus_info, &sinfo->aa_set))
> 
> I signed the kernel with redhat test key like below:
> pesign -c 'Red Hat Test Certificate' -i arch/x86/boot/bzImage -o /boot/vmlinuz-4.4.0-rc8+ -s --force
> 
> Thanks
> Dave

  reply	other threads:[~2016-01-15  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07  5:25 Kexec_file_load failed with "Missing required AuthAttr" Dave Young
2016-01-15  8:12 ` Dave Young [this message]
2016-01-18 15:49   ` [PATCH] Don't require SpcSpOpusInfo in Authenticode pkcs7 signatures Peter Jones
2016-01-18 15:49   ` Peter Jones
2016-01-19  1:08     ` Dave Young
2016-01-25 14:00       ` Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160115081249.GA19487@dhcp-128-65.nay.redhat.com \
    --to=dyoung@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pjones@redhat.com \
    --cc=vgoyal@redhat.com \
    --cc=xlpang@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox