Date: Mon, 01 Apr 2019 17:56:00 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 236944] security/strongswan: strongswan.in improvements Message-ID: <bug-236944-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236944 Bug ID: 236944 Summary: security/strongswan: strongswan.in improvements Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: jlduran@gmail.com CC: strongswan@Nanoteq.com Flags: maintainer-feedback?(strongswan@Nanoteq.com) CC: strongswan@Nanoteq.com Created attachment 203306 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D203306&action= =3Dedit Patch for strongswan.in This is a follow-up of bug #234648. There are still a few missing details: If the service is stopped, and "reload", "status" or "statusall" is issued,= the message displayed is rather cryptic. Also, if there are established connections, and "restart" is issued, there = is a possibility for charon not having enough time to teardown. In _ipsec.in th= ey hardcode a sleep of 2 seconds (https://github.com/strongswan/strongswan/blob/5c38a5ea832accec3a8d3942d878= ac5be5bb2a4b/src/ipsec/_ipsec.in#L183), here I've decided to reuse the waiting stanza. This is a proposed patch, again, far from elegant, but we're getting there. Thank you! --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236944-7788>