|
 |
1baafe |
From 3a161af91bffcd457586ab466e32ac8484028763 Mon Sep 17 00:00:00 2001
|
|
|
1baafe |
From: Petr Mensik <pemensik@redhat.com>
|
|
|
1baafe |
Date: Wed, 17 Jun 2020 23:17:13 +0200
|
|
|
1baafe |
Subject: [PATCH] Update man named with Red Hat specifics
|
|
|
1baafe |
|
|
|
1baafe |
This is almost unmodified text and requires revalidation. Some of those
|
|
|
1baafe |
statements are no longer correct.
|
|
|
1baafe |
---
|
|
|
1baafe |
bin/named/named.rst | 35 +++++++++++++++++++++++++++++++++++
|
|
|
1baafe |
1 file changed, 35 insertions(+)
|
|
|
1baafe |
|
|
|
1baafe |
diff --git a/bin/named/named.rst b/bin/named/named.rst
|
|
|
1baafe |
index 6fd8f87..3cd6350 100644
|
|
|
1baafe |
--- a/bin/named/named.rst
|
|
|
1baafe |
+++ b/bin/named/named.rst
|
|
|
1baafe |
@@ -228,6 +228,41 @@ Files
|
|
|
1baafe |
``/var/run/named/named.pid``
|
|
|
1baafe |
The default process-id file.
|
|
|
1baafe |
|
|
|
1baafe |
+Notes
|
|
|
1baafe |
+~~~~~
|
|
|
1baafe |
+
|
|
|
1baafe |
+**Red Hat SELinux BIND Security Profile:**
|
|
|
1baafe |
+
|
|
|
1baafe |
+By default, Red Hat ships BIND with the most secure SELinux policy
|
|
|
1baafe |
+that will not prevent normal BIND operation and will prevent exploitation
|
|
|
1baafe |
+of all known BIND security vulnerabilities. See the selinux(8) man page
|
|
|
1baafe |
+for information about SElinux.
|
|
|
1baafe |
+
|
|
|
1baafe |
+It is not necessary to run named in a chroot environment if the Red Hat
|
|
|
1baafe |
+SELinux policy for named is enabled. When enabled, this policy is far
|
|
|
1baafe |
+more secure than a chroot environment. Users are recommended to enable
|
|
|
1baafe |
+SELinux and remove the bind-chroot package.
|
|
|
1baafe |
+
|
|
|
1baafe |
+*With this extra security comes some restrictions:*
|
|
|
1baafe |
+
|
|
|
1baafe |
+By default, the SELinux policy does not allow named to write outside directory
|
|
|
1baafe |
+/var/named. That directory used to be read-only for named, but write access is
|
|
|
1baafe |
+enabled by default now.
|
|
|
1baafe |
+
|
|
|
1baafe |
+The "named" group must be granted read privelege to
|
|
|
1baafe |
+these files in order for named to be enabled to read them.
|
|
|
1baafe |
+Any file updated by named must be writeable by named user or named group.
|
|
|
1baafe |
+
|
|
|
1baafe |
+Any file created in the zone database file directory is automatically assigned
|
|
|
1baafe |
+the SELinux file context *named_zone_t* .
|
|
|
1baafe |
+
|
|
|
1baafe |
+The Red Hat BIND distribution and SELinux policy creates three directories where
|
|
|
1baafe |
+named were allowed to create and modify files: */var/named/slaves*, */var/named/dynamic*
|
|
|
1baafe |
+*/var/named/data*. The service is able to write and file under */var/named* with appropriate
|
|
|
1baafe |
+permissions. They are used for better organisation of zones and backward compatibility.
|
|
|
1baafe |
+Files in these directories are automatically assigned the '*named_cache_t*'
|
|
|
1baafe |
+file context, which SELinux always allows named to write.
|
|
|
1baafe |
+
|
|
|
1baafe |
See Also
|
|
|
1baafe |
~~~~~~~~
|
|
|
1baafe |
|
|
|
1baafe |
--
|
|
|
1baafe |
2.26.2
|
|
|
1baafe |
|