Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1401533
| From | Tadeusz Struk <tadeusz.struk@intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH RESEND v5 6/6] crypto: AF_ALG - add support for key_id |
| Date | 2016-05-16 16:30 +0200 |
| Message-ID | <rzrGX-892-23@gated-at.bofh.it> (permalink) |
| References | <rvxBf-6mz-3@gated-at.bofh.it> <rvxBg-6mz-27@gated-at.bofh.it> <ryuQy-59K-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Mat, On 05/13/2016 04:32 PM, Mat Martineau wrote: > >> + params.data_len = req->src_len; >> + params.enc_len = req->dst_len; Thanks for info. I have sent an update for this. > > The params member names have changed (now in_len and out_len). >> + ret = encrypt_blob(¶ms, in, out); > > The encrypt function for the key can now be called with params.key->type->asym_eds_op(). This also allows you to factor out the duplication in asym_key_encrypt, asym_key_decrypt, and asym_key_sign. See keyctl_pkey_e_d_s() in keyctl_pkey.c > >> +static int asym_key_verify(const struct key *key, struct akcipher_request *req) > ... >> + ret = verify_signature(key, NULL, &sig); > > key->type->asym_verify_signature() is available as well. Since these operation will be triggered from userspace I think it's better to use the official interface as defined in crypto/public_key.h instead of direct calls. Some operation may not be implemented for a given key type and the official interface performs necessary checks. Thanks, -- TS
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH RESEND v5 6/6] crypto: AF_ALG - add support for key_id Mat Martineau <mathew.j.martineau@linux.intel.com> - 2016-05-14 01:40 +0200 Re: [PATCH RESEND v5 6/6] crypto: AF_ALG - add support for key_id Tadeusz Struk <tadeusz.struk@intel.com> - 2016-05-16 16:30 +0200
csiph-web