slackware-current/patches/source/bind/default.named
Patrick J Volkerding ae2de64cd3 Wed Dec 20 21:10:47 UTC 2023
patches/packages/bind-9.16.45-x86_64-1_slack15.0.txz:  Upgraded.
  This is a bugfix release.
patches/packages/proftpd-1.3.8b-x86_64-1_slack15.0.txz:  Upgraded.
  This update fixes a security issue:
  mod_sftp: implemented mitigations for "Terrapin" SSH attack.
  For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2023-48795
  (* Security fix *)
testing/packages/bind-9.18.21-x86_64-1_slack15.0.txz:  Upgraded.
  This is a bugfix release.
2023-12-21 13:30:36 +01:00

24 lines
1 KiB
Text

# User to run named as:
NAMED_USER=named
# Group to use for named related files and directories.
# By default, named will also run as the primary group of $NAMED_USER,
# which will usually be the same as what's listed below, but not
# necessarily if something other than the default of "named" is used.
NAMED_GROUP=named
# Options to run named with. At least -u $NAMED_USER is required, but
# additional options may be added if needed.
NAMED_OPTIONS="-u $NAMED_USER"
# If this is set to YES, then before starting named the startup script
# will make sure that /etc/rndc.key (if it exists) and the enitre contents
# of /var/named are chowned to $NAMED_USER:$NAMED_GROUP. If some of these
# files are improperly owned, named will refuse to start or may not work
# properly. This is also a useful setting when upgrading from an older BIND
# package that would run as root.
#
# If NAMED_CHOWN is set to anything other than YES (or is unset), then these
# files will not be chowned automatically and the admin will handle any
# required file ownerships.
NAMED_CHOWN=NO