Your message dated Sat, 06 Sep 2025 12:14:57 +0100
with message-id
<165032e5317517556dd7fd8cf24843112a3fb6ac.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 13.1
has caused the Debian Bug report #1112021,
regarding trixie-pu: package strongswan/6.0.1-6+deb13u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1112021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112021
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:strongswan
User: [email protected]
Usertags: pu
Hi release team
I'd like to push a new strongSwan version to Trixie first point release
following a bug report found after the release: #1109942.
There's a bad interaction between the OpenSSL version in Trixie and
strongSwan, and the strongSwan version in Trixie actually switched the
default processing for standard algorithms to the OpenSSL plugin (in
Bookworm it was using "custom" plugins for all the standard algorithms
like AES, ECDSA and stuff like that).
Upstream has identified the cause and fixed it in the 6.0.2 release but
Trixie has 6.0.1. I've backported the two patches in the Trixie version,
the debdiff is attached.
Please authorize an upload of strongswan 6.0.1-6+deb13u1 to Trixie.
Thanks in advance!
Regards,
--
Yves-Alexis
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 13.1
Hi,
Each of the updates referenced by these requests was included in
today's 13.1 point release for trixie.
Regards,
Adam
--- End Message ---
