I tried out and did a write-up of what I did when installing GVM10-beta1.
Pretty straight forward like the “old” OpenVas9
If someone is interested here are the little howto.
This will be a (planned as) ongoing test with more of the packages installed from src…
Thanks for sharing I am curious did you found any pros, cons, obstacles, cool new stuff, … in the new version?
Btw. when using Ubuntu 18.04 you don’t need to add the nodesource apt repo. Ubuntu 18.04 already provides an up to date nodejs version https://packages.ubuntu.com/bionic/nodejs Just run
apt install nodejs
gvmd and openvassd seems more streamlined than “before”.
But I haven’t really done any large jobs yet.
And thanks for the node heads up. I am so used to add nodesource when using 16.04 so I didn’t even try
I’m really interested to see what the postgre things in 10 could give us.
So hopefully that will be a task for today
Really great, thanks for posting this howto.
Related to the redis config you could also have a look at the following documentation:
as well as the related OpenVAS/GVM changes to the redis configs shown here:
Thanks for the diskussion and tips!
I have updated the page.
Nothing fancy with startup daemons and such…
Something seems strange with the installation thou.
I’m going to run some tests and try get some debug logging going.
The scan “stalls” at 1% and nothing seems to happen after that.
The only thing that happens is that openvassd is going 100% on one core with:
openvassd: Serving /usr/local/var/run/openvassd.sock
And redis-monitor shows this.
1539184255.542899 [2 unix:/var/run/redis/redis-server.sock] "PING"
1539184255.543086 [2 unix:/var/run/redis/redis-server.sock] "FLUSHDB"
1539184255.543218 [2 unix:/var/run/redis/redis-server.sock] "SELECT" "0"
1539184255.543341 [0 unix:/var/run/redis/redis-server.sock] "HDEL" "GVM.__GlobalDBIndex" "2"
1539184255.543548 [0 unix:/var/run/redis/redis-server.sock] "HEXISTS" "GVM.__GlobalDBIndex" "1"
1539184255.543675 [0 unix:/var/run/redis/redis-server.sock] "SELECT" "1"
1539184255.543788 [1 unix:/var/run/redis/redis-server.sock] "SRANDMEMBER" "nvticache10"
1539184258.544853 [0 unix:/var/run/redis/redis-server.sock] "HSETNX" "GVM.__GlobalDBIndex" "1" "1"
1539184258.545147 [0 unix:/var/run/redis/redis-server.sock] "HSETNX" "GVM.__GlobalDBIndex" "2" "1"
1539184258.545307 [0 unix:/var/run/redis/redis-server.sock] "SELECT" "2"
1539184258.545469 [2 unix:/var/run/redis/redis-server.sock] "PING"
And for the moment I can’t find log_whole_attack in the scan config,
So this will be continued
Updates before changing location
The openvassd seems to freeze after a few seconds.
Two tries and the last non redis log in openvassd.log:
sd main:MESSAGE:2018-10-10 15h44.28 utc:23843: Plugin 2009/secpod_ms_directx_code_exec_vuln.nasl is deprecated. It will neither loaded nor launched.
And a strace on the running task openvassd stops on both tries:
write(3, “*2\r\n$11\r\nSRANDMEMBER\r\n$33\r\nfilen”…, 62) = 62
read(3, “$28\r\n126.96.36.199.4.1.256188.8.131.52001”…, 16384) = 35
seems there where no new beta releases in between which includes the fix discussed e.g. here: Community feed unusable or in various other threads.
The log_whole_attack isn’t available anymore from within a scan config since version 5.1.2 of the scanner:
The preference log_whole_attack is now an scanner-only preference.
Aah, now I remembered that one…
I looked in the commit to see if I could merge it, but the 6.x branch seems to be lots of refactoring.
And that really above my c++ knowledge to make anything out of it
I’ll wait for the next beta and continue then
Is this now a “global config setting” in openvassd.conf?
It was always a “global config setting” within the openvassd.conf but was provided (probably accidentally) on a per scan config base due to a typo within the code base: