Hi Stephan, On Tuesday 10 June 2008 18:48, Stephan Kleine wrote: > First of all I would like to thank you for forking Nessus and creating > OpenVAS! > > Further I wanted to notify you that I built OpenVAS RPMs for openSUSE 10.3 > and bring a few problems to your attention which I encountered during that > task: > > > 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.
could make available your patches spec file? > 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) this is normal. Should be less with the new openvas-plugins 1.0.1 package, did you apply this one? > 3. many plug-ins complain about missing files (see > http://pastebin.ca/1043943 for openvasd.dump and > http://pastebin.ca/1043944for openvasd.messages) normal as well. > 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. I also already wondered about this location. What does LFS say? Anyone here with a opinion where to place it? Where do similar application place their certificates? My first take would be /var/lib/openvas/CA/ but there might be better places. > 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. Would you or anyone else here be willing to create a more suitable xpm file? Also, currently we have only one logo, so in fact OpenVAS.xpm seems OK. > 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/) hm, I have to move my mind about the best location. I have no strong opinion yet. Do others have? > 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 correct. > but please have a look at 4-6 since those aren't hard to fix but still > buggers. help appreciated, at least for decision making. > Further I wanted to bring the openSUSE Build Service to your attention and > to suggest that you use it to build your project because: > > 1. It allows you to build packages for ~20 different versions of most major > distributions from a single spec file / source archive (32 & 64 bit > versions) > > 2. It provides your users with repositories specific for their distribution > & version so they can install OpenVAS via their distributions package > management and automatically receive the latest and greatest if new > packages are build. > > 3. It provides a world wide mirror infrastructure to distribute your > packages > > 4. It is very easy to use and free of charge. > > Please see http://en.opensuse.org/Build_Service for general Information. > http://en.opensuse.org/Build_Service_Tutorial is a small HowTo and > http://en.opensuse.org/Build_Service/cross_distribution_package_how_toexpla >ins how to write spec files for multiple distributions. Don't get > afraid by the KDevelop.spec example since your spec files are pretty simple > so it shouldn't be much trouble except conditional BuildRequires (feel free > to take my rpms for 10.3 from > http://download.opensuse.org/repositories/home:/bitshuffler/openSUSE_10.3/a >s a start). I thought about this already, but didn't dare to start it with my limited time. I am happy the the OpenVAS team has two guys who care about Debian packaging. Perhaps we find some SUSE enthusiasts as well :-) > 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. good news :-) Takers for the OpenSUSE integration? Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/ Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-devel mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
