[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6378539.AB6lySjknM@tachyon.chronox.de>
Date: Mon, 10 Nov 2014 02:41:56 +0100
From: Stephan Mueller <smueller@...onox.de>
To: Tadeusz Struk <tstruk@...il.com>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
Marek Vasut <marex@...x.de>,
Jason Cooper <cryptography@...edaemon.net>,
Grant Likely <grant.likely@...retlab.ca>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH v2 01/11] crypto: Documentation - crypto API high level spec
Am Mittwoch, 5. November 2014, 18:15:12 schrieb Tadeusz Struk:
Hi Tadeusz,
> Hi,
>
> On 11/02/2014 12:35 PM, Stephan Mueller wrote:
> > + * type:
> > + - blkcipher for symmetric block ciphers
>
> blkcipher for synchronous block ciphers
>
> > + - ablkcipher for asymmetric block ciphers
>
> ablkcipher for asynchronous block ciphers
>
> > + - cipher for single block ciphers that may be used with an
> > + additional template
> > + - shash for symmetric message digest
>
> shash for synchronous message digest
>
> > + - ahash for asymmetric message digest
>
> ahash for asynchronous message digest
>
> T.
Thanks a lot for this hint: I do not know how often I said "symmetric" or
"asymmetric" when in fact I meant synchronous and asynchronous....
Maybe I spent too much time in the crypto arena ;-)
--
Ciao
Stephan
--
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