一、gvm安裝
為了方便先獲取權限
中科大的源用不了，改用kali自己的源。進入源文件
去點kali源的注釋，把中科大源注釋掉。（i-修改 :wq保存修改並退出）
這個時候還不能安裝，需要先更新源
安裝gvm
apt-get install gvm
出現提醒
安裝完成，運行設置
二、gvm初始設置
運行gvm-setup:
和上面安裝中的提醒相關，是postgresql版本不匹配的問題
把13版本卸載，指定14版本為使用版本。然后再gvm-setup，運行起來了。但是顯示postgresql還是有問題，后文更新安全文件到當前（可以自由活動幾分鍾了~）。
三、檢驗gvm初始設置，配置postgresql
運行完成，顯示有個錯誤（error）
可以試着運行一下fix方案，但是沒反應。
產生這個問題還是源於起初的gvm版本和postgresql版本不配套。查看相關資料發現postgresql使用的通信端口是5433，和gvm的通信端口5432對不上，因此我們選擇改postgresql的端口。查看正在使用的端口。
查看進入postgresql設置文件（.conf）
修改端口號，保存退出。
修改配置之后還要重啟postgresql才可以應用配置。再運行一下fix方案
成功了，然后可以檢驗gvm設置了
┌──(root💀kali)-[/home/kali]
└─# gvm-check-setup
gvm-check-setup 21.4.3
Test completeness and readiness of GVM-21.4.3
Step 1: Checking OpenVAS (Scanner)...
OK: OpenVAS Scanner is present in version 21.4.4.
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: redis-server is running and listening on socket: /var/run/redis-openvas/redis-server.sock.
OK: redis-server configuration is OK and redis-server is running.
OK: _gvm owns all files in /var/lib/openvas/plugins
OK: NVT collection in /var/lib/openvas/plugins contains 96826 NVTs.
Checking that the obsolete redis database has been removed
OK: No old Redis DB
OK: ospd-OpenVAS is present in version 21.4.4.
Step 2: Checking GVMD Manager ...
OK: GVM Manager (gvmd) is present in version 21.4.5.
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 | zh_CN.UTF-8 | zh_CN.UTF-8 |
OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) ...
Oops, secure memory pool already initialized
OK: Greenbone Security Assistant is present in version 21.4.4.
Step 7: Checking if GVM services are up and running ...
Starting ospd-openvas service
Waiting for ospd-openvas service
OK: ospd-openvas service is active.
Starting gvmd service
Waiting for gvmd service
OK: gvmd service is active.
Starting gsad service
Waiting for gsad service
OK: gsad service is active.
Step 8: Checking few other requirements...
OK: nmap is present in version 21.4.4.
OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work.
WARNING: Could not find makensis binary, LSC credential package generation for Microsoft Windows targets will not work.
SUGGEST: Install nsis.
OK: xsltproc found.
WARNING: Your password policy is empty.
SUGGEST: Edit the /etc/gvm/pwpolicy.conf file to set a password policy.
It seems like your GVM-21.4.3 installation is OK.