From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: "Claude Opus 4.6 (1M context)" <noreply@anthropic.com>
Subject: Re: [PATCH 0/4] tftp: fix buffer overflows
Date: Fri, 17 Apr 2026 12:40:21 +0200 [thread overview]
Message-ID: <177642242118.157093.17397729672260000137.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260402-net-tftp-buffer-overflows-v1-0-0a18aa8ea19e@pengutronix.de>
On Thu, 02 Apr 2026 09:21:18 +0200, Sascha Hauer wrote:
> This adds more checks on incoming network data to prevent buffer
> overflows.
>
>
Applied, thanks!
[1/4] fs: tftp: prevent packet buffer overflow from long filenames
https://git.pengutronix.de/cgit/barebox/commit/?id=85eacc30b21f (link may not be stable)
[2/4] fs: tftp: fix OACK option parsing bounds check
https://git.pengutronix.de/cgit/barebox/commit/?id=a0ba8b517861 (link may not be stable)
[3/4] fs: tftp: reject OACK with blocksize of zero
https://git.pengutronix.de/cgit/barebox/commit/?id=0e3e6e737f6f (link may not be stable)
[4/4] fs: tftp: use bounded format for TFTP error message debug print
https://git.pengutronix.de/cgit/barebox/commit/?id=2fb15473263a (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-04-17 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 7:21 Sascha Hauer
2026-04-02 7:21 ` [PATCH 1/4] fs: tftp: prevent packet buffer overflow from long filenames Sascha Hauer
2026-04-17 9:14 ` Ahmad Fatoum
2026-04-02 7:21 ` [PATCH 2/4] fs: tftp: fix OACK option parsing bounds check Sascha Hauer
2026-04-17 9:28 ` Ahmad Fatoum
2026-04-02 7:21 ` [PATCH 3/4] fs: tftp: reject OACK with blocksize of zero Sascha Hauer
2026-04-17 9:32 ` Ahmad Fatoum
2026-04-02 7:21 ` [PATCH 4/4] fs: tftp: use bounded format for TFTP error message debug print Sascha Hauer
2026-04-17 9:42 ` Ahmad Fatoum
2026-04-17 10:40 ` Sascha Hauer [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=177642242118.157093.17397729672260000137.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=noreply@anthropic.com \
/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