From waja at cyconet.org  Tue Sep  8 08:53:18 2009
From: waja at cyconet.org (Jan Wagner)
Date: Tue, 8 Sep 2009 08:53:18 +0200
Subject: [Openvas-distro] openvas-server/mips: /usr/bin/ld: cannot find -ll
Message-ID: <200909080853.22304.waja@cyconet.org>

Hi there,

can please anybody have a look into 
https://buildd.debian.org/~luk/status/package.php?p=openvas-server#fail-
openvas-server-mips ? I don't have access to mips hardware (or lacking the 
information how), so could please anybody take some minutes to investigate.

Thanks and With kind regards, Jan.
P.S. Please keep me in CC, I'm not subscribed to debian-mips
-- 
Never write mail to <waja at spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090908/d96d9202/attachment.pgp

From waja at cyconet.org  Tue Sep  8 10:00:55 2009
From: waja at cyconet.org (Jan Wagner)
Date: Tue, 8 Sep 2009 10:00:55 +0200
Subject: [Openvas-distro] openvas-server/mips: /usr/bin/ld: cannot find
	-ll
In-Reply-To: <200909080853.22304.waja@cyconet.org>
References: <200909080853.22304.waja@cyconet.org>
Message-ID: <200909081001.00147.waja@cyconet.org>

On Tuesday 08 September 2009 08:53:18 Jan Wagner wrote:
> can please anybody have a look into
> https://buildd.debian.org/~luk/status/package.php?p=openvas-server#fail-
> openvas-server-mips ? I don't have access to mips hardware (or lacking the
> information how), so could please anybody take some minutes to investigate.

Could please try to apply the following and try to build:

+--- openvas-libraries-2.0.4~/libopenvas-config.in      2009-08-07 
12:23:15.000000000 +0200
++++ openvas-libraries-2.0.4/libopenvas-config.in       2009-09-08 
09:24:04.000000000 +0200
+@@ -35,7 +35,7 @@
+ LIBDIR=@libdir@
+ INCLUDEDIR=@includedir@
+ VERSION=@version@
+-EXTRA="@EXTRA@ @llib@"
++EXTRA="@EXTRA@"
+ EGDPATH="@egdpath@"
+
+


Thanks and With kind regards, Jan.
P.S. Please keep me in CC, I'm not subscribed to debian-mips
-- 
Never write mail to <waja at spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090908/08d08ec2/attachment.pgp

From jfs at computer.org  Sun Sep 20 01:13:53 2009
From: jfs at computer.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=)
Date: Sun, 20 Sep 2009 01:13:53 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] Hardening OpenVAS
In-Reply-To: <200908191511.21302.timb@openvas.org>
References: <200908191511.21302.timb@openvas.org>
Message-ID: <20090919231353.GA24710@javifsp.no-ip.org>

On Wed, Aug 19, 2009 at 03:11:19PM +0100, Tim Brown wrote:
> Does anyone have any issues with such a plan?

No issues at all, I actually applaud it!

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/20090920/47dcd4ad/attachment.pgp

From jfs at computer.org  Sun Sep 20 01:29:28 2009
From: jfs at computer.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=)
Date: Sun, 20 Sep 2009 01:29:28 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
 Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <200909181651.29063.waja@cyconet.org>
References: <20090915125109.GA8665@mx.putzo.net>
	<200909152107.37505.waja@cyconet.org>
	<200909181651.29063.waja@cyconet.org>
Message-ID: <20090919232928.GC24710@javifsp.no-ip.org>

On Fri, Sep 18, 2009 at 04:51:24PM +0200, Jan Wagner wrote:
> I decided to create a openvas-plugins package based on the latest upstream 
> release but recreating the tarball after doing:
> 
> rm -rf audit/ docs/ extra/ packaging/ scripts/ template.nasl
> 
> This removes all the stuff we needed to get rid due license/copyright issues. 
> Just the stuff for openvas-nvt-sync and the nes-plugins are left.
> 

Several comments:

- repackage the original source and consider renaming it to
  'openvas-plugins-dfsg' (add Provides: openvas-plugins) 
  to avoid confusion with former packages or packages distributed upstream

