From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] package/proftpd: security bump version to 1.3.9d
Date: Mon, 31 Aug 2026 00:16:06 +0200 [thread overview]
Message-ID: <20260830221606.33953-1-bernd@kuhls.net> (raw)
https://github.com/proftpd/proftpd/blob/v1.3.9d/NEWS
Version 1.3.9b fixes CVE-2026-44331.
Switched to sha256 tarball hash provided by upstream.
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
package/proftpd/proftpd.hash | 3 ++-
package/proftpd/proftpd.mk | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/package/proftpd/proftpd.hash b/package/proftpd/proftpd.hash
index 9ec632884c..1c81240d81 100644
--- a/package/proftpd/proftpd.hash
+++ b/package/proftpd/proftpd.hash
@@ -1,3 +1,4 @@
+# From https://github.com/proftpd/proftpd/releases/download/v1.3.9d/proftpd-1.3.9d.tar.gz.sha256
+sha256 68b094b1c57c775ad00ef469e9a87783dbbf31a85f98f48faf60becc2e84e4ec proftpd-1.3.9d.tar.gz
# Locally calculated
-sha256 bc3c7c47033ecff29f010efc18315d5906eb942d2e673ebce0138a96f11af0b4 proftpd-1.3.9a.tar.gz
sha256 391a473d755c29b5326fb726326ff3c37e42512f53a8f5789fc310232150bf80 COPYING
diff --git a/package/proftpd/proftpd.mk b/package/proftpd/proftpd.mk
index ba026f5dd1..e3216ed802 100644
--- a/package/proftpd/proftpd.mk
+++ b/package/proftpd/proftpd.mk
@@ -4,7 +4,7 @@
#
################################################################################
-PROFTPD_VERSION = 1.3.9a
+PROFTPD_VERSION = 1.3.9d
PROFTPD_SITE = https://github.com/proftpd/proftpd/archive/v$(PROFTPD_VERSION)
PROFTPD_LICENSE = GPL-2.0+
PROFTPD_LICENSE_FILES = COPYING
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-08-30 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 22:16 Bernd Kuhls [this message]
2026-08-31 19:34 ` [Buildroot] [PATCH 1/1] package/proftpd: security bump version to 1.3.9d Peter Korsgaard
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=20260830221606.33953-1-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
/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