Date: Thu, 14 Sep 2017 00:02:58 +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-Vnn9oKlczc@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=3D222258 tony@develop-help.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tony@develop-help.com --- Comment #2 from tony@develop-help.com --- Yes, the code grabs a handle to the cwd when opening the file for -i and us= es that handle when cleaning up when the file is closed, in this specific case when renaming the original file to a backup file, or renaming the work file over the original file. If we were passing AT_FDCWD we could just call rename(). I have a workaround patch (for perl) that calls rename() for absolute paths= on FreeBSD if Mathieu wants to try it on the tonyc/127663-freebsd-renameat bra= nch in the perl5 git at git://perl5.git.perl.org/perl.git I do wonder if renameat() will behave correctly in a container on FreeBSD. --=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-222258-8-Vnn9oKlczc>