Date: Sat, 16 Sep 2017 16:24:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 222258] renameat(2) capability error with absolute path names outside of a sandbox Message-ID: <bug-222258-8-sh1q0b0Dr4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222258-8@https.bugs.freebsd.org/bugzilla/> References: <bug-222258-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=222258 Mateusz Guzik <mjg@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mjg@FreeBSD.org --- Comment #9 from Mateusz Guzik <mjg@FreeBSD.org> --- Now this is sketchy. So when you openat/whatever with an absolute path caps are not getting populated and the dir fd is not logged by audit. On the other hand the fd is not used in the lookup, so making its caps affect the outcome anyway may not be the right thing to do here. There is also potential crappery with startdir (used by nfs). I guess restructuring is the way to go here. Note there is a much-needed cleanup to do here anyway: audit code *duplicates* the logic used to determine starting vnodes. -- 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-222258-8-sh1q0b0Dr4>