- don't remove the audit/, docs/ or extra/ subdirs. There is nothing there
  that has license issues. And the 'audit' scripts are actually useful to
  ensure that everything is OK.

- remove from the scripts *all* that the audit scripts report as not good
  according to license. Actually, this package could provide all the scripts
  that were formerly in the nessus-plugins package (and maybe even more)

Since this package has been rejected in the past it would be wise to review
it on the basis of http://ftp-master.debian.org/REJECT-FAQ.html to ensure
that it will go into Debian proper.

Also, as we discussed @ Debconf, a package with some plugins might be useful
for users that install OpenVAS without Internet access or the change of
running openvas-nvt-sync (internal networks with no rsync access, for
example). It would be nice if the openvas-plugins package provided at Debian
include a simple plugin (which would be removed when running
openvas-nvt-sync) alerting to the users on the need to update.

> Any objections to remove openvas-nvt-sync again from openvas-server and 
> uploading openvas-plugins? 

I agree to the change, but if you upload openvas-plugins please do what I
said above.


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/20090920/a80a5edf/attachment.pgp

From jfs at computer.org  Sun Sep 20 01:52:25 2009
From: jfs at computer.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=)
Date: Sun, 20 Sep 2009 01:52:25 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
 Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <20090919232928.GC24710@javifsp.no-ip.org>
References: <20090915125109.GA8665@mx.putzo.net>
	<200909152107.37505.waja@cyconet.org>
	<200909181651.29063.waja@cyconet.org>
	<20090919232928.GC24710@javifsp.no-ip.org>
Message-ID: <20090919235225.GD24710@javifsp.no-ip.org>


In addition to the comments I provided:

- Restore the package history (you started it from scratch)
- Joey already started some work early this year to provide a DFSG-free
  version of the plugins which is available at
  http://people.debian.org/~joey/stuff/openvas/plugins/
- Since the package will be updated from SVN it might be wiser to use 
  a date and not a release

  Maybe that work can be reused? I

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/20090920/d14fbc23/attachment.pgp

From waja at cyconet.org  Sun Sep 20 20:34:43 2009
From: waja at cyconet.org (Jan Wagner)
Date: Sun, 20 Sep 2009 20:34:43 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
	Was: Bug#546746: openvas-server: wrong plugin directory
Message-ID: <200909202034.44479.waja@cyconet.org>

Hi there,

On Sunday 20 September 2009, Javier Fern?ndez-Sanguino Pe?a wrote:
> Based on Joey's and Jan's work I've worked on an openvas-plugins-dfsg which
> includes both the openvas-nvt-sync as well as the plugin scripts. In order
> to do so I have reviewed (again) the plugins at openvas-plugins (1.0.7)
> release and removed all the non-DFSG stuff [1]

I see at least two reasons which may cause problems:

* scripts from latest upstream openvas-plugins are outdated and there 
shouldn't be any new upstream releases, so including the scripts may not make 
sence 
* openvas-nvt-sync and the nes-plugins are included into openvas-server in 
upstream trunk allready

My plan was, to just provide a _minimal_ package which includes only the 
requirements to use the plugin feed, since the plugins package itself are not 
maintained anymore. As soon as we have this components in openvas-server, I 
thought about defering the plugins package.

My reasons for not including the the plugins was:

* plugins outdated
* reviewing all the stuff is timeconsuming and gives you copyright/license 
headache
* when dropping the plugin package, we have the complete set of tools inside 
of openvas-server (same set of functionality)

> Please test and provide comments on the above packagse, if everybody agrees
> I will commit them to SVN and upload the packages.

Since I don't like neither the idea of shiping outdated scripts in our package 
nor going to the pain of reviewing all the new plugins for license/copyright 
issues ... what about splitting the stuff into 2 packages? For example 
openvas-plugins and openvas-plugins-base? The first just provides openvas-nvt-
sync and the required nes-plugins, which can disapear when these are merged 
into a upstream release. The second are just the addition plugins and stuff. 
Taking openvas-plugins-base from latest upstream release may be fine, if 
anybody gets this through NEW.
For my part, I would not upload any package to the archive shipped with 
plugins which are not reviewed by ftp-master. Means, if anybody is uploading 
the package based on 1.0.7 and ftp-master is passing it into it, I would 
happily upload a package based on this plugins. If a package includes an 
additional set of plugins, I don't care about, since the chance is too high to 
get into license/copyright troubles.
Maybe we can just upload a package with reduced upstream footprint to provide 
openvas-plugins (remember, just openvas-nvt-sync and the required nes-plugins) 
and an addition source tarball with any additional plugins (maybe from svn 
trunk or anything else). Keep in mind ... for those who wants to use the 
feeds, the additional plugins are without interests.

