(Kali) GVM login doesnt work

Linux Distribution and External Repo Discussion
1

┌──(kali㉿kali)-[/home]
└─$ sudo gvm-check-setup
gvm-check-setup 23.11.0
Test completeness and readiness of GVM-23.11.0
Step 1: Checking OpenVAS (Scanner)…
OK: OpenVAS Scanner is present in version 23.4.1.
OK: Notus Scanner is present in version 22.6.3.
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 91885 NVTs.
OK: The notus directory /var/lib/notus/products contains 465 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.7.1.
Step 2: Checking GVMD Manager …
OK: GVM Manager (gvmd) is present in version 23.6.2.
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 | C.UTF-8 | C.UTF-8 | | |
16440|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 22.9.1~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-23.11.0 installation is OK.

not able to login

2

Well, you haven’t provided any information about the contents of the logs at /var/log/gvm/gvmd.log or (less likely) /var/log/gvm/gsad.log. I suggest looking there for errors relative to your login issue.

If you need to reset the admin passsord you can try that:

sudo runuser -u _gvm -- gvmd --user=admin --new-password='<password>'

or

sudo -E -u _gvm -g _gvm gvmd --user=admin --new-password='<password>'
1 Like
3

i already tried this number of times. i get below message while logging to gui.
The Greenbone Vulnerability Manager service is not responding. This could be due to system maintenance. Please try again later, check the system status, or contact your system administrator.

4

Greenbone is a distributed service architecture that relies on the interaction of several independent components. gvmd is one of these components. It must be running to reset the user passwords from the command line or to log into GSA.

You need to ensure it’s running with gvm-start. gvm-check-setup should also verify that the gvmd and other services are running. See the Kali Linux install guide for complete more details.