Package: openvas-scanner Version: 5.0.7-3 Severity: normal Dear Maintainer,
I discovered an issue with the openvas-check-setup script on debian. The problem is, that the redis-server does not set its unix socket to /tmp/redis.socket but to /var/run/redis/redis.socket. As this is no redis-server problem, the script is checking for /tmp/redis.socket, it mourns a failure. However, the problem is, that the script is checking an entry in openvassd.conf, named kb_location (the config should be "kb_location=/var/run/redis/redis.socket"). I discussed this with the maintainers of openvas. However, I did not find the file "openvassd.conf" and so I could not edit the data of kb_location. So, please add this one to the packages (if it is already not in the version of experimental, which is version 9). The actual version in debian/testing is version 8, and "apt-file search openvassd.conf" did not get me any file output. The workaround is, to manually link /vr/run/redis/redis.socket to /tmp/redis.socket. Hope this helps a little bit. If I missed soemthing, please point me to it. Thank you for your help! Best regards Hans -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openvas-scanner depends on: ii debconf [debconf-2.0] 1.5.60 ii init-system-helpers 1.48 ii libc6 2.24-10 ii libgcrypt20 1.7.6-1 ii libglib2.0-0 2.50.3-2 ii libopenvas8 8.0.8-2 ii lsb-base 9.20161125 ii openssl 1.1.0e-2 ii redis-server 3:3.2.6-1 Versions of packages openvas-scanner recommends: ii nmap 7.40-1 ii rsync 3.1.2-1 Versions of packages openvas-scanner suggests: pn ike-scan <none> pn openvas-client <none> pn pnscan <none> ii snmp 5.7.3+dfsg-1.7 pn strobe <none> -- debconf information: * openvas-scanner/enable_redis: true
