public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Clemens Lang <cllang@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/stunnel] f43: New upstream release 5.80
Date: Fri, 07 Aug 2026 09:29:26 GMT [thread overview]
Message-ID: <178609496675.1.10417124025663014617.rpms-stunnel-4124bf0df81f@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/stunnel
Branch : f43
Commit : 4124bf0df81f957f4ba2eec15bb26d40a9e116a5
Author : Clemens Lang <cllang@redhat.com>
Date : 2026-08-07T11:14:27+02:00
Stats : +3/-3 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/stunnel/c/4124bf0df81f957f4ba2eec15bb26d40a9e116a5?branch=f43
Log:
New upstream release 5.80
* Security bugfixes
- CVE-2026-70368: Fixed an out-of-bounds memory access triggered by
logging attacker-controlled protocol messages longer than 1,024 bytes
(thanks to AISLE Research and Clemens Lang).
- CVE-2026-70367: Fixed a SOCKS server mode bypass of the localhost
destination filter using alternate local-address encodings and
interface-scoped IPv6 destinations (thanks to AISLE Research and
Clemens Lang).
- Restricted Windows GUI/service control pipes to local clients.
* Bugfixes
- Fixed concurrent DTLS handshakes from clients sharing an IP address.
- Fixed version reporting in builds from source.
- Rejected stream-oriented protocol negotiation with the UDP transport
during configuration validation.
- Fixed a TCP stream truncation (thanks to Solomon Jacobs).
- Fixed a transfer() loop (thanks to Solomon Jacobs).
- Fixed log reopening logs without a configured log file.
- Fixed some logged values (thanks to Jose Alf.).
- Fixed some error handling and cleanup issues (thanks to Jose Alf.).
- Fixed OpenSSL applink detection and MSYS2 MinGW builds.
* Features
- Added the "CRLcheckChain" service-level option for opt-in full-chain
CRL verification.
- Added the new 'transport' service-level option to choose between TLS
over TCP and DTLS over UDP.
(cherry picked from commit 1f2abd99d0ff3e74d4aaf06b597f1cfa2b7d2e72)
CVE: CVE-2026-70367
CVE: CVE-2026-70368
Resolves: rhbz#2494485
Signed-off-by: Clemens Lang <cllang@redhat.com>
From-source-git-commit: 5f1195c91efd66e434e98b9d2dd9caa461fdf138
---
diff --git a/sources b/sources
index 4bdacb8..6d9535b 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (stunnel-5.78.tar.gz) = e88abb4a7f39a7ebc4f5d9b8979514659304dac443e192d6cf8675d87ebaa1249677505014de0c685147039437f5b556afc7aa96c70c1621bca3686107ea6b21
-SHA512 (stunnel-5.78.tar.gz.asc) = 10c82ab9c56977a26b2c3d9b4e88c310bcd90116363573c86970aa94ea8ddd0692905abfb4b1fff83e3654a098075d4f7c669b5cf6e26fa01e4c161c927e98ca
+SHA512 (stunnel-5.80.tar.gz) = e07dd8614b8405e5e0cfef3f0ede21735f28efc125f2032f06655f629713e7a8944f1b383f9df5610f41d619feb3cbaf5cf351738e83084cb17fd155e180ffa3
+SHA512 (stunnel-5.80.tar.gz.asc) = 035f2a419235c01e65b58ce93db97bfd47d877da51f5a865a29e72ac68506057ed3d499781e258daf3fb026d415b4301681822a1cdda2a9b69e5c7ad94a0dbc4
diff --git a/stunnel.spec b/stunnel.spec
index 0f79fc1..ea69c00 100644
--- a/stunnel.spec
+++ b/stunnel.spec
@@ -15,7 +15,7 @@
Summary: A TLS-encrypting socket wrapper
Name: stunnel
-Version: 5.78
+Version: 5.80
Release: %autorelease
License: GPL-2.0-or-later WITH stunnel-exception AND MIT
URL: https://www.stunnel.org/
reply other threads:[~2026-08-07 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178609496675.1.10417124025663014617.rpms-stunnel-4124bf0df81f@fedoraproject.org \
--to=cllang@redhat.com \
--cc=git-commits@fedoraproject.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