From: David Howells Subject: Re: [PATCH 08/21] KEYS: Add signature verification facility [ver #3] Date: Wed, 18 Jan 2012 15:13:44 +0000 Message-ID: <29789.1326899624@redhat.com> References: <20111202184229.21874.25782.stgit@warthog.procyon.org.uk> <20111202184406.21874.65285.stgit@warthog.procyon.org.uk> <26123.1326889583@redhat.com> Cc: dhowells@redhat.com, keyrings@linux-nfs.org, linux-crypto@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, zohar@linux.vnet.ibm.com, arjan.van.de.ven@intel.com, alan.cox@intel.com To: "Kasatkin, Dmitry" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45402 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757647Ab2ARPOM (ORCPT ); Wed, 18 Jan 2012 10:14:12 -0500 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: Kasatkin, Dmitry wrote: > Yes. it is clear... > Would it be possible to have pass data (uncompleted) hash? Yes, provided it's not finalised. Also, with the current code it would have to be a shash, but I think I should be able to support the passing in of an async hash by exporting the state from that and importing the state into a shash using the crypto layer export and import functions. David