Anyways ... people.d.o is not reachable at the moment. So Javier, please 
reconsider to give the involved people more time so get their opinion about 
what you have done.

With kind regards, Jan.

From waja at cyconet.org  Sun Sep 20 20:42:09 2009
From: waja at cyconet.org (Jan Wagner)
Date: Sun, 20 Sep 2009 20:42:09 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
	Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <20090919232928.GC24710@javifsp.no-ip.org>
References: <20090915125109.GA8665@mx.putzo.net>
	<200909181651.29063.waja@cyconet.org>
	<20090919232928.GC24710@javifsp.no-ip.org>
Message-ID: <200909202042.16236.waja@cyconet.org>

Good evening Javier,

On Sunday, 20. September 2009, Javier Fern?ndez-Sanguino Pe?a wrote:
> > Any objections to remove openvas-nvt-sync again from openvas-server and 
> > uploading openvas-plugins? 
> 
> I agree to the change, but if you upload openvas-plugins please do what I
> said above

I don't know, if this was your intention, but in my ears this sounds a little 
bit to harsh.

With kind regards, Jan.
-- 
Never write mail to <waja at spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090920/ffc049ee/attachment.pgp

From jfs at computer.org  Sun Sep 20 21:45:33 2009
From: jfs at computer.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=)
Date: Sun, 20 Sep 2009 21:45:33 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
 Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <200909202034.44479.waja@cyconet.org>
References: <200909202034.44479.waja@cyconet.org>
Message-ID: <20090920194533.GA2406@javifsp.no-ip.org>

On Sun, Sep 20, 2009 at 08:34:43PM +0200, Jan Wagner wrote:
> I see at least two reasons which may cause problems:
> 
> * scripts from latest upstream openvas-plugins are outdated and there
> shouldn't be any new upstream releases, so including the scripts may not
> make sence 

That's easy to fix. Just replace the plugins with the latest versions in SVN
and you are done. I'm actually doing that right now for the next version.

> * openvas-nvt-sync and the nes-plugins are included into openvas-server in 
> upstream trunk allready

But we don't have that version in Debian yet. I think we should focus in
trying to fix the current situation.

> My plan was, to just provide a _minimal_ package which includes only the 
> requirements to use the plugin feed, since the plugins package itself are not 
> maintained anymore. As soon as we have this components in openvas-server, I 
> thought about defering the plugins package.
> 
> My reasons for not including the the plugins was:
> 
> * plugins outdated

Easily fixed.

> * reviewing all the stuff is timeconsuming and gives you copyright/license 
> headache

I already wasted my time and did the review, so this is no longer a reason.

> * when dropping the plugin package, we have the complete set of tools inside 
> of openvas-server (same set of functionality)

This is a reason for not providing openvas-plugins in the future, but not
*now*

> > Please test and provide comments on the above packagse, if everybody agrees
> > I will commit them to SVN and upload the packages.
> 
> Since I don't like neither the idea of shiping outdated scripts in our package 
> nor going to the pain of reviewing all the new plugins for license/copyright 
> issues ... what about splitting the stuff into 2 packages? For example 
> openvas-plugins and openvas-plugins-base? The first just provides openvas-nvt-
> sync and the required nes-plugins, which can disapear when these are merged 
> into a upstream release. The second are just the addition plugins and stuff. 
> Taking openvas-plugins-base from latest upstream release may be fine, if 
> anybody gets this through NEW.

The only complain from the ftp-masters on the openvas-plugins packages
uploaded early in January this year were the Gentoo scripts. I have dedicated
quite a lot of time to review any other scripts missing the licenses.

Since the license review has been already done I don't believe it makes sense
to provide two packages. The package, as it is, should go just fine through
NEW.

> Anyways ... people.d.o is not reachable at the moment. So Javier, please 
> reconsider to give the involved people more time so get their opinion about 
> what you have done.

Sure, I can give more time. 

However, as I said in the past: it is to the benefit of our (Debian) users
that we provide a set of plugins so that you can do a basic OpenVAS check
without requiring downloading stuff over the Internet (there's some
installations in which that becomes an issue). 

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/20090920/310a2b7f/attachment.pgp

From jfs at computer.org  Mon Sep 21 08:54:37 2009
From: jfs at computer.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=)
Date: Mon, 21 Sep 2009 08:54:37 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
 Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <200909202034.44479.waja@cyconet.org>
References: <200909202034.44479.waja@cyconet.org>
Message-ID: <20090921065437.GA29429@javifsp.no-ip.org>

On Sun, Sep 20, 2009 at 08:34:43PM +0200, Jan Wagner wrote:
> Anyways ... people.d.o is not reachable at the moment. So Javier, please 
> reconsider to give the involved people more time so get their opinion about 
> what you have done.

Since it is still down I've also uploaded the new openvas-plugins-dfsg and
openvas-server packages to http://www.gsyc.es/~jfs/openvas/

Regards

Javier

From waja at cyconet.org  Mon Sep 21 12:37:07 2009
From: waja at cyconet.org (Jan Wagner)
Date: Mon, 21 Sep 2009 12:37:07 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
	Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <20090920194533.GA2406@javifsp.no-ip.org>
References: <200909202034.44479.waja@cyconet.org>
	<20090920194533.GA2406@javifsp.no-ip.org>
Message-ID: <200909211237.13039.waja@cyconet.org>

Hi Javier,

On Sunday 20 September 2009 21:45:33 Javier Fern?ndez-Sanguino Pe?a wrote:
> Since the license review has been already done I don't believe it makes
> sense to provide two packages. The package, as it is, should go just fine
> through NEW.

okay .. lets try again. I know you love the idea to ship plugins within our 
packages. I can understand, that this may make sence for the situations where 
it is not possible to get the plugin feed.

From my POV we shoudl provide at least a (binary) package, which gives you 
only the (core) functionelity to recieve the latest plugins via the feed. This 
package requires the openvas-nvt-sync binary and the nes-plugins.

Reasons:

* this functionelity is integrated into openvas-server in trunk and openvas-
plugins is defered. As long as we keep this stuff in a seperate package, we 
can drop this package later and provide this package with openvas-server in 
the future without any issue for our users
* installing additional plugins with the package does not make sence for 
people who just wants to use the feed (reducing package/software footprint)

Additionally to this package, we _could_ provide one or more additionall 
plugins shipping the feeds. Maybe one of latest plugins provided by upstream 
(which we can build from the same source package as the core package) and 
maybe others from other sources.

To make things short ... please split the package into two binary packages (or 
even more, if you want), to make life easier for our users!

Thanks and with kind regards, Jan.
-- 
Never write mail to <waja at spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090921/552934f7/attachment.pgp

From waja at cyconet.org  Mon Sep 21 12:38:52 2009
From: waja at cyconet.org (Jan Wagner)
Date: Mon, 21 Sep 2009 12:38:52 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
	Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <200909211237.13039.waja@cyconet.org>
References: <200909202034.44479.waja@cyconet.org>
	<20090920194533.GA2406@javifsp.no-ip.org>
	<200909211237.13039.waja@cyconet.org>
Message-ID: <200909211238.52961.waja@cyconet.org>

Just a short copy&past from IRC (with permission from Jan):

12:23:19 < jan_oliver> about the strategy wrt openvas-plugins: In 3.0 we want 
to have openvas-libraries and openvas-scanner the only two modules required to 
run the scanner daemon.
12:23:34 < jan_oliver> -scanner will have the remaining *.nes plugins as well 
as the sync script-
12:24:08 < jan_oliver> the developers use the openvas-plugins module for their 
work, but there will be not releases of this module.
12:24:40 < jan_oliver> Instead, with each update of the feed, we will create a 
tar-ball with the date as version.
12:25:26 < jan_oliver> The sync script shall be extended to download the tar 
ball in case of a fresh installation to significantly speed up first sync.
12:26:42 < jan_oliver> So, packaging the NVTs could mean to grab the latest 
tar ball and install it into the NVT directory.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090921/18154ee9/attachment.pgp

