Date: Thu, 28 Sep 2017 19:10:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 222632] Enable Capsicum for connect(2) Message-ID: <bug-222632-8-UQ5jDwCplg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222632-8@https.bugs.freebsd.org/bugzilla/> References: <bug-222632-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222632 --- Comment #10 from Shawn Webb <shawn.webb@hardenedbsd.org> --- It turns out that SSL_connect doesn't call connect(2). SSL_connect assumes = an already-connected socket. Its job is to set up the SSL/TLS side of things. Which is really good news. I'm able to tell the non-capmode child process to perform the connect on be= half of the capmode parent. This is a doable workaround. However, long-term, we should figure out how to be able to call connect(2) in capmode. Until then,= we should explicitly tell users that connect(2) is unavailable in capmode and = that CAP_CONNECT is meaningless. --=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-222632-8-UQ5jDwCplg>