Commit ebbcf336 authored by Herbert Xu's avatar Herbert Xu

crypto: talitos - Use proper form for algorithm driver names

The name authenc(hmac(sha1-talitos),cbc(aes-talitos)) is potentially
ambiguous since it could also mean using the generic authenc template
on hmac(sha1-talitos) and cbc(aes-talitos).  In general, parentheses
should be reserved for templates that spawn algorithms.

This patches changes it to the form authenc-hmac-sha1-cbc-aes-talitos.
Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
parent 70bcaca7
......@@ -1144,7 +1144,7 @@ static struct talitos_alg_template driver_algs[] = {
/* single-pass ipsec_esp descriptor */
{
.name = "authenc(hmac(sha1),cbc(aes))",
.driver_name = "authenc(hmac(sha1-talitos),cbc(aes-talitos))",
.driver_name = "authenc-hmac-sha1-cbc-aes-talitos",
.blocksize = TALITOS_AES_MIN_BLOCK_SIZE,
.aead = {
.setkey = aead_authenc_setkey,
......@@ -1166,7 +1166,7 @@ static struct talitos_alg_template driver_algs[] = {
},
{
.name = "authenc(hmac(sha1),cbc(des3_ede))",
.driver_name = "authenc(hmac(sha1-talitos),cbc(3des-talitos))",
.driver_name = "authenc-hmac-sha1-cbc-3des-talitos",
.blocksize = TALITOS_3DES_MIN_BLOCK_SIZE,
.aead = {
.setkey = aead_authenc_setkey,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment