I redid everything according to the Trusted NVT page, and did it the same as the first time. Only thing I can see is the Unsafe Permissions, but I'm not sure how to handle that. What does it mean?
############################ root@localhost:/tmp# wget http://www.openvas.org/OpenVAS_TI.asc converted 'http://www.openvas.org/OpenVAS_TI.asc' (ANSI_X3.4-1968) -> ' http://www.openvas.org/OpenVAS_TI.asc' (UTF-8) --2016-01-03 22:18:07-- http://www.openvas.org/OpenVAS_TI.asc Resolving www.openvas.org (www.openvas.org)... 5.9.98.186 Connecting to www.openvas.org (www.openvas.org)|5.9.98.186|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1673 (1.6K) [text/plain] Saving to: 'OpenVAS_TI.asc.1' OpenVAS_TI.asc.1 100%[===============>] 1.63K --.-KB/s in 0.005s 2016-01-03 22:18:11 (306 KB/s) - 'OpenVAS_TI.asc.1' saved [1673/1673] root@localhost:/tmp# gpg --homedir=/etc/openvas/g gnupg/ gsad_log.conf root@localhost:/tmp# gpg --homedir=/etc/openvas/gnupg/ --import OpenVAS_TI.asc gpg: WARNING: unsafe permissions on homedir `/etc/openvas/gnupg/' gpg: key 48DB4530: "OpenVAS Transfer Integrity" not changed gpg: Total number processed: 1 gpg: unchanged: 1 root@localhost:/tmp# ^C root@localhost:/tmp# gpg --homedir=/etc/openvas/gnupg/ --lsign-key 48DB4530 gpg: WARNING: unsafe permissions on homedir `/etc/openvas/gnupg/' gpg: checking the trustdb gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model gpg: depth: 0 valid: 1 signed: 1 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: depth: 1 valid: 1 signed: 0 trust: 1-, 0q, 0n, 0m, 0f, 0u pub 1024D/48DB4530 created: 2007-11-05 expires: never usage: SC trust: unknown validity: full sub 2048g/70610CFB created: 2007-11-05 expires: never usage: E [ full ] (1). OpenVAS Transfer Integrity "OpenVAS Transfer Integrity" was already locally signed by key 807B4D30 Nothing to sign with key 807B4D30 Key not changed so no update needed. root@localhost:/tmp# ^C root@localhost:/tmp# openvas-nasl -p script.nasl (openvas-nasl:1902): lib kb_redis-CRITICAL **: get_redis_ctx: redis connection error: No such file or directory (openvas-nasl:1902): lib kb_redis-CRITICAL **: redis_new: cannot access redis at '/tmp/redis.sock' (openvas-nasl:1902): lib kb_redis-CRITICAL **: get_redis_ctx: redis connection error: No such file or directory root@localhost:/tmp# ############################ On 3 January 2016 at 21:48, Eero Volotinen <[email protected]> wrote: > Please read errors and try to understand messages. For example you enabled > signature checking and didn't import keys correctly. > > -- > Eero > > 2016-01-03 21:38 GMT+02:00 fbrand . <[email protected]>: > >> Hi, >> >> I'm having problems with Scanner not wanting to start after setup. NVT's >> didn't update 100% first time, but ran again later and ran through, but see >> still showing NVT db too low. >> >> Read somewhere to run "openvas-mkcert-client -n om -i", but that also >> did nothing. >> Scanner just gives ERROR when trying to start. >> Manager starts fine. >> >> Appreciate the help. >> >> ################ >> >> "openvas-check-setup" >> >> OK: OpenVAS Manager is present in version 6.0.1. >> Checking OpenVAS Manager client certificate ... >> OK: OpenVAS Manager client certificate is valid and present as >> /var/lib/openvas/CA/clientcert.pem. >> >> Checking OpenVAS Manager database ... >> >> OK: OpenVAS Manager database found in >> /var/lib/openvas/mgr/tasks.db. >> Checking access rights of OpenVAS Manager database ... >> >> OK: Access rights for the OpenVAS Manager database are correct. >> Checking if users exist ... >> OK: At least one user exists. >> >> Checking sqlite3 presence ... >> OK: sqlite3 found, extended checks of the OpenVAS Manager >> installation enabled. >> >> Checking OpenVAS Manager database revision ... >> OK: OpenVAS Manager database is at revision 146. >> Checking database revision expected by OpenVAS Manager ... >> OK: OpenVAS Manager expects database at revision 146. >> OK: Database schema is up to date. >> Checking OpenVAS Manager database (NVT data) ... >> ERROR: The number of NVTs in the OpenVAS Manager database is too >> low. >> FIX: Make sure OpenVAS Scanner is running with an up-to-date NVT >> collection and run 'openvasmd --rebuild'. >> WARNING: OpenVAS Scanner is NOT running! >> SUGGEST: Start OpenVAS Scanner (openvassd). >> ######################################### >> >> "openvassd.messages" >> >> root@localhost:/var/log/openvas# tail openvassd.messages >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/FreeWebShop_detect.nasl: Could not be loaded >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/esoft_slk_ssa_2005_135_01.nasl: bad or missing >> signature. Will not execute this script >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/esoft_slk_ssa_2005_135_01.nasl: Could not be loaded >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/freebsd_caml-light.nasl: bad or missing signature. >> Will not execute this script >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/freebsd_caml-light.nasl: Could not be loaded >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/gb_7zip_detect_lin.nasl: bad or missing signature. >> Will not execute this script >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/gb_7zip_detect_lin.nasl: Could not be loaded >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/esoft_slk_ssa_2007_066_05.nasl: bad or missing >> signature. Will not execute this script >> [Sun Jan 3 18:58:50 2016][1605] >> /var/lib/openvas/plugins/esoft_slk_ssa_2007_066_05.nasl: Could not be loaded >> [Sun Jan 3 18:58:50 2016][1605] Stopped loading plugins: High number of >> errors. >> root@localhost:/var/log/openvas# >> >> ################################ >> >> >> >> _______________________________________________ >> Openvas-discuss mailing list >> [email protected] >> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss >> > >
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
