Greenbone security assistant

Hello, there are issues with setting up openvas, the main one being that greenbone security assistant is not to be found in any repos.
Compilling it from source is a pain and I did not succeed.
Minor issue is with libopenvas needing to be added to ld path.

It has been changed to “gvm” long time ago

Running gvm-check-setup fails with:

Step 6: Checking Greenbone Security Assistant (GSA) …
ERROR: No Greenbone Security Assistant (gsad) found.
FIX: Please install Greenbone Security Assistant.

And gvm-start:

Failed to start greenbone-security-assistant.service: Unit greenbone-security-assistant.service not found.

It’s a known issue. And there is an other known issue as well. I checked forum of gvm and well… the reply of admin was extremely disappointing.

Fine, i’ll try to compile it and will explain the procedure here if any success.

Greenbone has completely taken over "Open"VAS as a retail product IMO. You can’t get any support on their forum unless it pertains to their paid product. They will quickly blame and dismiss the user\developer for GVM not working on any other Linux distro.

And the people who create extensive webpages explaining how to compile, install, and configure GVM/OpenVAS soon find their instructions no longer working as GVM source code gets updated.

clone gsad from github
checkout to the same version as gvm

apt install libudev-dev -t parrot-backports
apt install libmicrohttpd-dev libmicrohttpd12 libglib2.0-0 libglib2.0-dev libxml2-dev libxml2 libgvm21 libgvm-dev
cd gsad
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr/local ..
make install

So now we got gsad, the easiest part…

clone gsa from github
checkout to the same version as gvm
install nodejs 14:

export VERSION=node_14.x
export KEYRING=/usr/share/keyrings/nodesource.gpg
export DISTRIBUTION="$(lsb_release -s -c)"

curl -fsSL | gpg --dearmor | sudo tee "$KEYRING" >/dev/null
gpg --no-default-keyring --keyring "$KEYRING" --list-keys

echo "deb [signed-by=$KEYRING]$VERSION $DISTRIBUTION main" | sudo tee /etc/apt/sources.list.d/nodesource.list
echo "deb-src [signed-by=$KEYRING]$VERSION $DISTRIBUTION main" | sudo tee -a /etc/apt/sources.list.d/nodesource.list

replace lsb_release with some supported repo (bullseye is OK)

apt update && apt install nodejs -t bullseye
cd gsa
npm install

then yarn will produce an error when using repo’s version. So

curl -sS | sudo apt-key add -
echo "deb stable main" | sudo tee /etc/apt/sources.list.d/yarn.list

sudo apt update && sudo apt install yarn

yarn build

The rest of the procedure is straighforward, from the README, copy the build files into the proper directory and you’ll get GSA

You can see the problem here and the reply of the admin. I thought i am the worst admin in the world

This problem is different from yours, but it’s the new problem that many people is having

In the other topic, the same admin blamed Parrot packaging for the issue.

Where are the systemd configurations file for gvmd ? I can’t find it in /etc/systemd/system
I wanted to verify the path that the admin told you but for me it’s good all works fine but for greenbone security assistant which has no service. Just need to add one. But I’m unaware of what daemon it should start, now that gvm-check-setup says ''OK: gvmd service is active." and “Failed to start greenbone-security-assistant.service: Unit greenbone-security-assistant.service not found.”.
what do you recking this service is supposed to start ? (I though it’d be gvmd)
I also noticed “gvmd.service: Can’t open PID file /run/gvm/ (yet?) after start: Operation not permitted” when running gvm-stop. Maybe not important.

I don’t remember. I did some trouble shooting in other topic and it has some information. Current GVM version is really really bad

Ok I got the answer from this post: Failed to start greenbone-security-assistant.service: Unit greenbone-security-assistant.service not found. · Issue #3368 · greenbone/gsa · GitHub
I recreated the service and added the options PIDFile=/var/run/gsad/ since without it it fails to start and says that it cannot write pid file.
But now it is stuck at starting the service, the logs says
greenbone-security-assistant.service: Can't open PID file /run/gsad/ (yet?) after start: Operation not permitted
The owner of the directory gsad is _gvm and the service file contains:


OH well some info was in here error no openvas scanner found. - #18 by Masmer

Not sure if it relates to the lib openvas 21 problem, but i saw that problme on the forum of gvm as well. Just another problem and gvm closed the issue

Yes links are here:

and here:

It didn’t help though, still facing the same issue.

I mean if you look at the reply of the admin, who is contributing (or working) for gvm, you can’t see it’s helpful so well… what can you expect from this forum.

But you know what? This is a serious problem and i’ll work on it at least this weekend. I hope I can complete new anonsurf in time.

you can still get the virtual machine running but it eats up RAM, and can be unstable.
I contacted them once to inform them of their virtualbox disk not working, they did not try to understand it since I was not a paying customer, and got a broken feature for a long time, if not still broken.
Only the vwmare version works.

Not surprised. AnonSurf is almost completed. I can give gvm a try after this.

I am trying to recompile everything, leaving all options at default.
To do so I did remove all present related greenbone package from the system.
I need to test now, so it’ll be good that I find these handy scripts gvm-check-setup / gvm-start.
Could you tell me which package they’r in ?
Also I will have to rewrite all the service files, If you got any link it’ll be helpful.

I found that it it simply gvm needed, it will reinstall services and scripts.
My issue is with ospd-openvas, it won’t start cause of permissions matters.

Hm there are too many gvm packages from debian and i dont’ really know which i should start with.

  • gvm: a bunch of bash scripts to run setup (skip this)
  • python-gvm (binding / sdk for python. can skip)
  • gvmd, gvm-libs, gvm-tools, ospd-openvas

It should be in gvm. You can check by apt source gvm