IKEv1/XAuth connection to Dell SonicWall appliance fails

[Link Porterfield]

https://wiki.strongswan.org/issues/1434

This already been fixed upstream in 5.5.0
https://wiki.strongswan.org/versions/62

Description: Ubuntu 16.04.1 LTS
Release: 16.04

strongswan:
  Installed: 5.3.5-1ubuntu3
  Candidate: 5.3.5-1ubuntu3
  Version table:
 *** 5.3.5-1ubuntu3 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status

I expected connection to complete.

Connection terminated instead. See https://wiki.strongswan.org/issues/1434 for more details.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt  (paelzer)]

Since we merged 5.5 in zesty it was forgotten to mention it being fixed for a while.

[Christian Ehrhardt  (paelzer)]

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

[Christian Ehrhardt  (paelzer)]

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 this is good for server-next, if not I'm even leaning towards unsubscribing ubuntu-server since none will be able to verify which is a prereq for SRU activity.

[Joseph Huber (huber-joseph)]

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?

[Christian Ehrhardt  (paelzer)]

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 and essentially died by inactivity :-/

Nowadays the answer is simple in that Xenial is in ESM and an non-security issue like this won't be fixed anymore. It also lacked further activity / more bug reports of the same kind to make it more important/seen.
Hmm, all that sounds like excuses, we missed the update and I have to beg your pardon.
Still from today's POV Won't Fix is the only right status to set this to.

P.S. FYI Nowadays we have an improved triage process for server bugs in place and such an update will no more be missed. And gladly on cleanup only very few old cases look like that. Still feeling bad about this one ...