Bug 134060 - Current bind-chroot uses hardcoded /tmp/named path in scriplet
Summary: Current bind-chroot uses hardcoded /tmp/named path in scriplet
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: bind
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks: FC3Target
TreeView+ depends on / blocked
 
Reported: 2004-09-29 11:06 UTC by Matthias Saou
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: bind-9.2.4-2
Clone Of:
Environment:
Last Closed: 2004-10-18 21:04:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Matthias Saou 2004-09-29 11:06:05 UTC 
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.
Comment 1 Jason Vas Dias 2004-09-29 13:59:02 UTC 
Yes, this is the way bind-chroot always has done sysconfig/named
editing. 
The next version will use mktemp .
Note You need to log in before you can comment on or make changes to this bug.