From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 33D5FC282DD for ; Thu, 23 May 2019 13:26:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 084ED20862 for ; Thu, 23 May 2019 13:26:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730081AbfEWN0U (ORCPT ); Thu, 23 May 2019 09:26:20 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:39502 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726310AbfEWN0U (ORCPT ); Thu, 23 May 2019 09:26:20 -0400 Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4NDEuhD012227 for ; Thu, 23 May 2019 09:26:19 -0400 Received: from e06smtp04.uk.ibm.com (e06smtp04.uk.ibm.com [195.75.94.100]) by mx0a-001b2d01.pphosted.com with ESMTP id 2snv838h51-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 23 May 2019 09:26:19 -0400 Received: from localhost by e06smtp04.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 23 May 2019 14:26:17 +0100 Received: from b06cxnps4075.portsmouth.uk.ibm.com (9.149.109.197) by e06smtp04.uk.ibm.com (192.168.101.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Thu, 23 May 2019 14:26:13 +0100 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06cxnps4075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x4NDQCsO37028084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 23 May 2019 13:26:13 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D7AB9A4053; Thu, 23 May 2019 13:26:12 +0000 (GMT) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 68DC4A4057; Thu, 23 May 2019 13:26:12 +0000 (GMT) Received: from localhost.localdomain (unknown [9.80.80.124]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Thu, 23 May 2019 13:26:12 +0000 (GMT) Subject: Re: IMA signature generated by evmctl has unexpected key identifier From: Mimi Zohar To: Lakshmi , linux-integrity@vger.kernel.org Date: Thu, 23 May 2019 09:26:01 -0400 In-Reply-To: <3b8e6688-3d3e-18bf-239b-a0bc47d60a58@linux.microsoft.com> References: <90a4d769-4c32-4b2b-ceaa-6e0980d5c193@linux.microsoft.com> <1557854750.4139.65.camel@linux.ibm.com> <4b810e48-6ddc-19d0-9fc1-70cd29c7c01b@linux.microsoft.com> <1557869914.4139.73.camel@linux.ibm.com> <5d1ab46e-ea01-b7a7-4a9b-6e4bcb63c331@linux.microsoft.com> <1558485033.4039.215.camel@linux.ibm.com> <3b8e6688-3d3e-18bf-239b-a0bc47d60a58@linux.microsoft.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 19052313-0016-0000-0000-0000027EB7FE X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19052313-0017-0000-0000-000032DBAF38 Message-Id: <1558617961.4347.161.camel@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-05-23_11:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=729 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905230092 Sender: linux-integrity-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-integrity@vger.kernel.org On Wed, 2019-05-22 at 18:10 -0700, Lakshmi wrote: > In my setup, IMA signing key will be signed by a key in the "BuiltIn > Trusted Keys". That is exactly how it is meant to be used.  In conjunction with the examples/ scripts, please follow the "Generate trusted keys" section of the README.  The last two steps show how to create a certificate signing request (CSR) and sign the certificate with a CA key.  The CA public key should be loaded onto the builtin keyring. Mimi