Bug 16989 - named in chroot should bind /etc/named as diretory not file
Summary: named in chroot should bind /etc/named as diretory not file
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-20 00:21 CEST by Romain MARIADASSOU
Modified: 2023-11-01 09:36 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Romain MARIADASSOU 2015-10-20 00:21:04 CEST
Description of problem:
Script in named/bind9 : /usr/sbin/setup-named-chroot.sh is binding /etc/named as a file, but /etc/named is a directory. 
So /etc/named is never mounted in /var/lib/named/etc/named

Version-Release number of selected component (if applicable):
at least mga4 - mga5 in version i586 and x86_64

How reproducible:
Always

Steps to Reproduce:
1. create one or more files in dir /etc/named/
2. files should be available in /var/lib/named/etc/named after named is started

Steps for workaround:
1. Edit /usr/sbin/setup-named-chroot.sh
2. Add /etc/named to DIR_RO_SOURCES variable
3. Restart named
 


Reproducible: 

Steps to Reproduce:
Comment 1 Romain MARIADASSOU 2015-10-20 00:27:36 CEST
Bug was fixed in mga5 but not in mga4
Sorry for duplicate.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 2 Liam Hellen 2023-11-01 09:36:05 CET Comment hidden (spam)

CC: (none) => liamhellen55


Note You need to log in before you can comment on or make changes to this bug.