Hi,
I come by cleaning up some old bugs and this one is a sad one to see.
It wasn't able to be acted on when I looked at is last time. Then Joseph was so
kind to offer his help, but neither myself nor anyone else in the Team saw
that. Therefore this was not brought back onto anyone's todo-list an
Is this bug going to be fixed in Xenial? I can test in Xenial. If it
is not going to be fixed in Xenial, is there a way to load StrongSwan >
5.5.0 into Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
There is one thing why this doesn't qualify for server-next yet, which
is that it will be hard to reproduce without the complex associated
setup.
@Link - will you be able and willing to test and verify this on xenial
and yakkety if one will prepare a package with backports?
If you can I think thi
Since we merged 5.5 in zesty it was forgotten to mention it being fixed
for a while.
** Also affects: strongswan (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: strongswan (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: strongswan (Ubuntu
Now things are kind of ready for an SRU, the patch to be backported will be
https://wiki.strongswan.org/projects/strongswan/repository/revisions/1b4e7fe1e83b685b79d87dba5df42b6a852845f1/diff/src/libcharon/sa/ikev1/task_manager_v1.c
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: strongswan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608302
Title:
