Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
Hi, On Wednesday 20 February 2008 01:08, Jan-Oliver Wagner wrote: I'd like to call for voting on the change requests #1 - #4, listed here: http://www.openvas.org/openvas-crs.html I'm in favor of all four change requests. Bernhard pgp26NSOr46EY.pgp Description: PGP signature ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
On Mittwoch, 20. Februar 2008, Thomas Reinke wrote: #2 Insufficient knowledge of use scenarios to form a vote opinion, but comments as follows: NSR is, AFAIK, not broken w.r.t semi-colons. The actual NTP protocol has the same issue of being line oriented - the server replaces all semi-colons with newlines. NSR just carries this issue through to its code. Thus removing NSR does not solve the semi-colon issue, that can only be done by adding support to both client and server to support escaped semi-colons. As such, using the semi-colon problem as a justification to remove NSR doesn't make sense. Indeed it is only a first step to remove the design flaw. Fixing the protocol bug should be one of the next CRs (which will have much more impact on compatibility. I've extended the CR accordingly. Best Jan -- Dr. Jan-Oliver WagnerIntevation GmbH, Osnabrück 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 ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
#1 Adding script_oid(): In favour. #2 Insufficient knowledge of use scenarios to form a vote opinion, but comments as follows: NSR is, AFAIK, not broken w.r.t semi-colons. The actual NTP protocol has the same issue of being line oriented - the server replaces all semi-colons with newlines. NSR just carries this issue through to its code. Thus removing NSR does not solve the semi-colon issue, that can only be done by adding support to both client and server to support escaped semi-colons. As such, using the semi-colon problem as a justification to remove NSR doesn't make sense. #3 Removal of plugin factory: In favour. #4 Plugin upload: In sufficient knowledge of use scenarios to form a vote opinion. Thomas Jan-Oliver Wagner wrote: Hi, I'd like to call for voting on the change requests #1 - #4, listed here: http://www.openvas.org/openvas-crs.html Naturally, I am in favour of all 4 of them :-) However, please read and judge whether it is a good or bad idea or wether it needs further refinement. I am not totally sure about the proper voting scheme. Tim, Robert: Does SPI require something special or do we just decide upon a simple voting? Best Jan ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] Compile question...
Thanks for the quick reply!
Here's the relevant section of config.log:
configure:8134: checking for dn_expand in -lresolv
configure:8169: gcc -pipe -o conftest -g -O2 conftest.c -lresolv 5
/tmp/cczxthbQ.o: In function `main':
/src/audit/openvas-svn/openvas-libraries/conftest.c:30: undefined reference to
`dn_expand'
collect2: ld returned 1 exit status
configure:8175: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME
| #define PACKAGE_TARNAME
| #define PACKAGE_VERSION
| #define PACKAGE_STRING
| #define PACKAGE_BUGREPORT
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| /* end confdefs.h. */
|
| /* Override any GCC internal prototype to avoid an error.
|Use char because int might match the return type of a GCC
|builtin and then its argument prototype would still apply. */
| #ifdef __cplusplus
| extern C
| #endif
| char dn_expand ();
| int
| main ()
| {
| return dn_expand ();
| ;
| return 0;
| }
configure:8193: result: no
configure:8198: error: you need to install resolve library with development
files
--
Ed Vazquez
2008-02-20 11:05
A communist is like a crocodile: when it opens its mouth you
cannot tell whether it is trying to smile or preparing to eat
you up. - Sir Winston Leonard Spencer Churchill
-Original Message-
[snip]
The contents of config.log related to this test would help in figuring
out
what exactly failed (missing headers, missing libraries, or whatever).
Search for dn_expand in config.log The lines following the first
occurrence
until the next checking for should be the relevant part.
Regards,
Bernhard
smime.p7s
Description: S/MIME cryptographic signature
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] Compile question...
On Wednesday 20 February 2008 18:56, Vazquez, Ed wrote: When trying to compile the openvas-library code on Gentoo AMD64 (x86-64) _with_ the 32-bit compatibility libraries installed, I get the following error: checking for dn_expand in -lresolv... no configure: error: you need to install resolve library with development files make: *** [openvas-libraries.tmpl] Error 1 The contents of config.log related to this test would help in figuring out what exactly failed (missing headers, missing libraries, or whatever). Search for dn_expand in config.log The lines following the first occurrence until the next checking for should be the relevant part. Regards, Bernhard pgpliA9wXoeGg.pgp Description: PGP signature ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
