From: Vitaly Chikunov <vt@altlinux.org>
To: keyrings@vger.kernel.org, Jarkko Sakkinen <jarkko@kernel.org>,
David Howells <dhowells@redhat.com>,
linux-crypto@vger.kernel.org, linux-integrity@vger.kernel.org,
Eric Biggers <ebiggers@kernel.org>
Cc: Stefan Berger <stefanb@linux.ibm.com>
Subject: Re: [RFC PATCH] KEYS: Double max_size to make keyctl pkey_verify work
Date: Thu, 3 Feb 2022 01:38:06 +0300 [thread overview]
Message-ID: <20220202223806.bcfsjtr472kl3jj3@altlinux.org> (raw)
In-Reply-To: <20220202212437.mlj4cta4voqiqfpf@altlinux.org>
On Thu, Feb 03, 2022 at 12:24:37AM +0300, Vitaly Chikunov wrote:
> Stefan,
>
> On Wed, Feb 02, 2022 at 07:55:43AM -0500, Stefan Berger wrote:
> > On 2/2/22 01:59, Vitaly Chikunov wrote:
> > > Rarely used `keyctl pkey_verify' can verify raw signatures, but was
> > > failing, because ECDSA/EC-RDSA signature sizes are twice key sizes which
> > > does not pass in/out sizes check in keyctl_pkey_params_get_2.
> > > This in turn because these values cannot be distinguished by a single
> > > `max_size' callback return value.
> > > Also, `keyctl pkey_query` displays incorrect `max_sig_size' about these
> > > algorithms.
> > >
> > > Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
> >
> > How do you use pkey_query?
> >
> > $ keyctl padd asymmetric testkey %keyring:test < cert.der
> > 385037223
>
> It should be (for RSA key):
>
> keyctl pkey_query 385037223 0 enc=pkcs1 hash=sha256
>
> `0` is placeholder for a password.
>
> For example, I generated keys with your eckey-testing/generate.sh, and
> pkey_query after this patch is applied:
>
> # keyctl padd asymmetric "" @u < ecdsa-ca/ca.crt.der
> 66509339
> # keyctl pkey_query 66509339 0 enc=x962 hash=sha256
> key_size=256
> max_data_size=64
> max_sig_size=64
> max_enc_size=32
> max_dec_size=32
I just thought, we can also set these to 0 if encrypt/decrypt is not
enabled. Currently, there is no way to detect that encrypt is not
possible, except by extending that if (strcmp...), but if we going to
have it, why not correct other info too?
Thanks,
> encrypt=y
> decrypt=n
> sign=n
> verify=y
>
> W/o patch max_data_size= and max_sig_size= will be 32.
>
> Thanks,
>
> > $ keyctl pkey_query 385037223 ''
> > Password passing is not yet supported
> > $ keyctl pkey_query 385037223
> > Format:
> > keyctl --version
> > keyctl add <type> <desc> <data> <keyring>
> > [...]
> >
> > $ keyctl unlink 385037223
> > 1 links removed
> >
next prev parent reply other threads:[~2022-02-02 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 6:59 [RFC PATCH] KEYS: Double max_size to make keyctl pkey_verify work Vitaly Chikunov
2022-02-02 12:55 ` Stefan Berger
2022-02-02 21:24 ` Vitaly Chikunov
2022-02-02 22:38 ` Vitaly Chikunov [this message]
2022-02-03 3:42 ` Stefan Berger
2022-02-03 0:07 ` Vitaly Chikunov
2022-02-20 23:31 ` Jarkko Sakkinen
2022-02-03 3:15 ` Stefan Berger
2022-02-03 3:34 ` Vitaly Chikunov
2022-02-20 23:29 ` Jarkko Sakkinen
2022-02-21 2:43 ` Vitaly Chikunov
2022-02-25 19:47 ` Stefan Berger
2022-02-20 23:25 ` Jarkko Sakkinen
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=20220202223806.bcfsjtr472kl3jj3@altlinux.org \
--to=vt@altlinux.org \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).