From scott at atomicrocketturtle.com Wed Jun 3 22:07:40 2009 From: scott at atomicrocketturtle.com (Scott R. Shinn) Date: Wed, 03 Jun 2009 16:07:40 -0400 Subject: [Openvas-distro] Release Announcement: openvas-server 2.0.2 RPM packages Message-ID: <1244059660.3648.8412.camel@winona> openvas-server 2.0.2 has been update in the [atomic] rpm repository for: * CentOS 4 * CentOS 5 * RHEL 4 * RHEL 5 * Fedora 4-10 available for both i386 and x86_64 platforms. The atomic yum repository is available at: http://www.atomicrocketturtle.com Short Installation instructions: Step 1) Configure the repository for your system using the installer wget -q -O - http://www.atomicorp.com/installers/atomic |sh Step 2) Install openvas-server yum install openvas-server or to Upgrade yum upgrade openvas-server -Scott -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090603/f4b08d7d/attachment.pgp From felix.wolfsteller at intevation.de Thu Jun 4 09:14:17 2009 From: felix.wolfsteller at intevation.de (Felix Wolfsteller) Date: Thu, 4 Jun 2009 09:14:17 +0200 Subject: [Openvas-distro] Missing plugin_timeout option in Debian packages openvasd.conf Message-ID: <200906040914.17624.felix.wolfsteller@intevation.de> I noticed that in openvas-server/packaging/debian/openvasd.conf no plugin_timeout is set. The server then uses the default timeout. It appears that the default value in this special case - where the file exists, but the parameter is missing - is around 1 second (which has to be confirmed and would have to be changed in code asap, imho). One second is definately too short for a couple of NVTs to report correctly. Unfortunately it is not reported to the client if a NVT is killed because it hit the timeout (a log-message is put to openvasd.messages, though). I think the plugin_timeout should be set. If there is a specific reason to not set it, it should at least be in a commented line, so that users are aware of this option in openvasd.conf. -- felix -- Felix Wolfsteller | ++49-541-335 08 3451 | http://www.intevation.de/ PGP Key: 39DE0100 Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From felix.wolfsteller at intevation.de Thu Jun 4 13:02:30 2009 From: felix.wolfsteller at intevation.de (Felix Wolfsteller) Date: Thu, 4 Jun 2009 13:02:30 +0200 Subject: [Openvas-distro] Fwd: Re: Missing plugin_timeout option in Debian packages openvasd.conf Message-ID: <200906041302.30304.felix.wolfsteller@intevation.de> The short timeout was induced by my openvas-client. If the 'plugins_timeout' key is not present in openvasd.conf the plugins_timeout value defaults to 320 (5 Minutes 20 seconds) as expected. I still find that this parameter should be present in an openvasd.conf. So, to expose the parameter in openvasd.conf without changing the value of the parameter itself it could be set to 320. Btw: Testing changed plugins_timeout values is difficult due to openvas-client misbehaving a bit. If you seriously want to test the effects of a changed global timeout setting, remove the openvasrc(s) of your client. -- felix -- Felix Wolfsteller | ++49-541-335 08 3451 | http://www.intevation.de/ PGP Key: 39DE0100 Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From jfs at computer.org Thu Jun 25 00:58:11 2009 From: jfs at computer.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=) Date: Thu, 25 Jun 2009 00:58:11 +0200 Subject: [Openvas-distro] Fwd: Re: Missing plugin_timeout option in Debian packages openvasd.conf In-Reply-To: <200906041302.30304.felix.wolfsteller@intevation.de> References: <200906041302.30304.felix.wolfsteller@intevation.de> Message-ID: <20090624225811.GA16138@javifsp.no-ip.org> On Thu, Jun 04, 2009 at 01:02:30PM +0200, Felix Wolfsteller wrote: > The short timeout was induced by my openvas-client. > > If the 'plugins_timeout' key is not present in openvasd.conf the > plugins_timeout value defaults to 320 (5 Minutes 20 seconds) as expected. > > I still find that this parameter should be present in an openvasd.conf. > > So, to expose the parameter in openvasd.conf without changing the value of > the parameter itself it could be set to 320. I've just done that. The parameter in the file is, however, commented out (since it is already the default). I've also added 'admin_user' which was the only missing other configuration value from the manual page. Regards Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090625/7c9258a8/attachment.pgp