Package: gsad
Version: 24.12.2-1
Severity: normal
Dear Maintainer,
When I try to use gsad to create a new target, it fails with "Given
alive_tests was invalid", regardless of the "alive test" selected
(including "Consider alive").
Specifically, I use the "new target" icon, use a random target name.
select manual hosts and enter a single ip address (usually 1.2.3.4, but
it fails with others), then click "save".
This causes a red error popup with the text "Given alive_tests was
invalid".
I would expect the new target to be created.
This is on a clean, fresh installation of greenbone. This is the output
of gvm-check-setup.
madhatta@openvas5:~$ sudo gvm-check-setup
gvm-check-setup 25.04.0
This script is provided and maintained by Debian and Kali.
Test completeness and readiness of GVM-25.04.0
Step 1: Checking OpenVAS (Scanner)...
OK: OpenVAS Scanner is present in version 23.40.2.
OK: Notus Scanner is present in version 22.7.2.
OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
OK: _gvm owns all files in /var/lib/openvas/gnupg
OK: redis-server is present.
OK: scanner (db_address setting) is configured properly using the
redis-server socket: /var/run/redis-openvas/redis-server.sock
OK: the mqtt_server_uri is defined in /etc/openvas/openvas.conf
OK: _gvm owns all files in /var/lib/openvas/plugins
OK: NVT collection in /var/lib/openvas/plugins contains 95081 NVTs.
OK: The notus directory /var/lib/notus/products contains 512 NVTs.
Checking that the obsolete redis database has been removed
OK: No old Redis DB
OK: ospd-openvas service is active.
OK: ospd-OpenVAS is present in version 22.10.1.
Step 2: Checking GVMD Manager ...
OK: GVM Manager (gvmd) is present in version 26.16.1.
Step 3: Checking Certificates ...
OK: GVM client certificate is valid and present as
/var/lib/gvm/CA/clientcert.pem.
OK: Your GVM certificate infrastructure passed validation.
Step 4: Checking data ...
OK: SCAP data found in /var/lib/gvm/scap-data.
OK: CERT data found in /var/lib/gvm/cert-data.
Step 5: Checking Postgresql DB and user ...
OK: Postgresql version and default port are OK.
gvmd | _gvm | UTF8 | libc | en_GB.UTF-8 | en_GB.UTF-8
| | |
16441|pg-gvm|10|2200|f|22.6||
OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) ...
OK: Greenbone Security Assistant is present in version Deamon
24.12.2~git.
Step 7: Checking if GVM services are up and running ...
OK: gvmd service is active.
OK: gsad service is active.
Step 8: Checking few other requirements...
OK: nmap is present.
OK: ssh-keygen found, LSC credential generation for GNU/Linux targets
is likely to work.
OK: nsis found, LSC credential package generation for Microsoft Windows
targets is likely to work.
OK: xsltproc found.
WARNING: Your password policy is empty.
SUGGEST: Edit the /etc/gvm/pwpolicy.conf file to set a password policy.
Step 9: Checking greenbone-security-assistant...
OK: greenbone-security-assistant is installed
It seems like your GVM-25.04.0 installation is OK.
-- System Information:
Debian Release: forky/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.19.6+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gsad depends on:
ii gvmd 26.16.1-1
ii libc6 2.42-13
ii libgcrypt20 1.12.1-2
ii libglib2.0-0t64 2.87.2-3
ii libgnutls30t64 3.8.12-3
ii libgvm22t64 22.35.8-1
ii libmicrohttpd12t64 1.0.2-2
ii libxml2-16 2.15.1+dfsg-2+b1
ii zlib1g 1:1.3.dfsg+really1.3.1-3
Versions of packages gsad recommends:
ii greenbone-security-assistant 22.9.1-1
gsad suggests no packages.
-- no debconf information
