Package Details: openvas-scanner 23.11.1-1

Git Clone URL: https://aur.archlinux.org/openvas-scanner.git (read-only, click to copy)
Package Base: openvas-scanner
Description: Vulnerability scanning Daemon
Upstream URL: https://github.com/greenbone/openvas-scanner
Licenses: GPL-2.0-only
Groups: greenbone-vulnerability-manager
Submitter: mfulz
Maintainer: TrialnError
Last Packager: TrialnError
Votes: 0
Popularity: 0.000000
First Submitted: 2021-02-16 22:17 (UTC)
Last Updated: 2024-11-12 19:00 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

TrialnError commented on 2024-10-08 19:04 (UTC)

Regarding the missing binaries:
There are more packages needed. Looking at the install script of gvmd it is clearly stated, why those aren't available anymore by default: 

OPTION (INSTALL_OLD_SYNC_SCRIPTS "Install shell based feed sync scripts" OFF)
if (INSTALL_OLD_SYNC_SCRIPTS)
  message (DEPRECATION "The version of greenbone-feed-sync included in gvmd is deprecated in favor of the newer Python version (https://github.com/greenbone/greenbone-feed-sync/) and will be removed in the next major version.")
endif (INSTALL_OLD_SYNC_SCRIPTS)

It is deprecated.

TrialnError commented on 2024-10-08 18:08 (UTC)

I'm sorry that this is still a mess.
But I'm limited in my time and I only took the software, because it was neglected for a long time and in a non working state.
Regarding the missing binaries: I noticed that too and thats the reason why the systemd unit files are temporarily removed. My focus was mostly to get the groundwork right (how are users created, directories and such). Next on the agenda is the case of the missing binaries. Of note though: I wouldn't consider the wiki up to date and the content should be taken with a grain of salt. My opinion is, that the official doc should be used at the moment.
Regarding the maintenance: I will happily add co-maintainers, especially ones that want to use the software. I don't intend to maintain this software stack in the long run. But it should be in a state where it adheres the current guidelines and don't do questionable stuff (like the various sudo calls).
Until then I can only ask for patience and for more hands that take a stab on this.

rek2 commented on 2024-10-08 15:50 (UTC) (edited on 2024-10-08 15:51 (UTC) by rek2)

Hello thanks, everything compiled now, but there are a lot of things wrong, I am following the wiki entry and as I mention now I can use makepkg with ignore pgp key because that fails with "paru" but I can install all the packages listed in the arch wiki... But what makes me cry now because I have been with this on and off for more than 1-2 months there are missing binaries :( some packages are missing to install the bin/ etc example:

locate greenbone-feed-sync
/etc/systemd/system/multi-user.target.wants/greenbone-feed-sync.timer
/home/rek2/.cache/paru/clone/gvmd/src/build/tools/greenbone-feed-sync
/home/rek2/.cache/paru/clone/gvmd/src/gvmd-23.10.0/tools/greenbone-feed-sync.in

There is only the .timer under systemd the actual tool is never installed on an of the bin/ standard PATH places, is still on tools/ but never installed in the system etc so is all a super mess like this… I am about to give up and install nessus even do I will hate that because I rather use always open tools can someone please fix the packages so all tools are installed, and maybe update the wiki :(

TrialnError commented on 2024-09-22 19:09 (UTC)

Great, that this package now worked.
Regarding gsa I would suggest to post any issue on the respective package details page :) Avoids to search all over the place and notify users unnecessary if they're subscribed to this specific package.
Nevertheless thank you for reporting. I will look into it. It did build not to long ago :D

rek2 commented on 2024-09-19 16:18 (UTC)

Hello @TrilError I did was able to compile this one now, thank you. but unfortunatelly hit another problem with "gsa" :( 

✓ 2521 modules transformed.
x Build failed in 1m 36s
error during build:
[vite:terser] terser not found. Since Vite v3, terser has become an optional dependency. You need to install it.
    at loadTerserPath (file:///home/rek2/.cache/paru/clone/gsa/src/gsa-23.3.0/node_modules/vite/dist/node/chunks/dep-DyBnyoVI.js:19675:13)
    at Object.renderChunk (file:///home/rek2/.cache/paru/clone/gsa/src/gsa-23.3.0/node_modules/vite/dist/node/chunks/dep-DyBnyoVI.js:19710:27)
    at file:///home/rek2/.cache/paru/clone/gsa/src/gsa-23.3.0/node_modules/vite/node_modules/rollup/dist/es/shared/node-entry.js:19928:40
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'gsa-23.3.0-1':

note: I did install terser with paru -S terser but same result :(

TrialnError commented on 2024-09-18 19:13 (UTC)

-Werror is stripped from CMakeLists.txt and with that the build succeeds on FORTIFY_SOURCE=3. Lots of warnings though.
This is already done that way in gvm-libs.

TrialnError commented on 2024-09-18 18:33 (UTC)

Good it got figured out. After the pacman 7.0 update I noticed I wasn't in sync with the current Arch settings (aka still FORTIFY_SOURCE 2) and therefore had no issues :D
Following your ticket it seems the related samba package is optional. I will look into adding it to the AUR, but first I want to figure out how to handle the FORTIFY_SOURCE situation and get the current packages up to standard.

rek2 commented on 2024-09-16 15:52 (UTC)

Hello, so I fixed the original issue, had another one that I pasted on the same thread on the GitHub issues section, and they say we are missing a OpenVAS-smb package context: https://github.com/greenbone/openvas-scanner/issues/1710#issuecomment-2352558597

TrialnError commented on 2024-09-06 18:22 (UTC)

Hello rek2,
really odd. Do you have a customized makepkg.conf? Or does paru have a similar replacement?
What happens if you try to build the package with makepkg?

Regarding gsa vs greenbone-security-assistant: I'm fairly new to maintaining these PKGBUILDs. And on the ToDo is still to figure out what was tried to achieve and what should happen. I assume the latter will go, as it is in theory duplicating efforts. On the other hand it only used to build a sub part of the whole.
But I would suggest to stick with gsa.

rek2 commented on 2024-09-06 17:01 (UTC)

Hello TrialnError thank you for your reply, today I finished work a bit early and I have tried again with no luck :( I made sure I removed the old cache from ~/.cache/paru/clone/* so it pulls a new version… I think is the same error:

-- Build files have been written to: /home/rek2/.cache/paru/clone/openvas-scanner/src/build
make: Entering directory '/home/rek2/.cache/paru/clone/openvas-scanner/src/build'
[  1%] Building C object misc/CMakeFiles/openvas_misc_shared.dir/bpf_share.c.o
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors
make[2]: *** [misc/CMakeFiles/openvas_misc_shared.dir/build.make:76: misc/CMakeFiles/openvas_misc_shared.dir/bpf_share.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:229: misc/CMakeFiles/openvas_misc_shared.dir/all] Error 2
make: *** [Makefile:166: all] Error 2
make: Leaving directory '/home/rek2/.cache/paru/clone/openvas-scanner/src/build'
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'openvas-scanner-23.9.0-2': 
error: can't build ospd-openvas-22.7.1-1, deps not satisfied: openvas-scanner
error: packages failed to build: openvas-scanner-23.9.0-2  ospd-openvas-22.7.1-1

BTW why is there a gsa and a greenbone-security-assistant package? both seem very new, which one should I use?

1 2 3 4 5 Next › Last »