[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c5bfefc4653226e24195f5c87499c3292ecc15f5.camel@kernel.org>
Date: Wed, 26 Apr 2023 21:27:00 +0300
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Roberto Sassu <roberto.sassu@...weicloud.com>, dhowells@...hat.com,
dwmw2@...radead.org, herbert@...dor.apana.org.au,
davem@...emloft.net, ast@...nel.org, daniel@...earbox.net,
andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org,
yhs@...com, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
rostedt@...dmis.org, mhiramat@...nel.org, mykolal@...com,
shuah@...nel.org
Cc: linux-kernel@...r.kernel.org, keyrings@...r.kernel.org,
linux-crypto@...r.kernel.org, bpf@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org,
Roberto Sassu <roberto.sassu@...wei.com>
Subject: Re: [RFC][PATCH 3/6] verification: Introduce verify_umd_signature()
and verify_umd_message_sig()
On Wed, 2023-04-26 at 21:25 +0300, Jarkko Sakkinen wrote:
> On Wed, 2023-04-26 at 13:42 +0200, Roberto Sassu wrote:
> > On Wed, 2023-04-26 at 03:28 +0300, Jarkko Sakkinen wrote:
> > > On Tue Apr 25, 2023 at 8:35 PM EEST, Roberto Sassu wrote:
> > > > From: Roberto Sassu <roberto.sassu@...wei.com>
> > > >
> > > > Introduce verify_umd_signature() and verify_umd_message_sig(), to verify
> > > > UMD-parsed signatures from detached data. It aims to be used by kernel
> > > > subsystems wishing to verify the authenticity of system data, with
> > > > system-defined keyrings as trust anchor.
> > >
> > > UMD is not generic knowledge. It is a term coined up in this patch set
> > > so please open code it to each patch.
> >
> > Yes, Linus also commented on this:
> >
> > https://lwn.net/ml/linux-kernel/CAHk-=wihqhksXHkcjuTrYmC-vajeRcNh3s6eeoJNxS7wp77dFQ@mail.gmail.com/
> >
> > I will check if the full name is mentioned at least once. So far, it
> > seems that using umd for function names should be ok.
>
> Also: "UMD-based parser for the asymmetric key type"
>
> It is a tautology:
>
> UMD is based on parser which based on UMD.
>
> I.e. makes no sense.
>
> Everyone hates three letter acronyms so I would consider not
> inventing a new one out of the void.
>
> So the corrective step would be to rename Kconfig flags as
> USER_ASYMMETRIC_KEY_PARSER and USER_ASYMMETRIC_SIGNATURE_PARSER.
(or along the lines)
BR, Jarkko
Powered by blists - more mailing lists