Date: Tue, 12 Sep 2017 14:04:21 +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@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222258 Bug ID: 222258 Summary: renameat(2) capability error with absolute path names outside of a sandbox Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: mat@FreeBSD.org CC: bapt@FreeBSD.org, emaste@freebsd.org Created attachment 186296 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D186296&action= =3Dedit kdump output This week's lang/perl5-devel update brought in a change in the way perl -i = -ne 'foo' (equivalent of sed -i -e 'foo') works, it now uses renameat(2). When using lang/perl5-devel from ports r449631, (and before ports r449684 w= here I told Perl not to use the *at functions,) this happens: # perl5.27.4 -i.bak -ne 's/foo/bar/' /tmp/foo Can't rename in-place work file '/tmp/f8BoL2A7' to '/tmp/foo': Capabilities insufficient It works all right when given a relative path, but not at all if given an absolute one. Attached is the output of ktrace that command. (This is outside of any sandbox.) --=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>