From: Yann Droneaud <ydroneaud@opteya.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Alexandru Gagniuc <mr.nuke.me@gmail.com>,
"Chan, Donald" <hoiho@lab126.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH] lib: rsa: use actual OpenSSL 1.1.0 EVP MD API
Date: Wed, 2 Mar 2022 20:38:36 +0100 [thread overview]
Message-ID: <06d9cb69-413a-565b-baf8-c53610495293@opteya.com> (raw)
In-Reply-To: <CAPnjgZ2NuNrPg0jDc2FcfR46qhApFzBS2Z7vKD+w5nvGAupqYw@mail.gmail.com>
Hi,
Le 02/03/2022 à 02:10, Simon Glass a écrit :
> On Tue, 1 Mar 2022 at 08:12, Yann Droneaud <ydroneaud@opteya.com> wrote:
>> Since OpenSSL 1.1.0, EVP_MD_CTX_create() is EVP_MD_CTX_new()
>> EVP_MD_CTX_destroy() is EVP_MD_CTX_free()
>> EVP_MD_CTX_init() is EVP_MD_CTX_reset()
>>
>> As there's no need to reset a newly created EVP_MD_CTX, moreover
>> EVP_DigestSignInit() does the reset, thus call to EVP_MD_CTX_init()
>> can be dropped.
>> As there's no need to reset an EVP_MD_CTX before it's destroyed,
>> as it will be reset by EVP_MD_CTX_free(), call to EVP_MD_CTX_reset()
>> is not needed and can be dropped.
> Do we still need to support the old version?
No, see
https://source.denx.de/u-boot/u-boot/-/commit/fe68a67a5f11991146f47c2975a4e1156355a92c
Regards
--
Yann Droneaud
OPTEYA
next prev parent reply other threads:[~2022-03-02 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 15:12 [PATCH] lib: rsa: use actual OpenSSL 1.1.0 EVP MD API Yann Droneaud
2022-03-02 1:10 ` Simon Glass
2022-03-02 7:57 ` Heinrich Schuchardt
2022-03-02 19:38 ` Yann Droneaud [this message]
2022-03-05 16:36 ` Tom Rini
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=06d9cb69-413a-565b-baf8-c53610495293@opteya.com \
--to=ydroneaud@opteya.com \
--cc=hoiho@lab126.com \
--cc=mkl@pengutronix.de \
--cc=mr.nuke.me@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.