From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 270E83976BB for ; Mon, 30 Mar 2026 20:14:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774901685; cv=none; b=CMfXkH/r+qcDanqAcShmR8Z6kRbJk6qj1IvdE8e4Cd5iTzjp6HXbXDhbN2EZ6QnYtLIB9qwOFjMfKYnxBTIOgHkLbl85+S1QK7sefTF8QXg7dymh0b35qCPQmPW9e0q7NSUBuGUcPK+PrbeXm2i8rVmQvRsZOf3OUI1OXg2vBhE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774901685; c=relaxed/simple; bh=R1pwynaUgdRNgwi51uAR6jOtIkYi7AVrXxJDFaXkJh4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=DMbVNPJCFsZqhxOgazOj9wDEYB3lbH/7UQ+FvVVbZD5sH9wb9iuQaSyobat+mskjStn/s5eLCEU+Iev035ARtll+lk7lXxswHtJbqKUmkbjeIZn9MhB0r1W/a99YZOUihfJOwsVeWemXahvM63ZgZMDZHig1/CDCu+fATqei0pU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=RoXe/XtP; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="RoXe/XtP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9E6C0C4CEF7; Mon, 30 Mar 2026 20:14:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774901684; bh=R1pwynaUgdRNgwi51uAR6jOtIkYi7AVrXxJDFaXkJh4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RoXe/XtPnlKlcGuJVUli+flPMw9Uxht+mTZxi25g1tonWQrIZVC6LgcnmWzWFWDW2 tirkNFjtenNxxOPjFuIykvi+kABfgYNI6B8bOpOI0RKxAaA1a1G3UFK0zPIz82m8AD XOhDZDwP+sVYWXusA1RXCrTTF58Da6TwcH8rS3TDIYXF+hdQtFiXQq7Uag/sPAebjl LYKSmKz2hbQ55iKX9NWVTEWhM7txw+G+sZ78npwiOOigATTXmg8Qw1Pnbi8U5NoYhv L/dih5KUb/cfbJ3evSuAdyRwpC8F7as9uQz0ot+Pk6tgmA7oGIv1mcPPEbxu9olad9 8Fp8iCE4NLJug== Date: Mon, 30 Mar 2026 13:13:36 -0700 From: Eric Biggers To: Mimi Zohar Cc: linux-integrity@vger.kernel.org, Stefan Berger Subject: Re: [PATCH 1/3] ima: Define asymmetric_verify_v3() to verify IMA sigv3 signatures Message-ID: <20260330201336.GE4303@sol> References: <20260324203929.2475782-1-zohar@linux.ibm.com> <20260324203929.2475782-2-zohar@linux.ibm.com> Precedence: bulk X-Mailing-List: linux-integrity@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260324203929.2475782-2-zohar@linux.ibm.com> On Tue, Mar 24, 2026 at 04:39:27PM -0400, Mimi Zohar wrote: > + * IMA signature version 3 disambiguates the data that is signed by > + * indirectly signing the hash of the ima_file_id structure data. The right way to think about it is that it's the ima_file_id itself that is being signed and verified, and taking the hash of it is only a workaround for legacy algorithms that can only sign and verify hashes. With modern algorithms like Ed25519 and ML-DSA that accept arbitrary-length messages, that workaround won't be needed. - Eric