fix for SIGSEGV when using mysql plugin
Bug #1795813 reported by
Jean-Daniel Dupas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
strongswan (Ubuntu) |
Fix Released
|
Medium
|
Christian Ehrhardt |
Bug Description
There is an issue with the mysql plugin that make the server crash reliably on heavy load.
https:/
This issue was just fixed upstream: https:/
Would it be possible to include the fix in the bionic releases ?
Related branches
~paelzer/ubuntu/+source/strongswan:merge-disco-5.7.1-1-lp1806401
Merged
into
ubuntu/+source/strongswan:debian/sid
at
revision 1c90d2e33cc7946059e241de270a5022c0b4d0f0
- Andreas Hasenack: Approve
- Canonical Server: Pending requested
- git-ubuntu developers: Pending requested
-
Diff: 2323 lines (+1744/-90)22 files modifieddebian/changelog (+1317/-0)
debian/control (+122/-6)
debian/ipsec.secrets.proto (+0/-3)
debian/libcharon-extra-plugins.install (+64/-12)
debian/libcharon-standard-plugins.install (+19/-0)
debian/libstrongswan-extra-plugins.install (+55/-0)
debian/libstrongswan.install (+11/-6)
debian/patches/dont-load-kernel-libipsec-plugin-by-default.patch (+11/-0)
debian/patches/lp1795813-mysql-Don-t-release-the-connection-if-transactions-a.patch (+40/-0)
debian/patches/series (+2/-0)
debian/rules (+49/-6)
debian/strongswan-starter.install (+4/-0)
debian/strongswan-starter.postinst (+0/-57)
debian/strongswan-tnc-base.install (+16/-0)
debian/strongswan-tnc-client.install (+5/-0)
debian/strongswan-tnc-ifmap.install (+3/-0)
debian/strongswan-tnc-pdp.install (+3/-0)
debian/strongswan-tnc-server.install (+10/-0)
debian/usr.lib.ipsec.charon (+4/-0)
debian/usr.lib.ipsec.lookip (+2/-0)
debian/usr.lib.ipsec.stroke (+2/-0)
debian/usr.sbin.charon-systemd (+5/-0)
CVE References
Changed in strongswan (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in strongswan (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Christian Ehrhardt (paelzer) |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
If someone can prepare a backport, please follow the steps at https:/ /wiki.ubuntu. com/StableRelea seUpdates# Procedure to have Bionic updated.
All the steps documented there need to be followed. In particular, I'm concerned that we have a test case that can be followed by someone not familiar with the package for SRU verification purposes.