linux-kernel - Re: ahash alg that does not implement import/export failed to register

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20160108095454.GB3472@gondor.apana.org.au>
Date:	Fri, 8 Jan 2016 18:54:54 +0900
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Tom Lendacky <thomas.lendacky@....com>
Cc:	Tim Chen <tim.c.chen@...ux.intel.com>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-crypto <linux-crypto@...r.kernel.org>,
	"megha.dey" <megha.dey@...el.com>
Subject: Re: ahash alg that does not implement import/export failed to
 register

On Thu, Jan 07, 2016 at 08:49:31AM -0600, Tom Lendacky wrote:
> 
> Is it expected that import and export should work across algorithm
> implementations (eg. export sha1 state from hardware driver and import
> into sha1-generic algorithm)?  Or is the state purely meant for use by
> the driver only? I see a few hardware drivers exporting/importing
> to/from sha1_state and sha256_state and that is what prompts this
> question.

For algorithms in general there is no requirement for the states
to be exported in a particular format.  For certain special cases
such as crc32c we do require a specific format but you don't have
to worry about this for SHA.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt