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=-7.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 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 EF7B3C43603 for ; Mon, 9 Dec 2019 19:47:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BCEC6206E0 for ; Mon, 9 Dec 2019 19:47:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726532AbfLITrY (ORCPT ); Mon, 9 Dec 2019 14:47:24 -0500 Received: from mga04.intel.com ([192.55.52.120]:48858 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726342AbfLITrY (ORCPT ); Mon, 9 Dec 2019 14:47:24 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Dec 2019 11:47:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,296,1571727600"; d="scan'208";a="215199721" Received: from nshalmon-mobl.ger.corp.intel.com (HELO localhost) ([10.252.8.146]) by orsmga006.jf.intel.com with ESMTP; 09 Dec 2019 11:47:17 -0800 Date: Mon, 9 Dec 2019 21:47:15 +0200 From: Jarkko Sakkinen To: James Bottomley Cc: "Zhao, Shirley" , Mimi Zohar , Jonathan Corbet , "linux-integrity@vger.kernel.org" , "keyrings@vger.kernel.org" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , 'Mauro Carvalho Chehab' , "Zhu, Bing" , "Chen, Luhai" Subject: Re: One question about trusted key of keyring in Linux kernel. Message-ID: <20191209194715.GD19243@linux.intel.com> References: <1575057916.6220.7.camel@linux.ibm.com> <1575260220.4080.17.camel@linux.ibm.com> <1575267453.4080.26.camel@linux.ibm.com> <1575269075.4080.31.camel@linux.ibm.com> <1575312932.24227.13.camel@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1575312932.24227.13.camel@linux.ibm.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Mon, Dec 02, 2019 at 10:55:32AM -0800, James Bottomley wrote: > blob but it looks like we need to fix the API. I suppose the good news > is given this failure that we have the opportunity to rewrite the API > since no-one else can have used it for anything because of this. The I did successfully run this test when I wrote it 5 years ago: https://github.com/jsakkine-intel/tpm2-scripts/blob/master/keyctl-smoke.sh Given that there is API a way must be found that backwards compatibility is not broken. New format is fine but it must co-exist. /Jarkko