From: Tom Rini <trini@konsulko.com>
To: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Heiko Schocher <hs@denx.de>,
Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Anastasiia Lukianenko <anastasiia_lukianenko@epam.com>,
Andrii Anisov <andrii_anisov@epam.com>,
Aswath Govindraju <a-govindraju@ti.com>,
Bin Meng <bmeng.cn@gmail.com>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Joel Stanley <joel@jms.id.au>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Masahisa Kojima <masahisa.kojima@linaro.org>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
Sean Anderson <seanga2@gmail.com>, Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCH v5 1/8] lib: add crypt subsystem
Date: Fri, 23 Jul 2021 14:52:58 -0400 [thread overview]
Message-ID: <20210723185258.GC9379@bill-the-cat> (raw)
In-Reply-To: <20210708135740.3078100-2-jaeckel-floss@eyet-services.de>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
On Thu, Jul 08, 2021 at 03:57:33PM +0200, Steffen Jaeckel wrote:
> Add the basic functionality required to support the standard crypt
> format.
> The files crypt-sha256.c and crypt-sha512.c originate from libxcrypt and
> their formatting is therefor retained.
> The integration is done via a crypt_compare() function in crypt.c.
>
> ```
> libxcrypt $ git describe --long --always --all
> tags/v4.4.17-0-g6b110bc
> ```
>
> Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
> Reviewed-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Heiko Schocher <hs@denx.de>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-07-23 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 13:57 [PATCH v5 0/8] common: Introduce crypt-style password support Steffen Jaeckel
2021-07-08 13:57 ` [PATCH v5 1/8] lib: add crypt subsystem Steffen Jaeckel
2021-07-23 18:52 ` Tom Rini [this message]
2021-07-08 13:57 ` [PATCH v5 2/8] lib: wrap crypt API to hide errno usage Steffen Jaeckel
2021-07-23 18:53 ` Tom Rini
2021-07-08 13:57 ` [PATCH v5 3/8] common: integrate crypt-based passwords Steffen Jaeckel
2021-07-23 18:53 ` Tom Rini
2021-07-08 13:57 ` [PATCH v5 4/8] common: Rename macro appropriately Steffen Jaeckel
2021-07-23 18:53 ` Tom Rini
2021-07-08 13:57 ` [PATCH v5 5/8] common: allow disabling of timeout for password entry Steffen Jaeckel
2021-07-23 18:53 ` Tom Rini
2021-07-08 13:57 ` [PATCH v5 6/8] common: add AUTOBOOT_FLUSH_STDIN option Steffen Jaeckel
2021-07-23 18:53 ` Tom Rini
2021-07-08 13:57 ` [PATCH v5 7/8] common: add support to fallback to plain SHA256 Steffen Jaeckel
2021-07-23 18:53 ` Tom Rini
2021-07-08 13:57 ` [PATCH v5 8/8] test: add first autoboot unit tests Steffen Jaeckel
2021-07-23 18:53 ` 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=20210723185258.GC9379@bill-the-cat \
--to=trini@konsulko.com \
--cc=a-govindraju@ti.com \
--cc=anastasiia_lukianenko@epam.com \
--cc=andrii_anisov@epam.com \
--cc=bmeng.cn@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=hs@denx.de \
--cc=jaeckel-floss@eyet-services.de \
--cc=joel@jms.id.au \
--cc=m.szyprowski@samsung.com \
--cc=masahisa.kojima@linaro.org \
--cc=mr.nuke.me@gmail.com \
--cc=patrick.delaunay@foss.st.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=t-kristo@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox