Hello Nataneal,
I looked at the link and it appears to be a very old bug.
So its fixed in newer versions of openswan?
No, the version used by Bering-uClibc is 2.4.5 which is the latest stable
version released only a few weeks ago and still has the bug.
Eric
Using Tomcat but need to do
Hello list,
Issuing the command ipsec auto --status while there is no tunnel will
trigger a uclibc only bug in openswan (it blindly mallocs 0 bytes)
more info at
http://bugs.xelerance.com/view.php?id=627http://bugs.xelerance.com/view.php?id=627
patch and updated buildtool.cfg/buildtool.mk can
Hello Cedric,
Thanks for your fix! I will commit it to CVS and also update the current
ipsec package in CVS.
Regards,
Eric
Issuing the command ipsec auto --status while there is no tunnel will
trigger a uclibc only bug in openswan (it blindly mallocs 0 bytes)
more info at
Hello Natanael,
Issuing the command ipsec auto --status while there is no tunnel will
trigger a uclibc only bug in openswan (it blindly mallocs 0 bytes)
does it affect openswan on a 2.6 kernel too?
It looks like it, the malloc problem is in an openswan userspace tool and
has to do with a
