Public bug reported:

Binary package hint: strongswan

After upgrade to natty, I found that my ipsec connection did not work
anymore. After investigation I found the following error messages in
/var/log/syslog:

-- cut here --
May 15 13:53:57 fwbukd charon: 05[DMN] thread 5 received 11
May 15 13:53:57 fwbukd charon: 05[DMN] killing ourself, received critical signal
-- cut here --

After some google search I found the following reference to an opensuse
bugrentry which describes exactly the same problem:

http://lists.suse.com/opensuse-bugs/2011-03/msg02058.html

The mentioned patch which fixes this crash is located here:

http://git.strongswan.org/strongswan.git/?p=strongswan.git;a=commitdiff_plain;h=9bac426bf3b9badf1c39d282e8d49881ffbe3142

After applying this patch and recompiling strongswan the crash vanishes
and strongswan 4.5.0 works like a charm again. So please apply this
patch ASAP for the default packages of strongswan. However, better would
be to upgrade to 4.5.2 as that one fixes another bunch of problems as
well.

** Affects: strongswan (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782984

Title:
  strongswan-4.5.0 has known bug: causes charon to crash: "killing
  ourself, received critical signal"

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to