On Tuesday 10 June 2008 17:48:33 Stephan Kleine wrote: > 1. I used the 10.2 src.rpms as base and just cleaned up the spec files and > added missing dependencies. The only needed patches were the $DESTDIR ones.
Are the dependencies release specific or are we missing some? > 2. openvasd complains about missing files on startup. The missing ones seem > to be: byte_func.inc, slad.inc, smb_nt.inc, url_func.inc (see > http://pastebin.ca/1043940 for the startup log) > > 3. many plug-ins complain about missing files (see > http://pastebin.ca/1043943 for openvasd.dump and > http://pastebin.ca/1043944for openvasd.messages) See your later comments, actually some work has been done on the Windows checks. > 4. The certificates that are generated for the server end up in > /usr/com/openvas/CA/, which is, to the best of my knowledge, at least > unorthodox. If one doesn't use already existing certificates but the > generated ones they would be specific for that service / server and > therefore should be in /var/lib/openvas/CA/ or /etc/openvas too to prevent > clutter. Interesting, on Debian they end up in /var/lib/openvas/CA. Are you applying the patch? I think openvas-server trunk fixes it, but the original ./configure defines localstatedir as PREFIX/com (which is where your problems are probably coming from). The patched Makefile over rules this. > 5. The icon doesn't work for the menu entry because in > OpenVAS-Client.desktop it is referred to OpenVAS.xpm and not > OpenVAS-Client.xpm. Also the format of that icon is just wrong for a little > thumbnail that should be shown in a menu left of the programs name / > description because it is far from being a square. The OpenVAS-Client.desktop file has been fixed in trunk of openvas-client. > 6. I haven't found a way to point the client to the correct manual > location. It always tries to load > /usr/share/doc/OpenVAS/users-manual-de.pdf which doesn't exist since I > configured the openvas-manual rpm to put its content into the clients doc > directory (/usr/share/doc/packages/openvas-client/) This is a bug, I have changed openvas-client trunk to look for the manual in PREFIX/share/doc/openvas-manual. > If I understood the mails in your archive right 2&3 are because some files > had to be removed cause of copyright issues and will be resolved over the > time but please have a look at 4-6 since those aren't hard to fix but still > buggers. I agree, 5 and 6 are fixed in trunk, I believe 4 is because the patch isn't being applied. If you can investigate this, that would be helpful. > Further I wanted to bring the openSUSE Build Service to your attention and > to suggest that you use it to build your project because: Jan is mostly responsible for the opensuse spec files so I'll defer to him, but I agree it sounds very useful. > Last but not least I wanted to inform you that I requested the replacement > of Nessus with OpenVAS in openSUSE 11.1 (since it is too late for 11.0) and > my request got accepted: > https://bugzilla.novell.com/show_bug.cgi?id=396251. So, if you > consider using the Build Service (which I really hope ;)), > please use that feature request to coordinate it with the openSUSE devs to > avoid duplicated work. Fantastic, many thanks. Hopefully, we'll be ready with a nice stable build in time for that release. Many thanks for the bug reports, Tim -- Tim Brown <mailto:[EMAIL PROTECTED]> <http://www.nth-dimension.org.uk/> _______________________________________________ Openvas-devel mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
