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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALLzPKZ8voNPoyfTznq+_gPThbW6rqdGKLBztZ8qkesM2qtziQ@mail.gmail.com>
Date:	Wed, 18 Jan 2012 17:20:40 +0200
From:	"Kasatkin, Dmitry" <dmitry.kasatkin@...el.com>
To:	David Howells <dhowells@...hat.com>
Cc:	keyrings@...ux-nfs.org, linux-crypto@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, zohar@...ux.vnet.ibm.com,
	arjan.van.de.ven@...el.com, alan.cox@...el.com
Subject: Re: [PATCH 08/21] KEYS: Add signature verification facility [ver #3]

On Wed, Jan 18, 2012 at 5:13 PM, David Howells <dhowells@...hat.com> wrote:
> Kasatkin, Dmitry <dmitry.kasatkin@...el.com> 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.
>

I thought about export/import.
But I think export/Import is hash driver implementation specific...
Cannot use ahash state for shash...

As you said in repose to later patch, you could provide some function  to
build a final metadata buffer out of signature to finalize the hash...

- Dmitry


> David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