Date: Tue, 25 Jul 2023 09:27:19 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262180] jail escaping via jail-friendly nullfs Message-ID: <bug-262180-227-X4sWtfzdX4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262180-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262180-227@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=3D262180 crest@rlwinm.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crest@rlwinm.de --- Comment #2 from crest@rlwinm.de --- Where in your sequence of of commands did you attach to the jail? It's the = jail that's locking in processes not the nullfs. Outside of the jail you're expe= cted to be able to leave the nullfs with `cd ..`. Or did I miss-understand and t= he nullfs mount from inside the jail is able to expose a path from beneath the jail under the jail root directory despite the (n)mount performed inside the jail? If this is the case just ignoring it with a the release is EoL is a c= heap cop out and we have to define what's the expected semantics for nullfs moun= ting at different enforce_statfs levels. --=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-262180-227-X4sWtfzdX4>