We are happy to announce the release of strongSwan 5.3.5, which fixes a regression in 5.3.4.
Fixes a Regression in 5.3.4
5.3.4 replaced uses of sigwait(3) with sigwaitinfo(2). Unlike the former, the latter may fail with EINTR errors if the syscall is interrupted by a signal that is unblocked but not in the set of signals the call waits for. Because this situation wasn't handled properly, the daemon could get terminated unexpectedly with the error: "waiting for signal failed: Interrupted system call".
Other Notable Changes
- RADIUS retransmission timeouts are now configurable via strongswan.conf, courtesy of Thom Troy.