> Subject: Re: [lng-odp] [API-NEXT PATCH v2 1/7] api: crypto: decouple key
> length from algorithm enumeration
>
> On Wed, Dec 7, 2016 at 3:32 AM, Savolainen, Petri (Nokia - FI/Espoo)
> <petri.savolai...@nokia-bell-labs.com> wrote:
> >
> >> > /**
> &
On Wed, Dec 7, 2016 at 3:32 AM, Savolainen, Petri (Nokia - FI/Espoo)
wrote:
>
>> > /**
>> > + * Cipher algorithm capabilities
>> > + */
>> > +typedef struct odp_crypto_cipher_capa_t {
>> > + /** Key length in bytes */
>> > + uint32_t key_len;
>>
> > /**
> > + * Cipher algorithm capabilities
> > + */
> > +typedef struct odp_crypto_cipher_capa_t {
> > + /** Key length in bytes */
> > + uint32_t key_len;
> > +
> > + /** IV length in bytes */
> > + uint32_t iv_len;
> > +
> > +} odp_crypto_cipher_capa_t;
>
> This
On Mon, Dec 5, 2016 at 2:39 AM, Petri Savolainen
wrote:
> Enumerations for cipher and authentication algorithms grow
> fast if key and digest lengths are included into the enum.
> Decoupled lengths from algorithm names, only exception is
> SHA-2 family of
Enumerations for cipher and authentication algorithms grow
fast if key and digest lengths are included into the enum.
Decoupled lengths from algorithm names, only exception is
SHA-2 family of authentication algorithms which has established
naming convention with digest lengths (SHA-224, SHA-256,