strongswan service file should be upstream one
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
strongswan (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Hello,
Ubuntu ships a custom /lib/systemd/
Upstream ships a far simpler systemd file:
[Service]
ExecStart=
StandardOutput=
Stop action is handled directly by systemd. No PID file handling is needed. However, since start is done with --nofork, the unit is ready while strongSwan may not be started yet. However, looking at the source code of strongSwan, I see it forks quite early, before charon is started. I would suggest to keep upstream service file (or patch it like Debian to add "reload" action).
CVE References
Changed in strongswan (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
Thanks for taking the time to file a bug! Can you specify what release of ubuntu you are running and what version of strongswan you are seeing this issue?
I took a look at the version in Debain unstable and Bionic and they looked similar.