[Openvas-distro] Testing OpenVAS OBS packages

Michael Wiegand michael.wiegand at greenbone.net
Wed Feb 9 17:24:47 CET 2011


Hello Stephan,

I have finally found the time to test your OBS OpenVAS packages (UNSTABLE v4) 
on openSUSE 11.3. First off, thanks a lot for the great packaging and your 
tireless efforts to make installing OpenVAS ever easier. :)

I have a few quick notes, mostly about packaging in general, so I'm CCing 
openvas-distro, I hope you don't mind.

I tried to approach this somewhat from the user perspective, i.e. I install 
the packages and want a working installation without having to do too much 
myself. I noticed that I had to do several taks before my installation was 
operational:

1) Do a Feed Synchronization with openvas-nvt-sync.
2) Create client certificates and the om user for the manager so it can talk 
to the scanner.
3) Start the scanner so it builds the initial cache.
4) Start openvas-manager with --rebuild to initialize the manager DB.
5) Start the manager.
6) Start the GSA
7) Create an Admin user so I can login on the GSA and create more users.

From a packager perspective, I can understand not wanting to do all this 
during installation, but from the perspective of a user who is new to OpenVAS 
I'd about ready to stop trying after step 2 and would probably remove the 
package again.

I know OpenVAS has a steep learning curve and requires some skills to use, but 
I think it should be easy to install the packages and get a first taste.

I don't know what would be the best solution for this; maybe an optional 
guided configuration using the steps mentioned above, like other 
(mail/file/web)server packages do?

Would this make more sense in packaging or is that something OpenVAS should 
provide itself?

Looking forward to your feedback on this, opinions from other packagers are 
welcome as well of course.

Some more minor issues:
- I noticed the NVT and the cache directory (/var/lib/openvas/ 
and /var/cache/openvas/) are not present after installation of the 
openvas-scanner package. I guess they should be part of the package, but they 
were not created during make install up until now. This is fixed in SVN 
r10262, I've attached the patch if you want to use it on your packages.
- I also noticed that gsad listen on port 9393 by default and openvasad on 
port 9392; the current default ports are the other way around.

As always, thanks for your packaging work and your patience. :)

Regards,

Michael

-- 
Michael Wiegand |  Greenbone Networks GmbH  |  http://www.greenbone.net/
Neuer Graben 17, 49074 Osnabrück, Germany | AG Osnabrück, HR B 202460
Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner

-------------- next part --------------
A non-text attachment was scrubbed...
Name: r10262.patch
Type: text/x-diff
Size: 408 bytes
Desc: not available
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20110209/200333b4/r10262.bin


More information about the Openvas-distro mailing list