From: Tom Rini <trini@konsulko.com>
To: Jerome Forissier <jerome.forissier@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>, u-boot@lists.denx.de
Subject: Re: [PATCH 0/3] net: use strnstr() for lwip_strnstr()
Date: Mon, 20 Jan 2025 14:54:00 -0600 [thread overview]
Message-ID: <20250120205400.GF3476@bill-the-cat> (raw)
In-Reply-To: <173740634466.2858231.5892096095947475294.b4-ty@konsulko.com>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
On Mon, Jan 20, 2025 at 02:52:24PM -0600, Tom Rini wrote:
> On Sat, 04 Jan 2025 00:21:15 +0100, Heinrich Schuchardt wrote:
>
> > Using strstr() instead of strnstr() creates a security concern.
> >
> > * Implement missing library function strnstr() and add unit tests.
> > * Use it for lwIP.
> >
> > Heinrich Schuchardt (3):
> > lib: implement strnstr()
> > test: unit tests for strstr() and strnstr()
> > net: use strnstr() for lwip_strnstr()
> >
> > [...]
>
> Applied to u-boot/master, thanks!
This was premature, sorry, I need to re-test this in Azure before
pushing.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2025-01-20 20:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 23:21 [PATCH 0/3] net: use strnstr() for lwip_strnstr() Heinrich Schuchardt
2025-01-03 23:21 ` [PATCH 1/3] lib: implement strnstr() Heinrich Schuchardt
2025-01-06 7:44 ` Jerome Forissier
2025-01-06 10:14 ` Rasmus Villemoes
2025-01-06 10:22 ` Jerome Forissier
2025-01-03 23:21 ` [PATCH 2/3] test: unit tests for strstr() and strnstr() Heinrich Schuchardt
2025-01-09 7:53 ` Ilias Apalodimas
2025-01-03 23:21 ` [PATCH 3/3] net: use strnstr() for lwip_strnstr() Heinrich Schuchardt
2025-01-06 7:50 ` Jerome Forissier
2025-01-21 1:05 ` Tom Rini
2025-01-21 2:18 ` Heinrich Schuchardt
2025-01-21 2:33 ` Tom Rini
2025-01-20 20:52 ` [PATCH 0/3] " Tom Rini
2025-01-20 20:54 ` Tom Rini [this message]
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=20250120205400.GF3476@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox