Description of problem: The current FC devel bind-chroot uses a hardcoded path of /tmp/named in its scriplet, which is a predictable name that can lead to security concerns. Using mktemp instead should be considered. Version-Release number of selected component (if applicable): bind-chroot-9.2.4-1 How reproducible: Always. Steps to Reproduce: 1. rpm -qp --scripts bind-chroot-9.2.4-1.i386.rpm | grep tmp Actual results: grep -v '^ROOTDIR='/var/named/chroot /etc/sysconfig/named > /tmp/named mv -f /tmp/named /etc/sysconfig/named Expected results: Seeing something like TMP=$(mktemp /tmp/named.XXXXXX) then using $TMP.
Yes, this is the way bind-chroot always has done sysconfig/named editing. The next version will use mktemp .