From waja at cyconet.org  Mon Sep 21 13:09:35 2009
From: waja at cyconet.org (Jan Wagner)
Date: Mon, 21 Sep 2009 13:09:35 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
	Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <20090921065437.GA29429@javifsp.no-ip.org>
References: <200909202034.44479.waja@cyconet.org>
	<20090921065437.GA29429@javifsp.no-ip.org>
Message-ID: <200909211309.38955.waja@cyconet.org>

Hi Javier,

On Monday 21 September 2009 08:54:37 Javier Fern?ndez-Sanguino Pe?a wrote:
> On Sun, Sep 20, 2009 at 08:34:43PM +0200, Jan Wagner wrote:
> > Anyways ... people.d.o is not reachable at the moment. So Javier, please
> > reconsider to give the involved people more time so get their opinion
> > about what you have done.
>
> Since it is still down I've also uploaded the new openvas-plugins-dfsg and
> openvas-server packages to http://www.gsyc.es/~jfs/openvas/

There are a couple of problems reported by lintian

$ lintian ../openvas-plugins-dfsg_1.0.7-3+svn20090920.dsc
W: openvas-plugins-dfsg source: patch-system-but-direct-changes-in-diff 
audit/NOTES and 9692 more
$ lintian ../openvas-plugins-dfsg_1.0.7-3+svn20090920_i386.deb
W: openvas-plugins-dfsg: binary-without-manpage usr/sbin/openvas-nvt-sync
E: openvas-plugins-dfsg: read-in-maintainer-script postrm:9
E: openvas-plugins-dfsg: read-in-maintainer-script postrm:24
E: openvas-plugins-dfsg: missing-dependency-on-libc needed by 
./var/lib/openvas/plugins/find_service.nes and 3 others

some other stuff I've found when having a quick look:

* you forgot to install your manpage for openvas-nvt-sync
* the nes-plugins should IMHO be in /usr/lib and not in /var/lib, since that 
are shared libraries
* please, please consider splitting the binary packages.

With kind regards, Jan.
-- 
Never write mail to <waja at spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090921/b97542e3/attachment.pgp

From kost at linux.hr  Mon Sep 21 15:09:19 2009
From: kost at linux.hr (Vlatko Kosturjak)
Date: Mon, 21 Sep 2009 15:09:19 +0200
Subject: [Openvas-distro] [Fwd: [Openvas-commits] r5095 -
	trunk/openvas-libraries]
Message-ID: <4AB77AFF.3040501@linux.hr>

I'm including this on -devel and -distro mailing list as it is 
concerning package maintainers as well. It is regarding pkg-config 
implementation for new openvas-libraries in 3.x.

openvas-libraries ship with libnasl and openvas-lib now. As client 
doesn't need libnasl, should:

[1] we have more pkg-configs files for each configuration - e.g.
libopenvas-nasl for linking server type versions
libopenvas-client for linking client type versions
(or any other naming convention)

[2] ..or we should have single pkg-config which will link all libraries 
and that's it?

Also, would be correct to have version in libopenvas like glib have i.e. 
  libglib-2.0, or we should have single (libopenvas) and package 
mainteners would do it differently if they feel it for each distro?

Let me know, so we can proceed further with pkg-config support 
implementation.

-------- Original Message --------
Subject: [Openvas-commits] r5095 - trunk/openvas-libraries
Date: Mon, 21 Sep 2009 14:52:40 +0200 (CEST)
From: scm-commit at wald.intevation.org
Reply-To: openvas-devel at wald.intevation.org
To: openvas-commits at wald.intevation.org

Author: kost
Date: 2009-09-21 14:52:40 +0200 (Mon, 21 Sep 2009)
New Revision: 5095

Added:
    trunk/openvas-libraries/libopenvas.pc.in
Modified:
    trunk/openvas-libraries/ChangeLog
Log:
Initial support for pkg-config



