net-analyzer/openvas 4.0 was released March 17th, 2011 There is no ebuild for it in portage yet. Reproducible: Always
Created attachment 266687 [details] ebuilds for openvas-4 Theses ebuilds adds different openvas compoments openvas-administrator openvas-gsd openvas-manager openvas-cli openvas-gsa openvas-libraries openvas-scanner I have added the option (via use flag restricted) to confined openvas as a non root user.
I had OpenVas 3.0 in my system. I'v tried a update, but got the following errors: libopenvas_nasl.a(nasl_scanner_glue.c.o): In function `script_get_preference_file_content': nasl_scanner_glue.c:(.text+0xf92): undefined reference to `get_plugin_preference_file_content' nasl_scanner_glue.c:(.text+0xfaa): undefined reference to `get_plugin_preference_file_size' I've solved the problem uninstalling old openvas libraries and tools before instaling 4.0: # emerge --unmerge net-analyzer/openvas-libraries net-analyzer/openvas-client net-analyzer/openvas-scanner I've made a meta package openvas-4.0 and will post here
Created attachment 269863 [details] OpenVAS 4.0 meta package This is a openvas meta package to made more easy the compilation of all components in OpenVAS 4.0. Obviously, you will need the other ebuilds.
It is in the pentoo overlay now, with some fixes. Any further suggestions are welcome http://trac.pentoo.ch/browser/portage/trunk/net-analyzer/openvas*
Just to inform: I had problems compiling openvas-libraries with MAKEOPTS="-j5" in a Core i5. No problems using MAKEOPTS="-j1" Problem was ld: cannot find -lopenvas_misc
(In reply to comment #5) > Just to inform: > > I had problems compiling openvas-libraries with MAKEOPTS="-j5" in a Core i5. No > problems using MAKEOPTS="-j1" > Can you be more specific? Which ebuild/version?.. have you tried to compile it manually? I have core5/amd64, compiles fine here.
(In reply to comment #6) > (In reply to comment #5) > > Just to inform: > > > > I had problems compiling openvas-libraries with MAKEOPTS="-j5" in a Core i5. > > No problems using MAKEOPTS="-j1" > > > > Can you be more specific? Which ebuild/version?.. have you tried to compile it > manually? I have core5/amd64, compiles fine here. My problem was with net-analyzer/openvas-libraries-4.0.3 sys-devel/make-3.8.2 sys-devel/gcc-4.4.5 To me, this implies a bad Makefile... Some objects need others... With MAKEOPTS="-j5", gcc will try to compile 5 packages at the same time... And that crash occurs... with -j1, no problem, because makefile grants correct order... Note: there is openvas-libraries-4.0.5 in OpenVAS site. So maybe this is ok at now?
(In reply to comment #7) I have backported a fix from 4.0.4 library 6 weeks ago in the pentoo overlay. Here it is if you want to apply it manually: http://trac.pentoo.ch/browser/portage/trunk/net-analyzer/openvas-libraries/files/openvas-libraries-4.0.3_cmake.patch Better yet run: layman -a pentoo ps. Montjoie, thank you for the initial ebuilds and very clever path hacks.
added 'pentoo' on 2011-Jun-24 initial thoughts 1) steps #3 and #4 of the net-analyzer/openvas ebuild should reflect that usernames will collide 2) step #5 should offer better cert meta management 3) for step #6, /etc/init.d/openvassd refers to "/usr/lib/openvas" which doesn't exist, /var/lib/openvas? 4) step #7, directory /var/lib/openvas/mgr needs to be created first 5) step #9 also refers to "/usr/lib/openvas", again edited to /var/lib/openvas 6) step #10 needs to indicate port 9392; https://localhost:9392/ 7) logins fail, not as per above?
continuation using the openvas-check-setup script 1) /var/lib/openvas/mgr/tasks.db should be mode 600 after being created 2) openvasmd wasn't started, this fixes the prior login failure 3) as with older versions of openvas, rc-status always indicates that openvasd crashed 4) /etc/init.d/openvasad, also refers to "/usr/lib/openvas"
dev-texlive/texlive-latexextra needs to be added as a dependency. otherwise you get zero byte PDF reports. [...] ! LaTeX Error: File `comment.sty' not found. Type X to quit or <RETURN> to proceed, or enter new name. (Default extension: sty) Enter file name: ! Emergency stop. <read *> http://seclists.org/openvas/2010/q1/336
I have just submitted the next pack of fixes (and see more to come) http://trac.pentoo.ch/changeset/2411 all issues should be fixed except "6)". gsad 2343 root 4u IPv4 252286 0t0 TCP *:https (LISTEN) Please double check and come back with more suggestions ;-)
*** Bug 298307 has been marked as a duplicate of this bug. ***
I've now initially committed openvas 4 ebuilds. For now, I'm not installing doxygen-generated docs. I may add that later if people need it. I'm also not using an openvas-user, like the pentoo ebuilds do - it's a lot of hassle and I'm not sure it's worth it. Please open new bugs for any issues you may have.
It is why in the initial ebuilds I have put a restricted use flag for people who dont want another service under root user. Just let the choice to people to choose between facility (openvas as root) and some security (openvas restricted under openvas user).
