rndc dumpdb doesn't fail on unwritable dump file
Summary
rndc dumpdb
doesn't fail on unwritable dump-file
BIND version affected
BIND 9.18.29 (Extended Support Version) <id:165360e>
running on Linux x86_64 6.6.11-un-def-alt1 #1 SMP PREEMPT_DYNAMIC Wed Jan 10 18:10:40 UTC 2024
built by make with '--build=x86_64-alt-linux' '--host=x86_64-alt-linux' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib64' '--libexecdir=/usr/lib' '--localstatedir=/var/lib' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--disable-dependency-tracking' '--disable-silent-rules' '--runstatedir=/var/run' '--without-included-gettext' '--localstatedir=/var' '--with-libidn2' '--enable-linux-caps' '--enable-fixed-rrset' '--with-openssl' '--with-jemalloc=yes' '--with-json-c=yes' '--disable-static' '--includedir=/usr/include/bind9' '--with-gssapi=yes' '--enable-doh' 'build_alias=x86_64-alt-linux' 'host_alias=x86_64-alt-linux' 'CFLAGS=-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto -DOPENSSL_API_COMPAT=10100'
compiled by GCC 13.2.1 20240128 (ALT Sisyphus 13.2.1-alt4)
compiled with OpenSSL version: OpenSSL 3.1.7 3 Sep 2024
linked to OpenSSL version: OpenSSL 3.1.7 3 Sep 2024
compiled with libuv version: 1.48.0
linked to libuv version: 1.48.0
compiled with libnghttp2 version: 1.63.0
linked to libnghttp2 version: 1.63.0
compiled with json-c version: 0.17
linked to json-c version: 0.17
threads support is enabled
DNSSEC algorithms: RSASHA1 NSEC3RSASHA1 RSASHA256 RSASHA512 ECDSAP256SHA256 ECDSAP384SHA384 ED25519 ED448
DS algorithms: SHA-1 SHA-256 SHA-384
HMAC algorithms: HMAC-MD5 HMAC-SHA1 HMAC-SHA224 HMAC-SHA256 HMAC-SHA384 HMAC-SHA512
TKEY mode 2 support (Diffie-Hellman): yes
TKEY mode 3 support (GSS-API): yes
default paths:
named configuration: /etc/named.conf
rndc configuration: /etc/rndc.conf
DNSSEC root key: /etc/bind.keys
nsupdate session key: /var/run/named/session.key
named PID file: /var/run/named/named.pid
named lock file: /var/run/named/named.lock
Steps to reproduce
- configure
dump-file
to point to unwritable path (e.g.dump-file "/nonexistent/path";
) - run
named
as unprivileged user (for example,named -u named
) - run
rndc dumpdb
What is the current bug behavior?
rndc
exits without error message and code 0
What is the expected correct behavior?
rndc
should fail with error message and exit code 1