From: Stephan Mueller <smueller@chronox.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH v2 3/5] crypto: AF_ALG -- add setpubkey setsockopt call
Date: Fri, 30 Oct 2015 09:42:27 +0100 [thread overview]
Message-ID: <1977247.RiyifmUyDD@tauon.atsec.com> (raw)
In-Reply-To: <DE14D478-A941-4F5B-A43F-7C6DB51E2CCE@holtmann.org>
Am Freitag, 30. Oktober 2015, 17:16:47 schrieb Marcel Holtmann:
Hi Marcel,
>Hi Stephan,
>
>> For supporting asymmetric ciphers, user space must be able to set the
>> public key. The patch adds a new setsockopt call for setting the public
>> key.
>>
>> Signed-off-by: Stephan Mueller <smueller@chronox.de>
>> ---
>> crypto/af_alg.c | 14 +++++++++++---
>> include/crypto/if_alg.h | 1 +
>> 2 files changed, 12 insertions(+), 3 deletions(-)
>>
>> diff --git a/crypto/af_alg.c b/crypto/af_alg.c
>> index a8e7aa3..bf6528e 100644
>> --- a/crypto/af_alg.c
>> +++ b/crypto/af_alg.c
>> @@ -173,13 +173,16 @@ static int alg_bind(struct socket *sock, struct
>> sockaddr *uaddr, int addr_len) }
>>
>> static int alg_setkey(struct sock *sk, char __user *ukey,
>> - unsigned int keylen)
>> + unsigned int keylen, bool pubkey)
>> {
>>
>> struct alg_sock *ask = alg_sk(sk);
>> const struct af_alg_type *type = ask->type;
>> u8 *key;
>> int err;
>>
>> + if (pubkey && !type->setpubkey)
>> + return -EOPNOTSUPP;
>> +
>>
>> key = sock_kmalloc(sk, keylen, GFP_KERNEL);
>> if (!key)
>>
>> return -ENOMEM;
>>
>> @@ -188,7 +191,10 @@ static int alg_setkey(struct sock *sk, char __user
>> *ukey,>
>> if (copy_from_user(key, ukey, keylen))
>>
>> goto out;
>>
>> - err = type->setkey(ask->private, key, keylen);
>> + if (pubkey)
>> + err = type->setpubkey(ask->private, key, keylen);
>> + else
>> + err = type->setkey(ask->private, key, keyless);
>
>why is this kind of hackery needed? Why not just introduce alg_setpubkey to
>keep this a lot cleaner.
You are fully correct. I wanted to spare a re-implementation of the setkey
function. But instead of that hack, having something like the following would
be much cleaner:
setkey_common() {
...
heavy lifting
...
}
setpubkey() {
setkey_common(type->setpubkey)
}
setkey() {
setkey_common(type->setkey)
}
>> out:
>> sock_kzfree_s(sk, key, keylen);
>>
>> @@ -212,12 +218,14 @@ static int alg_setsockopt(struct socket *sock, int
>> level, int optname,>
>> switch (optname) {
>>
>> case ALG_SET_KEY:
>> + case ALG_SET_PUBKEY:
>> if (sock->state == SS_CONNECTED)
>>
>> goto unlock;
>>
>> if (!type->setkey)
>>
>> goto unlock;
>>
>> - err = alg_setkey(sk, optval, optlen);
>> + err = alg_setkey(sk, optval, optlen,
>> + (optname == ALG_SET_PUBKEY) ? true : false);
>>
>> break;
>
>Same here. Why not give ALG_SET_PUBKEY a separate case statement. Especially
>since you have to check type->setkey vs type->setpubkey.
Same here.
>> case ALG_SET_AEAD_AUTHSIZE:
>> if (sock->state == SS_CONNECTED)
>>
>> diff --git a/include/crypto/if_alg.h b/include/crypto/if_alg.h
>> index 018afb2..ca4dc72 100644
>> --- a/include/crypto/if_alg.h
>> +++ b/include/crypto/if_alg.h
>> @@ -49,6 +49,7 @@ struct af_alg_type {
>>
>> void *(*bind)(const char *name, u32 type, u32 mask);
>> void (*release)(void *private);
>> int (*setkey)(void *private, const u8 *key, unsigned int keylen);
>>
>> + int (*setpubkey)(void *private, const u8 *key, unsigned int keylen);
>>
>> int (*accept)(void *private, struct sock *sk);
>> int (*setauthsize)(void *private, unsigned int authorize);
>
>Regards
>
>Marcel
Thanks.
Ciao
Stephan
next prev parent reply other threads:[~2015-10-30 8:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 10:44 [PATCH v2 0/5] crypto: add algif_akcipher user space API Stephan Mueller
2015-10-18 10:45 ` [PATCH v2 1/5] MPI: fix off by one in mpi_read_raw_from_sgl Stephan Mueller
2015-10-19 23:25 ` Tadeusz Struk
2015-10-20 14:20 ` Herbert Xu
2015-10-18 10:46 ` [PATCH v2 2/5] crypto: AF_ALG -- add sign/verify API Stephan Mueller
2015-10-18 10:47 ` [PATCH v2 3/5] crypto: AF_ALG -- add setpubkey setsockopt call Stephan Mueller
2015-10-30 8:16 ` Marcel Holtmann
2015-10-30 8:42 ` Stephan Mueller [this message]
2015-10-18 10:48 ` [PATCH v2 4/5] crypto: AF_ALG -- add asymmetric cipher interface Stephan Mueller
2015-10-18 10:49 ` [PATCH v2 5/5] crypto: algif_akcipher - enable compilation Stephan Mueller
2015-10-19 1:32 ` [PATCH v2 0/5] crypto: add algif_akcipher user space API Herbert Xu
2015-10-19 7:14 ` Stephan Mueller
2015-10-19 7:27 ` Herbert Xu
2015-10-27 4:54 ` Marcel Holtmann
2015-10-27 9:12 ` Stephan Mueller
2015-10-27 9:19 ` David Woodhouse
2015-10-27 10:50 ` Stephan Mueller
2015-10-27 23:15 ` David Woodhouse
2015-10-27 23:35 ` Stephan Mueller
2015-10-27 23:43 ` David Woodhouse
2015-10-27 23:47 ` Stephan Mueller
2015-10-28 0:37 ` David Woodhouse
2015-10-28 1:18 ` Stephan Mueller
2015-10-28 1:36 ` David Woodhouse
2015-10-28 0:46 ` Marcel Holtmann
2015-10-28 1:29 ` Stephan Mueller
2015-10-28 2:56 ` Marcel Holtmann
2015-10-28 10:12 ` Stephan Mueller
2015-10-27 15:16 ` Tadeusz Struk
2015-12-14 18:06 ` Tadeusz Struk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1977247.RiyifmUyDD@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®