Date: Mon, 06 Mar 2017 06:07:47 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 217574] PkgBase: runtime package removes sticky bit from /tmp Message-ID: <bug-217574-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217574 Bug ID: 217574 Summary: PkgBase: runtime package removes sticky bit from /tmp Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: bsdports@kyle-evans.net Created attachment 180554 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180554&action= =3Dedit git(1) produced diff to set permissions on /tmp after install of -runtime Hi, In deploying pkgbase on a lot of the machines I manage, I find that install= ing the runtime pkg resets permissions on my /tmp and removes the sticky bit. T= his is pretty unfriendly, unfortunately, for programs not run as root that crea= te temp files. This is reproducible just by installing the -runtime pkg on a machine with /tmp at 1777 like in a standard install. On one hand, pkg(8) probably shouldn't be overwriting permissions on a directory that it didn't create. On the other hand, if /tmp doesn't exist (= say, installing into a new jail environment or something to that effect) then the runtime pkg should probably be setting sensible permissions since it's not a directory that had previously existed. I'm attaching a patch to set sensible permissions (1777) on /tmp in accorda= nce with bsdconfig behavior to address the latter part of my previous paragraph, which would alleviate this problem. --=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-217574-8>