Modified: trunk/openvas-libraries/ChangeLog
===================================================================
--- trunk/openvas-libraries/ChangeLog	2009-09-21 12:35:03 UTC (rev 5094)
+++ trunk/openvas-libraries/ChangeLog	2009-09-21 12:52:40 UTC (rev 5095)
@@ -1,3 +1,7 @@
+2009-09-21  Vlatko Kosturjak <kost at linux.hr>
+
+	* libopenvas.pc.in: new file, support for pkg-config
+
  2009-09-21  Felix Wolfsteller <felix.wolfsteller at intevation.de>

  	* base/openvas_certificate_file.c: Commented another show_error,

Added: trunk/openvas-libraries/libopenvas.pc.in
===================================================================
--- trunk/openvas-libraries/libopenvas.pc.in	2009-09-21 12:35:03 UTC 
(rev 5094)
+++ trunk/openvas-libraries/libopenvas.pc.in	2009-09-21 12:52:40 UTC 
(rev 5095)
@@ -0,0 +1,11 @@
+prefix=@prefix@
+exec_prefix=@exec_prefix@
+libdir=@libdir@
+includedir=@includedir@
+
+Name: openvas-libraries
+Description: OpenVAS libraries
+Version: @version@
+Requires: glib-2.0 = 2.8.0
+Cflags: -I${includedir}
+Libs: -L${libdir} -lglib

_______________________________________________
Openvas-commits mailing list
Openvas-commits at wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-commits

From matthew.mundell at intevation.de  Mon Sep 21 15:31:25 2009
From: matthew.mundell at intevation.de (Matthew Mundell)
Date: 21 Sep 2009 13:30:25 -0001
Subject: [Openvas-distro] [Fwd: [Openvas-commits] r5095
	-									trunk/openvas-libraries]
In-Reply-To: Message of Mon, 21 Sep 2009 15:09:19 +0200.
	<4AB77AFF.3040501@linux.hr>
Message-ID: <20090921133112.5EB4EDF7BC@mail.ukfsn.org>

> openvas-libraries ship with libnasl and openvas-lib now. As client
> doesn't need libnasl, should:

There is also the OMP library to consider.  Soon there'll be libopenvas_net
too.  OMP clients could require only libopenvas_omp, so if we're choosing
[1], it should be possible to choose only that library.

> [1] we have more pkg-configs files for each configuration - e.g.
> libopenvas-nasl for linking server type versions
> libopenvas-client for linking client type versions
> (or any other naming convention)

Probably something like libopenvas-base, libopenvas-net, libopenvas-nasl
and libopenvas-omp.  libopenvas_misc could be provided by libopenvas_base,
I think.

> [2] ..or we should have single pkg-config which will link all libraries
> and that's it?

This is a much simpler immediate solution.  It's what libopenvas-config is
doing now.

From jfs at computer.org  Mon Sep 21 16:39:45 2009
From: jfs at computer.org (Javier Fernandez-Sanguino)
Date: Mon, 21 Sep 2009 16:39:45 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
	Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <200909211309.38955.waja@cyconet.org>
References: <200909202034.44479.waja@cyconet.org>
	<20090921065437.GA29429@javifsp.no-ip.org>
	<200909211309.38955.waja@cyconet.org>
Message-ID: <f3c99a80909210739m4fee200cxd35435c8ddb4f5ea@mail.gmail.com>

El d?a 21 de septiembre de 2009 13:09, Jan Wagner <waja at cyconet.org> escribi?:
> There are a couple of problems reported by lintian

Yes, I've seen those.

> some other stuff I've found when having a quick look:
>
> * you forgot to install your manpage for openvas-nvt-sync

This should has been fixed in the version I uploaded this morning
(-3+svn20090920)

> * the nes-plugins should IMHO be in /usr/lib and not in /var/lib, since that
> are shared libraries

This too is fixed. Did you pick up the latest version?

> * please, please consider splitting the binary packages.

Based on the information you sent I suggest we provide a single binary
package right now and *when* upstream provides a tar.gz for
openvas-plugins then we just change the package to use those sources
instead. Since those sources will not include the .nes files or the
sync script it would be an easy switch.

I don't see how splitting into two binary packages make sense in the long run.
If we have one binary package:

Right now: add one dependency in openvas-server. To
openvas-plugins-dfsg (a Depends:)

In the future: add in openvas-scanner/server a Conflicts: to the
version of openvas-plugins-dfsg whicih provided the .nes and sync file
(to prevent file conflicts) and downgrade the Depends to a Recommends
(so people can opt out from installing the openvas-plugins-dfsg
package)

