Thank you for investigating this issue.
I'm not sure there's enough justification to put the fix into Ubuntu
directly right now. If someone familiar with the protocol and code base
can provide more technical detail on why this is a production-ready fix,
or if upstream patch it (indicating that it is suitable for production)
then I think that would change. Or, of course, if an Ubuntu developer
disagrees with me.
For now, it sounds like the best venue for this workaround would be a
patched package in a PPA for users to opt to install if they
specifically need this workaround.
I'm going to mark this bug Won't Fix for now, in order that it remains
searchable and doesn't expire. But please do comment and change the
status back to New if more information becomes available or the
situation changes (eg. upstream picks up the fix). If an upstream bug
gets filed, please link to it too.
** Changed in: ipsec-tools (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipsec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1016639
Title:
LT2P VPN connection issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/1016639/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
