Date: Mon, 12 Dec 2016 14:40:52 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 215250] jail break under particular circumstance Message-ID: <bug-215250-9824-qIDoYpACZa@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215250-9824@https.bugs.freebsd.org/bugzilla/> References: <bug-215250-9824@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=3D215250 Jamie Gritton <jamie@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamie@FreeBSD.org Resolution|--- |Works As Intended Status|New |Closed --- Comment #2 from Jamie Gritton <jamie@FreeBSD.org> --- Yes, it's expected behavior. It's not so much a "break" as being pulled ou= t of the jail by an administrator with proper permission who presumably knows wh= at he's doing. Preventing an assisted break like this would be doable, but would involve either tracing all .. traversals back to at least a prison root, or attachi= ng a prison reference to every directory in the vnode cache. Both of those seem= to be a bit of overkill. I have to admin I've done the very thing in the example: temporarily moving /usr/ports to a jail. Lately I've gone with nullfs instead, which doesn't = open this hole. --=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-215250-9824-qIDoYpACZa>