If we have two binary packages:

Right now:
We have two add dependencies in the openvas-server packages:
   - one to openvas-plugins-base (which provides sync and .nes). This
should be a Depends:
   - one to openvas-plugins-dfsg. This could be a Recommends:

In the future:
  - openvas-scanner/server would have to Conflicts: with the older
version openvas-plugins-base package  (to prevent file conflicts)
  - remove the openvas-plugins-base package from the archive

The solution with two packages looks more complicated to me and does
not seem like a value-added service for our users.

Pray tell me why do you think that splitting openvas-plugins-dfsg into
two binary packages makes life any easier to our users.

Regards

Javier

From waja at cyconet.org  Mon Sep 21 20:50:59 2009
From: waja at cyconet.org (Jan Wagner)
Date: Mon, 21 Sep 2009 20:50:59 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
	Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <f3c99a80909210739m4fee200cxd35435c8ddb4f5ea@mail.gmail.com>
References: <200909202034.44479.waja@cyconet.org>
	<200909211309.38955.waja@cyconet.org>
	<f3c99a80909210739m4fee200cxd35435c8ddb4f5ea@mail.gmail.com>
Message-ID: <200909212051.06068.waja@cyconet.org>

Hi Javier,

On Monday, 21. September 2009, Javier Fernandez-Sanguino wrote:
> If we have two binary packages:
> 
> Right now:
> We have two add dependencies in the openvas-server packages:
>    - one to openvas-plugins-base (which provides sync and .nes). This
> should be a Depends:
>    - one to openvas-plugins-dfsg. This could be a Recommends:
> 
> In the future:
>   - openvas-scanner/server would have to Conflicts: with the older
> version openvas-plugins-base package  (to prevent file conflicts)
>   - remove the openvas-plugins-base package from the archive

this looks good for me. 

> The solution with two packages looks more complicated to me and does
> not seem like a value-added service for our users.
> 
> Pray tell me why do you think that splitting openvas-plugins-dfsg into
> two binary packages makes life any easier to our users.

For those who just want to use the feed, there are too problems when shiping 
all the stuff in one binary package:

* most people (with security conserns) are trying to keep installed footprint 
(packages/binaries/...) as small as possible, shipping unused plugins for this 
case doesn't match that strategy
* when installing the plugins via our package and syncing the plugins from 
feed, users overwrite and/or remove scripts which should be there (looking 
from package managment of view)

Also .. from my point of view openvas-plugins is a volatile package and if we 
split the plugins into a seperate package, life will be more easier to update 
it possible via volatile.debian.org.

I would also like to have more opinions from others, if is makes more sence to 
ship all together at once or just split the infrastructure and the plugins 
stuff into seperate packages.

Thanks for sharing ideas, Jan.
P.S. I also would be interested into the disadvantage of having multiple 
binary packages (beside the small work of repackaging).
-- 
Never write mail to <waja at spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090921/a473dd62/attachment-0001.pgp

From jfs at computer.org  Wed Sep 23 01:23:16 2009
From: jfs at computer.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=)
Date: Wed, 23 Sep 2009 01:23:16 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] openvas-plugin package
 Was: Bug#546746: openvas-server: wrong plugin directory
In-Reply-To: <200909212051.06068.waja@cyconet.org>
References: <200909202034.44479.waja@cyconet.org>
	<200909211309.38955.waja@cyconet.org>
	<f3c99a80909210739m4fee200cxd35435c8ddb4f5ea@mail.gmail.com>
	<200909212051.06068.waja@cyconet.org>
Message-ID: <20090922232316.GB11286@javifsp.no-ip.org>

On Mon, Sep 21, 2009 at 08:50:59PM +0200, Jan Wagner wrote:
> For those who just want to use the feed, there are too problems when shiping 
> all the stuff in one binary package:

Well, based on my experience with nessus-plugins I don't share your concerns
on the plugins package. I've haven't had any major issues in the 10 years (!)
that nessus-plugins + it's accompanying nessus-update-plugins script.

In any case, I have prepared a new version of the openvas-plugins package and
have uploaded it (version 1.0.7-4+svn20090920) which splits the plugin
contents. 

