From: "Alex G." <mr.nuke.me@gmail.com>
To: Artem Panfilov <panfilov.artyom@gmail.com>,
Tom Rini <trini@konsulko.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/1] lib/ecdsa: Fix LibreSSL before v2.7.0
Date: Thu, 29 Jul 2021 10:48:30 -0500 [thread overview]
Message-ID: <387c820c-e012-46df-34f8-066fef263706@gmail.com> (raw)
In-Reply-To: <e53b512c-8463-c88b-de28-0756c5427ff1@gmail.com>
Hi Artem
On 7/29/21 9:52 AM, Artem Panfilov wrote:
> On 29.07.2021 15:59, Tom Rini wrote:
>> Well yes, this is part of the question now, is there enough interest in
>> the old version to bother with? The other part of the question is
>> what's being built now that wasn't being built before, and is that a bug
>> or a feature (a less CONFIG-dependent set of tools is good for generic
>> distributions).
>
> OK, if someone else will report the same issue after u-boot release,
> then it should be fixed. Currently, I am okay with my local fix
> by disabling the CONFIG_TOOLS_LIBCRYPTO option.
ECDSA signing was not verified against a libcrypto that old. Given that
signatures are non-deterministic, I doubt we could have a CI test that
says old-libcrypto, known block must equal known signature.
When we added ECDSA, there was not a need to consider old libcrypto
versions, but I also did not pay attention to the #ifdefs in the much
older RSA path. I'm sorry that you had to go through the frustrations of
getting a patch rejected which does something the codebase already does.
I am going to take a look at cleaning up the RSA path. There's no point
in maintaining backwards compatibility if we're not doing it across the
board.
Alex
next prev parent reply other threads:[~2021-07-29 15:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 18:10 [PATCH 1/1] lib/ecdsa: Fix LibreSSL before v2.7.0 Artem Panfilov
2021-07-28 19:16 ` Alex G.
[not found] ` <CAFzqoFjxO8Ox5vCyU_oXc4=a=iKR7NHEY=rgNMppQ5760DL6Kw@mail.gmail.com>
2021-07-28 20:00 ` Alex G.
2021-07-28 20:07 ` Tom Rini
2021-07-28 22:29 ` Artem Panfilov
2021-07-28 22:56 ` Tom Rini
2021-07-28 23:37 ` Artem Panfilov
2021-07-28 23:43 ` Tom Rini
2021-07-29 10:40 ` Artem Panfilov
2021-07-29 12:59 ` Tom Rini
2021-07-29 14:52 ` Artem Panfilov
2021-07-29 15:48 ` Alex G. [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-28 18:04 Artem Panfilov
2021-07-29 5:13 ` Jonathan Gray
2021-07-31 16:59 ` Simon Glass
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=387c820c-e012-46df-34f8-066fef263706@gmail.com \
--to=mr.nuke.me@gmail.com \
--cc=panfilov.artyom@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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