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
Have Red Hat patched their stable release with this fix? I'm wondering
if the patch is a patch that demonstrates the workaround for a bug or is
intended for production code. Has upstream committed a fix?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
It does not look like Redhat has done anything with this officially.
Paul is the release manager of Openswan:
http://ca.linkedin.com/pub/dir/Paul/Wouters
and provided the patch as a workaround after discovering what he thinks is just
a bug in ipsec-tools (although in an email to me he admits
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please could you clarify if this is a bug in Android, a bug in Ubuntu's
ipsec-tools or both? Is there an ipsec-tools upstream bug on this, or
one in Debian or Red Hat's bug trackers, and if so could you please
There is no bug reported on the ipsec-tools bug tracker, this is coming
from the boys at android - if you search the link I provided above
you'll see them blaming ipsec-tools for it, so thats the best I can
offer. The fact that Redhat has implemented a work-around for it (see
provided patch
