|
4a8b8bd95f
|
- Applied upstream patch adjusting an internal thread id causing
charon keying daemon start failure (bnc#779038,strongswan#198):
openssl: Ensure the thread ID is never zero
This might otherwise cause problems because OpenSSL tries to
lock mutexes recursively if it assumes the lock is held by a
different thread e.g. during FIPS initialization.
See http://wiki.strongswan.org/issues/198 for more informations.
OBS-URL: https://build.opensuse.org/package/show/network:vpn/strongswan?expand=0&rev=48
|
2012-09-07 12:53:09 +00:00 |
|