Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2847961imu; Sun, 9 Dec 2018 10:42:21 -0800 (PST) X-Google-Smtp-Source: AFSGD/V1jmcslDO3gAqcEQyAD/O1KXb1dDGa8MhlClxMICsa5EZmmHL1kcEIgyDDeQUWo8XDhKPD X-Received: by 2002:a62:435a:: with SMTP id q87mr9466329pfa.109.1544380941809; Sun, 09 Dec 2018 10:42:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544380941; cv=none; d=google.com; s=arc-20160816; b=oUNPAXa3RVBxGCZwBq4z8tvnJs5v0wvTWy9o6pF+JM1fjAgFqD9t31QFyNOAe8OHeG dnDKIAboOWtLM5uR9bfAFiBSY8zgKntJ1VAM5nxCxBcaf2DZel+nXprZzbbuCACTDhXj rfp2EsWJbKAUAH/ITffWDYEXfaxNDYbdvFJE3SMvlHDQXOCH2qdQ2ibbbiUUYnsr2YX9 2O22oiiiFWIyankJHPq7ptItb65t0G7n9COFZmHKSNWXkKslnZTnue0YXPSYA0Dx5T8r 00GEDiHa1/L8KqMNHXjznNSPQQEXMphz0lsXTiXoxGIvPgldrW+/6e6l4fsmzv368DOm +8xg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :mime-version:references:in-reply-to:date:cc:to:from:subject; bh=uOpbdh7fnm95F+c7a0FoT3ru2FlJBtFLte0zRunVuOQ=; b=sBo3+k4dBUn2eML6Q+K4kV+yZ2Omhn1XK9CUtXUNP5dhNVc9pCdx91MzY0FlBCrnd1 OOLFmEFpkvLV6UjeRwlNZozywAPPT51LJ95LMFXH4O4pCoqCE5oIUIKB/xhPTSBbJ02O vTQ4YrmEBZuUco4FM4HArC/TIv9Z988olxJ06PqLmICUNcDYgsqXNY4NoxxFGchM53tB +J6esbaw9Gygel51tCJ8u0l6C+vETsHK5t5uCmUQJZnxYe308Jl7UpHE4/RnKc8ujWn8 ZwLosqJkEK0UMyOlR4NUJjULqPom4QwAIMtKDkpNNqQw129p8LRc+RY00xKUIdPkzU4+ 8JMw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n12si7667517pgb.563.2018.12.09.10.42.05; Sun, 09 Dec 2018 10:42:21 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726243AbeLISkT (ORCPT + 99 others); Sun, 9 Dec 2018 13:40:19 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:55270 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726223AbeLISkS (ORCPT ); Sun, 9 Dec 2018 13:40:18 -0500 Received: from pps.filterd (m0098404.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id wB9Id7Rv100858 for ; Sun, 9 Dec 2018 13:40:17 -0500 Received: from e06smtp07.uk.ibm.com (e06smtp07.uk.ibm.com [195.75.94.103]) by mx0a-001b2d01.pphosted.com with ESMTP id 2p8uydca72-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 09 Dec 2018 13:40:17 -0500 Received: from localhost by e06smtp07.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sun, 9 Dec 2018 18:40:15 -0000 Received: from b06cxnps4075.portsmouth.uk.ibm.com (9.149.109.197) by e06smtp07.uk.ibm.com (192.168.101.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Sun, 9 Dec 2018 18:40:10 -0000 Received: from d06av26.portsmouth.uk.ibm.com (d06av26.portsmouth.uk.ibm.com [9.149.105.62]) by b06cxnps4075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id wB9Ie9pN852324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sun, 9 Dec 2018 18:40:09 GMT Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 17D6EAE057; Sun, 9 Dec 2018 18:40:09 +0000 (GMT) Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 71F4BAE045; Sun, 9 Dec 2018 18:40:07 +0000 (GMT) Received: from localhost.localdomain (unknown [9.80.88.113]) by d06av26.portsmouth.uk.ibm.com (Postfix) with ESMTP; Sun, 9 Dec 2018 18:40:07 +0000 (GMT) Subject: Re: [PATCH v2 0/7] add platform/firmware keys support for kernel verification by IMA From: Mimi Zohar To: Nayna Jain , linux-integrity@vger.kernel.org Cc: linux-security-module@vger.kernel.org, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, dhowells@redhat.com, jforbes@redhat.com, seth.forshee@canonical.com, kexec@lists.infradead.org, keyrings@vger.kernel.org, vgoyal@redhat.com, ebiederm@xmission.com, mpe@ellerman.id.au Date: Sun, 09 Dec 2018 13:39:56 -0500 In-Reply-To: <20181208202705.18673-1-nayna@linux.ibm.com> References: <20181208202705.18673-1-nayna@linux.ibm.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: 18120918-0028-0000-0000-0000032829AB X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18120918-0029-0000-0000-000023E448D4 Message-Id: <1544380796.3794.6.camel@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-12-09_07:,, 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812090173 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Nayna, On Sun, 2018-12-09 at 01:56 +0530, Nayna Jain wrote: > On secure boot enabled systems, a verified kernel may need to kexec > additional kernels. For example, it may be used as a bootloader needing > to kexec a target kernel or it may need to kexec a crashdump kernel. > In such cases, it may want to verify the signature of the next kernel > image. > > It is possible that the new kernel image is signed with third party keys > which are stored as platform or firmware keys in the 'db' variable. The > kernel, however, can not directly verify these platform keys, and an > administrator may therefore not want to trust them for arbitrary usage. > In order to differentiate platform keys from other keys and provide the > necessary separation of trust the kernel needs an additional keyring to > store platform/firmware keys. > > The secure boot key database is expected to store the keys as EFI > Signature List(ESL). The patch set uses David Howells and Josh Boyer's > patch to access and parse the ESL to extract the certificates and load > them onto the platform keyring. > > The last patch in this patch set adds support for IMA-appraisal to > verify the kexec'ed kernel image based on keys stored in the platform > keyring. Thanks!  This patch set is now in the #next-integrity branch. https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git/ Mimi