It should fix all your concerns. Please take a look at it and let me know if
it's OK for you. 

BTW, I have not fixed some of the lintian errors and added an override. The
reasoning why is in the changelog. If you want more info then shoot me an
email.

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/20090923/34f2be75/attachment.pgp

From Jan-Oliver.Wagner at greenbone.net  Wed Sep 23 08:16:07 2009
From: Jan-Oliver.Wagner at greenbone.net (Jan-Oliver Wagner)
Date: Wed, 23 Sep 2009 08:16:07 +0200
Subject: [Openvas-distro] branches in openvas-packaging?
Message-ID: <200909230816.09259.Jan-Oliver.Wagner@greenbone.net>

Hi,

shouldn't "trunk/openvas-packaging/openvas-libraries/debian/trunk" be branched to something like "trunk/openvas-packaging/openvas-libraries/debian/2-0-branch" so that the 3.0.0 modifications can go to trunk without causing trouble for the next 2.0.x releases?

Best

	Jan

-- 
Dr. Jan-Oliver Wagner |  ++49-541-335084-0  |  http://www.greenbone.net/
Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Osnabr?ck, HR B 202460
Gesch?ftsf?hrer: Lukas Grunwald, Dr. Jan-Oliver Wagner

From Jan-Oliver.Wagner at greenbone.net  Thu Sep 24 22:02:58 2009
From: Jan-Oliver.Wagner at greenbone.net (Jan-Oliver Wagner)
Date: Thu, 24 Sep 2009 22:02:58 +0200
Subject: [Openvas-distro] branches in openvas-packaging?
In-Reply-To: <200909230816.09259.Jan-Oliver.Wagner@greenbone.net>
References: <200909230816.09259.Jan-Oliver.Wagner@greenbone.net>
Message-ID: <200909242202.58827.Jan-Oliver.Wagner@greenbone.net>

On Wednesday 23 September 2009 08:16:07 Jan-Oliver Wagner wrote:
> shouldn't "trunk/openvas-packaging/openvas-libraries/debian/trunk" be branched to something like "trunk/openvas-packaging/openvas-libraries/debian/2-0-branch" so that the 3.0.0 modifications can go to trunk without causing trouble for the next 2.0.x releases?

I created now a 2-0 branch.

Attached is a simple patch to have a debian package for 3.0.0.beta1.
I am not a debian maintainer, so can please the debian guys review it
whether it makes sense. Please go ahead and commit any portion of it
you think is acceptable.

Best

	Jan
 

-- 
Dr. Jan-Oliver Wagner |  ++49-541-335084-0  |  http://www.greenbone.net/
Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabr?ck
AG Osnabr?ck, HR B 202460 | Gesch?ftsf?hrer: Lukas Grunwald, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openvas-libraries-3.0.0.beta1-debian.diff
Type: text/x-patch
Size: 3987 bytes
Desc: not available
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090924/d637f462/openvas-libraries-3.0.0.beta1-debian.bin

From waja at cyconet.org  Thu Sep 24 22:59:12 2009
From: waja at cyconet.org (Jan Wagner)
Date: Thu, 24 Sep 2009 22:59:12 +0200
Subject: [Openvas-distro] [Openvas-distro-deb] branches in
	openvas-packaging?
In-Reply-To: <200909242202.58827.Jan-Oliver.Wagner@greenbone.net>
References: <200909230816.09259.Jan-Oliver.Wagner@greenbone.net>
	<200909242202.58827.Jan-Oliver.Wagner@greenbone.net>
Message-ID: <200909242259.19718.waja@cyconet.org>

On Thursday, 24. September 2009, Jan-Oliver Wagner wrote:
> I created now a 2-0 branch.
> 
> Attached is a simple patch to have a debian package for 3.0.0.beta1.
> I am not a debian maintainer, so can please the debian guys review it
> whether it makes sense. Please go ahead and commit any portion of it
> you think is acceptable.

I copied all the other modules to openvas/trunk/openvas-packaging/openvas-
*/debian/2-0/.

We should keep our packaging there until we start working on 3.x branch.

With kind regards, Jan.
-- 
Never write mail to <waja at spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/openvas-distro/attachments/20090924/656270ca/attachment.pgp