From jandradas at gmv.com Fri Aug 1 10:19:02 2008 From: jandradas at gmv.com (Jonas Andradas Arias) Date: Fri, 1 Aug 2008 10:19:02 +0200 Subject: [Openvas-discuss] idea: Contest 'Best advancesforOpenVASNetwork Vulnerability Tests' References: <455387.46753.qm@web59612.mail.ac4.yahoo.com><200807301112.11386.jan-oliver.wagner@intevation.de><37F4A378F4156446B5B25B616830B5A55BDA22@GMVMAIL2.gmv.es> <200807311650.15288.jan-oliver.wagner@intevation.de> Message-ID: <37F4A378F4156446B5B25B616830B5A55BDA45@GMVMAIL2.gmv.es> Hello Jan, -----Original Message----- >From: openvas-discuss-bounces at wald.intevation.org on behalf of Jan-Oliver Wagner >Sent: Thu 7/31/2008 4:50 PM >To: openvas-discuss at wald.intevation.org >Subject: Re: [Openvas-discuss] idea: Contest 'Best advancesforOpenVASNetwork Vulnerability Tests' > *snip* > >The OpenVAS team works on a OpenVAS Compendium where a NASL developer >guide should be part of. Currently you find openvas-compendium under >doc/ in SVN, but it will soon emerge as a package of its own. > >The NASL devel part is in the works and should see significant progress in August. > >Apart from this the nasl2_reference is of some help. > >The best help usually are the other NASL scripts which you could take >as examples. > >Best > > Jan > Thank you for the information. I'll have a look at other NASL scripts and the NASL2_reference PDF, and will be looking forward for the NASL Developer Guide (I might start reading it from the SVN). Regards, Jonas. ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080801/7bacb66a/attachment.htm From jan-oliver.wagner at intevation.de Fri Aug 1 11:09:43 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Fri, 1 Aug 2008 11:09:43 +0200 Subject: [Openvas-discuss] idea: Contest 'Best advances for OpenVAS Network Vulnerability Tests' In-Reply-To: <200806261551.11333.jan-oliver.wagner@intevation.de> References: <200806261551.11333.jan-oliver.wagner@intevation.de> Message-ID: <200808011109.47470.jan-oliver.wagner@intevation.de> On Donnerstag, 26. Juni 2008, Jan-Oliver Wagner wrote: > how about arranging a Contest 'Best advances for OpenVAS Network Vulnerability Tests' > in order to make OpenVAS more known, get people to look on how to implement > further NVTs or in other ways implement ideas to improve OpenVAS? > > What I am having in mind is something like this (just quickly drafted and > entirely open for suggestions how to change or extend or entirely > rewrite it): I'd like to not delay this contest any further as we received quite positive feedback. Surley it would be good to have support by SPI for managing it, but Intevation could take over responsibilities until things are clearified. Getting the contest to start is more important than to get the details straightened, IMHO. Please feel free to fix or improve the actual announcement of the contest (we have already two additional sponsorts :-) : """ Contest: Best advances for OpenVAS Network Vulnerability Tests The OpenVAS Team (Open Vulnerability Assessment System, [1]) calls for submission of patches, scripts, converters or anything else that significantly improves the OpenVAS framework for extended Open Source Network Vulnerability Testing. Basically your are free to choose the actual area of improvements, examples are: * New .nasl scripts for recent security alerts * NASL libraries for simplifying development of new test scripts * Converter routines that (semi-)automatically create NASL scripts from formal security alerts. * Performance improvements for the current tests. There are arbitrary other ways to extend/improve the OpenVAS test routines. The only hard requirement is that your solution is published as Free Software under GNU GPLv2+. Current winner prices are (the amount might increase because additional sponsors are welcome to add to the price as along as the contest is open): 1: 500 Euro 2: 300 Euro 3: 200 Euro The sponsors and OpenVAS steering team will jointly choose the winners inspired by these criteria: * number of CVEs/BIDs covered * relevance of the covered alerts * sustainable future benefit (e.g. in the case of supporting APIs) * how well the development was coordinated via the public OpenVAS mailing lists (teams may win as well) * code quality (documentation, design, style) Contest sponsors are (sorted by sponsored amount): * Intevation GmbH, www.intevation.net * DN-Systems GmbH, www.dn-systems.de * Tim Brown Time table: 2008-08-15: Contest started 2008-10-15: Contest closes 2007-10-30: Winners nominated How to participate: * express you wish to participate on the OpenVAS mailing list and what you plan to work on * summarize you contribution before contests closes and submit it on the OpenVAS mailing list [1] www.openvas.org """ -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From phornung at gmail.com Mon Aug 4 19:36:16 2008 From: phornung at gmail.com (Patrick Hornung) Date: Mon, 4 Aug 2008 13:36:16 -0400 Subject: [Openvas-discuss] OpenVAS Vmware appliance In-Reply-To: <200807301119.08856.jan-oliver.wagner@intevation.de> References: <9587e64c0807260837y796799e8ld09abd23fb3d1664@mail.gmail.com> <200807301119.08856.jan-oliver.wagner@intevation.de> Message-ID: <9587e64c0808041036i52a1ececq782d6d70f1637854@mail.gmail.com> On Wed, Jul 30, 2008 at 5:19 AM, Jan-Oliver Wagner < jan-oliver.wagner at intevation.de> wrote: > On Samstag, 26. Juli 2008, Patrick Hornung wrote: > > I'm new to the discussion list, and I'm interested in using OpenVAS to > > create an entirely GPL vmware appliance for security scanning (which of > > course I'll supply to the community). I'm planning on building a web > > interface to initiate the scans, and I'm wondering if there's a > command-line > > interface available for OpenVAS. I've been looking for a few days and > I've > > seen a project called reason a few years back that wwould do this, but > > nothing currently seems to be available. > > http://reason.sourceforge.netdoesn't exist. If someone still has a > > copy and it's still redistributable, > > can you email it to me? > > I am not 100% sure what you are looking for, but OpenVAS-Client offers > command line execution even without any GUI. I've since found that it's actually OpenVAS-Client, which was a bit unexpected. :-) I still have the problem related to the bug that was fixed recently with regards to the command line client not being able to work without X. Here's a link to the discussion: http://lists.wald.intevation.org/pipermail/openvas-discuss/2008-July/000635.html I'm not having much success with the compiling, so does anyone happen to have a compiled version of the version that includes that bug fix for fedora/i686? If not, that's okay - I'll keep toying with it. > > > Also, I created an OpenVAS server on a very bare install of fedora 9 in > > vmware, but my scans only seem to do port scans and it never makes it to > the > > vulnerability scan part. Is there something obvious that I'm missing? > > maybe you have configured openvasd with "nasl-no-signature-checks=no" > but not configured signatures and/or not configured the OpenVAS NVT feed? > > I was using everything as it came from the rpm available, but I'll certainly check this out. Thanks for the tips. My timeline for a release of the VM is early September, so I'll definitely keep you informed on how it's going. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080804/88bd1f10/attachment.htm From msh9 at washington.edu Thu Aug 7 00:50:53 2008 From: msh9 at washington.edu (Michael Stephen Hughes) Date: Wed, 06 Aug 2008 15:50:53 -0700 Subject: [Openvas-discuss] Trouble Compiling Library version 1.0.2 Message-ID: <489A2ACD.2060206@washington.edu> Hello, I am having trouble compiling the openvas-libraries package on red hat 4.6. The package auto configures succcessfully, but when I run make it dies on compiling network.o in the libopenvas directory. Specifically, network.c:255: error: 'nessus_connection' has no member named 'last_err', network.c:1531: error: 'nessus_connection' has no member named 'bufptr', and network.c:792: error: 'nessus_connection' has no member named 'tls_cred' all show up several times before make exits. From jan-oliver.wagner at intevation.de Thu Aug 7 14:13:39 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Thu, 7 Aug 2008 14:13:39 +0200 Subject: [Openvas-discuss] Trouble Compiling Library version 1.0.2 In-Reply-To: <489A2ACD.2060206@washington.edu> References: <489A2ACD.2060206@washington.edu> Message-ID: <200808071413.41956.jan-oliver.wagner@intevation.de> On Donnerstag, 7. August 2008, Michael Stephen Hughes wrote: > I am having trouble compiling the openvas-libraries package on red hat > 4.6. The package auto configures succcessfully, but when I run make it > dies on compiling network.o in the libopenvas directory. Specifically, > network.c:255: error: 'nessus_connection' has no member named 'last_err', this is odd because nessus_connection is defined in the very same file and does contain "last_err". Can you $ make distclean and configure again? Are there any problems reported during configuration such as missing gnutls-dev or so? Perhaps you can paste the output here. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From michael.hughes at gmx.com Thu Aug 7 18:20:31 2008 From: michael.hughes at gmx.com (Michael Stephen Hughes) Date: Thu, 07 Aug 2008 09:20:31 -0700 Subject: [Openvas-discuss] Trouble Compiling Library version 1.0.2 In-Reply-To: <200808071413.41956.jan-oliver.wagner@intevation.de> References: <489A2ACD.2060206@washington.edu> <200808071413.41956.jan-oliver.wagner@intevation.de> Message-ID: <489B20CF.3020200@gmx.com> Jan-Oliver Wagner wrote: > this is odd because nessus_connection is defined in the very same file > and does contain "last_err". > > Can you > $ make distclean > > and configure again? > Are there any problems reported during configuration such as missing > gnutls-dev or so? > The configuration exits with status 0, no problems. Going through the config.log I see a number errors reported, but nothing that stopped autoconfig from finishing. ex: conftest.c:8:28: error: ac_nonexistent.h: No such file or directory configure:9509: gcc -pipe -c -g -O2 conftest.c >&5 conftest.c:63:24: error: sys/sockio.h: No such file or directory configure:9548: gcc -E conftest.c conftest.c:30:24: error: sys/sockio.h: No such file or directory This appeared at the end of the configuration output to stdout config.status: WARNING: openvas-libraries.tmpl.in seems to ignore the --datarootdir setting From phornung at gmail.com Fri Aug 8 23:04:19 2008 From: phornung at gmail.com (Patrick Hornung) Date: Fri, 8 Aug 2008 17:04:19 -0400 Subject: [Openvas-discuss] OpenVAS Vmware appliance In-Reply-To: <9587e64c0808041036i52a1ececq782d6d70f1637854@mail.gmail.com> References: <9587e64c0807260837y796799e8ld09abd23fb3d1664@mail.gmail.com> <200807301119.08856.jan-oliver.wagner@intevation.de> <9587e64c0808041036i52a1ececq782d6d70f1637854@mail.gmail.com> Message-ID: <9587e64c0808081404y7247fe52t417b8049af670b3c@mail.gmail.com> > > > > >> >> > Also, I created an OpenVAS server on a very bare install of fedora 9 in >> > vmware, but my scans only seem to do port scans and it never makes it to >> the >> > vulnerability scan part. Is there something obvious that I'm missing? >> >> maybe you have configured openvasd with "nasl-no-signature-checks=no" >> but not configured signatures and/or not configured the OpenVAS NVT feed? >> >> > I was using everything as it came from the rpm available, but I'll > certainly check this out. > > Thanks for the tips. My timeline for a release of the VM is early > September, so I'll definitely keep you informed on how it's going. > > I have some more information on the problem I'm having, it seems that I'm getting SIGSEGV errors in my openvasd log. Here's an example of a scan of 4 hosts on my local network. I'm running the server with the following command: OpenVAS-Client -T html_graph localhost 1241 test test /root/file test3 I'm running the command line client from the server, the server runs the command on port 1241, my username and password are both 'test' while I troubleshoot, the file /root/file contains these hosts, and test3 is the directory I'm writing the results to. As a test, I've rebuilt everything on debian now using subversion this time for everything but the client, which I compiled from 1.0.4 using the --disable-gtk as referenced in a prior issue. Based on that, it seems I'm making the same mistake again... Is there anything else I can do to troubleshoot this? [Fri Aug 8 16:49:10 2008][2604] user test starts a new scan. Target(s) : 10.0.0.109,10.0.0.110,10.0.0.189,10.0.0.218, with max_hosts = 5 and max_checks = 4 [Fri Aug 8 16:49:10 2008][2604] user test : testing 10.0.0.109 (10.0.0.109) [2605] [Fri Aug 8 16:49:11 2008][2604] user test : testing 10.0.0.110 (10.0.0.110) [2606] [Fri Aug 8 16:49:11 2008][2604] user test : testing 10.0.0.189 (10.0.0.189) [2607] [Fri Aug 8 16:49:11 2008][2604] user test : testing 10.0.0.218 (10.0.0.218) [2608] [Fri Aug 8 16:49:11 2008][2527] connection from 10.0.0.109 [Fri Aug 8 16:49:17 2008][2527] connection from 10.0.0.109 [Fri Aug 8 16:49:17 2008][2605] SIGSEGV occured ! [Fri Aug 8 16:49:17 2008][2527] connection from 10.0.0.109 [Fri Aug 8 16:49:18 2008][2608] SIGSEGV occured ! [Fri Aug 8 16:49:18 2008][2606] SIGSEGV occured ! [Fri Aug 8 16:49:36 2008][2607] SIGSEGV occured ! [Fri Aug 8 16:49:36 2008][2604] user test : test complete [Fri Aug 8 16:49:36 2008][2604] SIGSEGV occured ! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080808/e1647fc2/attachment.html From boris.chernenko at yahoo.com Sun Aug 10 17:02:18 2008 From: boris.chernenko at yahoo.com (Boris Chernenko) Date: Sun, 10 Aug 2008 08:02:18 -0700 (PDT) Subject: [Openvas-discuss] idea: Contest 'Best advances for OpenVAS Network Vulnerability Tests' In-Reply-To: <200807282251.16082.jan-oliver.wagner@intevation.de> Message-ID: <771357.96310.qm@web59605.mail.ac4.yahoo.com> --- On Mon, 7/28/08, Jan-Oliver Wagner wrote: > > I wonder how you are going to rewrite the TCP & > SYN scanners... Just > > curious. > > thats easy: Pull those C-parts that are not implementable > in NASL into the > language/API of NASL. Well, we can write a scanner in NASL. It would not be so slow. > The existance of C plugins IMHO is a broken design. -------------- next part -------------- A non-text attachment was scrubbed... Name: tcpscan.nasl Type: application/octet-stream Size: 1871 bytes Desc: not available Url : http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080810/81472ea3/tcpscan.obj From phornung at gmail.com Fri Aug 15 17:50:41 2008 From: phornung at gmail.com (Patrick Hornung) Date: Fri, 15 Aug 2008 11:50:41 -0400 Subject: [Openvas-discuss] OpenVAS Vmware appliance In-Reply-To: <9587e64c0808081404y7247fe52t417b8049af670b3c@mail.gmail.com> References: <9587e64c0807260837y796799e8ld09abd23fb3d1664@mail.gmail.com> <200807301119.08856.jan-oliver.wagner@intevation.de> <9587e64c0808041036i52a1ececq782d6d70f1637854@mail.gmail.com> <9587e64c0808081404y7247fe52t417b8049af670b3c@mail.gmail.com> Message-ID: <9587e64c0808150850q7eeced4do7231dfe38c4f59c6@mail.gmail.com> I can't imagine everyone is having the SIGSEGV error, right? Are there tests I should be avoiding? I've rebuilt my entire test system again using Fedora 9 and the unofficial repository listed in the instructions. I can't seem to run a single test on a single host without a SIGSEGV appearing at the end of the openvas log. If it matters, running a test with no port scanner and no plugins completes without the error (although it's a rather useless test). On Fri, Aug 8, 2008 at 5:04 PM, Patrick Hornung wrote: > >> >> >>> >>> > Also, I created an OpenVAS server on a very bare install of fedora 9 in >>> > vmware, but my scans only seem to do port scans and it never makes it >>> to the >>> > vulnerability scan part. Is there something obvious that I'm missing? >>> >>> maybe you have configured openvasd with "nasl-no-signature-checks=no" >>> but not configured signatures and/or not configured the OpenVAS NVT feed? >>> >>> >> I was using everything as it came from the rpm available, but I'll >> certainly check this out. >> >> Thanks for the tips. My timeline for a release of the VM is early >> September, so I'll definitely keep you informed on how it's going. >> >> > I have some more information on the problem I'm having, it seems that I'm > getting SIGSEGV errors in my openvasd log. Here's an example of a scan of 4 > hosts on my local network. I'm running the server with the following > command: OpenVAS-Client -T html_graph localhost 1241 test test /root/file > test3 > I'm running the command line client from the server, the server runs the > command on port 1241, my username and password are both 'test' while I > troubleshoot, the file /root/file contains these hosts, and test3 is the > directory I'm writing the results to. > > As a test, I've rebuilt everything on debian now using subversion this time > for everything but the client, which I compiled from 1.0.4 using the > --disable-gtk as referenced in a prior issue. Based on that, it seems I'm > making the same mistake again... > > Is there anything else I can do to troubleshoot this? > > [Fri Aug 8 16:49:10 2008][2604] user test starts a new scan. Target(s) : > 10.0.0.109,10.0.0.110,10.0.0.189,10.0.0.218, with max_hosts = 5 and > max_checks = 4 > [Fri Aug 8 16:49:10 2008][2604] user test : testing 10.0.0.109 ( > 10.0.0.109) [2605] > [Fri Aug 8 16:49:11 2008][2604] user test : testing 10.0.0.110 ( > 10.0.0.110) [2606] > [Fri Aug 8 16:49:11 2008][2604] user test : testing 10.0.0.189 ( > 10.0.0.189) [2607] > [Fri Aug 8 16:49:11 2008][2604] user test : testing 10.0.0.218 ( > 10.0.0.218) [2608] > [Fri Aug 8 16:49:11 2008][2527] connection from 10.0.0.109 > [Fri Aug 8 16:49:17 2008][2527] connection from 10.0.0.109 > [Fri Aug 8 16:49:17 2008][2605] SIGSEGV occured ! > [Fri Aug 8 16:49:17 2008][2527] connection from 10.0.0.109 > [Fri Aug 8 16:49:18 2008][2608] SIGSEGV occured ! > [Fri Aug 8 16:49:18 2008][2606] SIGSEGV occured ! > [Fri Aug 8 16:49:36 2008][2607] SIGSEGV occured ! > [Fri Aug 8 16:49:36 2008][2604] user test : test complete > [Fri Aug 8 16:49:36 2008][2604] SIGSEGV occured ! > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080815/c1ceb009/attachment.html From timb at nth-dimension.org.uk Fri Aug 15 18:07:20 2008 From: timb at nth-dimension.org.uk (Tim Brown) Date: Fri, 15 Aug 2008 17:07:20 +0100 Subject: [Openvas-discuss] OpenVAS Vmware appliance In-Reply-To: <9587e64c0808150850q7eeced4do7231dfe38c4f59c6@mail.gmail.com> References: <9587e64c0807260837y796799e8ld09abd23fb3d1664@mail.gmail.com> <9587e64c0808081404y7247fe52t417b8049af670b3c@mail.gmail.com> <9587e64c0808150850q7eeced4do7231dfe38c4f59c6@mail.gmail.com> Message-ID: <200808151707.20734.timb@nth-dimension.org.uk> On Friday 15 August 2008 16:50:41 Patrick Hornung wrote: > I can't imagine everyone is having the SIGSEGV error, right? Are there > tests I should be avoiding? > > I've rebuilt my entire test system again using Fedora 9 and the unofficial > repository listed in the instructions. I can't seem to run a single test > on a single host without a SIGSEGV appearing at the end of the openvas log. > If it matters, running a test with no port scanner and no plugins > completes without the error (although it's a rather useless test). Noone has yet sent me the debug out I was after. Without that it's not trivial to identify the route cause. Cheers, Tim -- Tim Brown From phornung at gmail.com Fri Aug 15 18:58:04 2008 From: phornung at gmail.com (Patrick Hornung) Date: Fri, 15 Aug 2008 12:58:04 -0400 Subject: [Openvas-discuss] OpenVAS Vmware appliance In-Reply-To: <200808151707.20734.timb@nth-dimension.org.uk> References: <9587e64c0807260837y796799e8ld09abd23fb3d1664@mail.gmail.com> <9587e64c0808081404y7247fe52t417b8049af670b3c@mail.gmail.com> <9587e64c0808150850q7eeced4do7231dfe38c4f59c6@mail.gmail.com> <200808151707.20734.timb@nth-dimension.org.uk> Message-ID: <9587e64c0808150958k2f8616b4ya71d907688369429@mail.gmail.com> That's certainly fair. I'll try to get that for you, but I'll need some instruction or time to research how to do this. Alternatively, I can make available my vmware appliance with that base installation set running. I did stumble upon some news that might help things. I was frustrated and I wiped out my entire /usr/lib/openvas/plugins directory and ran openvas-nvt-sync to make sure only the exact feed contents were being run, and the tests ran through without the error. Also, I received much less trouble from starting openvasd because dependencies were all met. Perhaps there are outdated or incomplete plugins in the plugins rpm? On the downside, I'm missing port scanners and a huge number of checks, which makes sense because the feed seems to contain the Debian local security checks only (according to http://www.openvas.org/openvas-nvt-feed.html). Sorry if I sound needy - I really want to understand the project and its inner workings, and I'd really like to help it grow in any way I can. On Fri, Aug 15, 2008 at 12:07 PM, Tim Brown wrote: > On Friday 15 August 2008 16:50:41 Patrick Hornung wrote: > > I can't imagine everyone is having the SIGSEGV error, right? Are there > > tests I should be avoiding? > > > > I've rebuilt my entire test system again using Fedora 9 and the > unofficial > > repository listed in the instructions. I can't seem to run a single test > > on a single host without a SIGSEGV appearing at the end of the openvas > log. > > If it matters, running a test with no port scanner and no plugins > > completes without the error (although it's a rather useless test). > > Noone has yet sent me the debug out I was after. Without that it's not > trivial to identify the route cause. > > Cheers, > Tim > -- > Tim Brown > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080815/bf4109e2/attachment.htm From barry.smoke at arklegaudit.gov Fri Aug 15 20:30:43 2008 From: barry.smoke at arklegaudit.gov (Barry Smoke) Date: Fri, 15 Aug 2008 13:30:43 -0500 Subject: [Openvas-discuss] ubuntu openvasd ? Message-ID: <1CA8273BEDC6F44BBB19F22139C53BB0019C78A2@postoffice.audit.local> I upgraded my production ubuntu 8.04 box to alpha 5 of 8.10(I know, why would you do that...) well, we are highly dependent on nessus.... when I saw this http://packages.ubuntu.com/intrepid/openvas-client I assumed that openvasd was in the packages included. that apparently is not the case. Is it easy to add a debian apt source, so I can apt-get just openvasd, or does someone have openvasd compiled for ubuntu 8.10(so I can just install it)? why would ubuntu choose only the openvas client to include(when nessus server is listed as a program that needs removal) Just wondering...kinda in panic mode because of the licensing change of the feeds at nessus.org(like everyone else I'm sure) Thanks, Barry Smoke Network Administrator AR Division of Legislative Audit -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080815/ca226fc9/attachment-0001.html From barry.smoke at arklegaudit.gov Fri Aug 15 20:34:37 2008 From: barry.smoke at arklegaudit.gov (Barry Smoke) Date: Fri, 15 Aug 2008 13:34:37 -0500 Subject: [Openvas-discuss] existing nessus plugins/cutoff from free download Message-ID: <1CA8273BEDC6F44BBB19F22139C53BB0019C78A3@postoffice.audit.local> I know nessus 3 was not released under gpl... did the plugins licensing change at that point also...? I'm wondering if the plugins that were downloaded as of 07/31/08 are gpl plugins? Can I take my current plugins, and move them over to openvas, or are all the gpl ones already included? Thanks, Barry Smoke Network Administrator AR Division of Legislative Audit -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080815/4c0fda0f/attachment.htm From phornung at gmail.com Fri Aug 15 21:20:15 2008 From: phornung at gmail.com (Patrick Hornung) Date: Fri, 15 Aug 2008 15:20:15 -0400 Subject: [Openvas-discuss] ubuntu openvasd ? In-Reply-To: <1CA8273BEDC6F44BBB19F22139C53BB0019C78A2@postoffice.audit.local> References: <1CA8273BEDC6F44BBB19F22139C53BB0019C78A2@postoffice.audit.local> Message-ID: <9587e64c0808151220s30b6da89i832f302b7f4dbe8a@mail.gmail.com> The OpenVAS server component isn't integrated into Debian yet. http://www.openvas.org/openvas-server.html On Fri, Aug 15, 2008 at 2:30 PM, Barry Smoke wrote: > I upgraded my production ubuntu 8.04 box to alpha 5 of 8.10(I know, why > would you do that?) > > well, we are highly dependent on nessus?. > > when I saw this http://packages.ubuntu.com/intrepid/openvas-client > > I assumed that openvasd was in the packages included. that apparently is > not the case. > > > > Is it easy to add a debian apt source, so I can apt-get just openvasd, > > or does someone have openvasd compiled for ubuntu 8.10(so I can just > install it)? > > > > why would ubuntu choose only the openvas client to include(when nessus > server is listed as a program that needs removal) > > > > Just wondering?kinda in panic mode because of the licensing change of the > feeds at nessus.org(like everyone else I'm sure) > > > > Thanks, > > Barry Smoke > > Network Administrator > > AR Division of Legislative Audit > > > > > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080815/3aeaef4f/attachment.html From jandradas at gmv.com Sat Aug 16 13:06:31 2008 From: jandradas at gmv.com (Jonas Andradas Arias) Date: Sat, 16 Aug 2008 13:06:31 +0200 Subject: [Openvas-discuss] existing nessus plugins/cutoff from free download References: <1CA8273BEDC6F44BBB19F22139C53BB0019C78A3@postoffice.audit.local> Message-ID: <37F4A378F4156446B5B25B616830B5A55BDACC@GMVMAIL2.gmv.es> Hello Barry, -----Original Message----- >From: openvas-discuss-bounces at wald.intevation.org on behalf of Barry Smoke >Sent: Fri 8/15/2008 8:34 PM >To: openvas-discuss at wald.intevation.org >Subject: [Openvas-discuss] existing nessus plugins/cutoff from free download > >I know nessus 3 was not released under gpl... > >did the plugins licensing change at that point also...? > As far as I know, Nessus Plugins stopped being GPL since version 2.2. Only a handful of them (the ones included in the nessus-plugins debian package, and I suppose those are the ones included in OpenVAS) were GPL. The new licensing change at Nessus is that, for personal use, one can still receive their plugin feed for free (with some delay respect to the paying customers), but that is no longer the case for commercial purposes, for which a license costs $1200 annually (for each Nessus installation). > > >I'm wondering if the plugins that were downloaded as of 07/31/08 are gpl >plugins? > Maybe some of them are, but most of them I am mostly sure that are not GPL. > >Can I take my current plugins, and move them over to openvas, or are all >the gpl ones already included? With the current license, I think you can *NOT* move them over to OpenVAS, but probably you could rewrite them for OpenVAS, but that is somewhat tricky... Where is the thin line that separates when you are just making a plugin that does the same as a Nessus one does, and when are you "making a derivate work" of their plugin (and thus, might not be allowed to do that based on their license). Maybe someone else could bring some more light on this, as I am no expert. Best Regards, Jon?s Andradas. ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080816/2d542726/attachment.htm From michael.wiegand at intevation.de Mon Aug 18 09:12:52 2008 From: michael.wiegand at intevation.de (Michael Wiegand) Date: Mon, 18 Aug 2008 09:12:52 +0200 Subject: [Openvas-discuss] OpenVAS Vmware appliance In-Reply-To: <9587e64c0808150958k2f8616b4ya71d907688369429@mail.gmail.com> References: <9587e64c0807260837y796799e8ld09abd23fb3d1664@mail.gmail.com> <200808151707.20734.timb@nth-dimension.org.uk> <9587e64c0808150958k2f8616b4ya71d907688369429@mail.gmail.com> Message-ID: <200808180912.52339.michael.wiegand@intevation.de> Am Freitag, 15. August 2008 18:58:04 schrieb Patrick Hornung: > That's certainly fair. I'll try to get that for you, but I'll need some > instruction or time to research how to do this. Just let us now if you need help with that. You might want to join #openvas on irc.oftc.net if you get stuck; or just ask your question on this list. > openvas-nvt-sync to make sure only the exact feed contents were being run, > and the tests ran through without the error. Also, I received much less > trouble from starting openvasd because dependencies were all met. Perhaps > there are outdated or incomplete plugins in the plugins rpm? On the > downside, I'm missing port scanners and a huge number of checks, which > makes sense because the feed seems to contain the Debian local security > checks only (according to http://www.openvas.org/openvas-nvt-feed.html). Thank you for your correct observation. :) A number of plugins had to be removed from the plugin package since they were part of Nessus and not available under the GPL. This is very regrettable as it breaks quite a few other plugins (that's one reason for the "xyz.nasl not found" errors), but can't be helped at the moment. The NVT feed on the other hand is a first batch of plugins that only depend on available plugins but - as you said - they only offer a very limited number of checks. > Sorry if I sound needy - I really want to understand the project and its > inner workings, and I'd really like to help it grow in any way I can. Thank you, we certainly appreciate your support! Is there any question you have right now (well, apart from the SIGSEGV issue :) ) or any area you would like to concentrate on? As you have seen, NVT development is one area that could certainly use improvement and will be a focus of development in the next months. Regards, Michael -- Michael Wiegand OpenPGP key: D7D049EC Intevation GmbH, Osnabr?ck http://www.intevation.de/ Amtsgericht Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From saulov8 at gmail.com Mon Aug 18 16:34:50 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Mon, 18 Aug 2008 11:34:50 -0300 Subject: [Openvas-discuss] Openvas-server scripts Message-ID: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> Hi, I just installed the openvas-server on Debian Etch from deb * http://apt.intevation.de/ etch openvas *repository*. *Those packages are installed: libopenvas1 libopenvas1-dev But the openvas-client can't comunicate with openvas-server, so i looked for docs and found the OpenVAS Compendium. In this doc, on page 17, there the steps to configurate the openvas-server. It says: communication between server and client is only possible through SSL encrypted connections. To do this i have to use the openvas-mkcert script provided by the openvas-server package, and to create new users i have to use the openvas-adduser provided by the same package. So, where those scripts on Debian Etch? Thank a lot for any help. -- Saulo Medeiros de Ara?jo 61 2191-9821 / 61 9119-9893 saulo.araujo at mda.gov.br / saulov8 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080818/06bcf4f9/attachment.html From phornung at gmail.com Mon Aug 18 17:27:01 2008 From: phornung at gmail.com (Patrick Hornung) Date: Mon, 18 Aug 2008 11:27:01 -0400 Subject: [Openvas-discuss] Openvas-server scripts In-Reply-To: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> References: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> Message-ID: <9587e64c0808180827w5829de08q3ff5fb45b6b85cfe@mail.gmail.com> Hi, The only packages available for Etch are the library component, which you have installed. You'll need to install the libnasl, server, and plugins component before everything will work. -Patrick On Mon, Aug 18, 2008 at 10:34 AM, Saulo Medeiros de Ara?jo < saulov8 at gmail.com> wrote: > Hi, > > I just installed the openvas-server on Debian Etch from deb * > http://apt.intevation.de/ etch openvas *repository*. *Those packages are > installed: > > libopenvas1 > libopenvas1-dev > > But the openvas-client can't comunicate with openvas-server, so i looked > for docs and found the OpenVAS Compendium. In this doc, on page 17, there > the steps to configurate the openvas-server. It says: communication between > server and client is only possible through SSL encrypted connections. To do > this i have to use the openvas-mkcert script provided by the openvas-server > package, and to create new users i have to use the openvas-adduser provided > by the same package. > > So, where those scripts on Debian Etch? > > Thank a lot for any help. > > -- > Saulo Medeiros de Ara?jo > 61 2191-9821 / 61 9119-9893 > saulo.araujo at mda.gov.br / saulov8 at gmail.com > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080818/cde4e074/attachment.htm From saulov8 at gmail.com Mon Aug 18 19:02:09 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Mon, 18 Aug 2008 14:02:09 -0300 Subject: [Openvas-discuss] Openvas-server scripts In-Reply-To: <9587e64c0808180827w5829de08q3ff5fb45b6b85cfe@mail.gmail.com> References: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> <9587e64c0808180827w5829de08q3ff5fb45b6b85cfe@mail.gmail.com> Message-ID: <515c3e9d0808181002l6d3c3f13na50be2db49902158@mail.gmail.com> In first time, thanks Jonas and Patrick!! I've sucesfully installed: openvas-libnasl-1.0.1 openvas-libraries-1.0.2 openvas-plugins-1.0.2 openvas-server-1.0.1 Now i got this error when i run openvas: * # openvasd openvasd: error while loading shared libraries: libopenvasnasl.so.1: cannot open shared object file: No such file or directory* I've looked for the libopenvasnasl.so.1 library and it was found in: */usr/local/lib/libopenvasnasl.so.1* So, whats wrong? On Mon, Aug 18, 2008 at 12:27 PM, Patrick Hornung wrote: > Hi, > > The only packages available for Etch are the library component, which you > have installed. You'll need to install the libnasl, server, and plugins > component before everything will work. > > -Patrick > > On Mon, Aug 18, 2008 at 10:34 AM, Saulo Medeiros de Ara?jo < > saulov8 at gmail.com> wrote: > >> Hi, >> >> I just installed the openvas-server on Debian Etch from deb * >> http://apt.intevation.de/ etch openvas *repository*. *Those packages are >> installed: >> >> libopenvas1 >> libopenvas1-dev >> >> But the openvas-client can't comunicate with openvas-server, so i looked >> for docs and found the OpenVAS Compendium. In this doc, on page 17, there >> the steps to configurate the openvas-server. It says: communication between >> server and client is only possible through SSL encrypted connections. To do >> this i have to use the openvas-mkcert script provided by the openvas-server >> package, and to create new users i have to use the openvas-adduser provided >> by the same package. >> >> So, where those scripts on Debian Etch? >> >> Thank a lot for any help. >> >> -- >> Saulo Medeiros de Ara?jo >> 61 2191-9821 / 61 9119-9893 >> saulo.araujo at mda.gov.br / saulov8 at gmail.com >> >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss at wald.intevation.org >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -- Saulo Medeiros de Ara?jo 61 2191-9821 / 61 9119-9893 saulo.araujo at mda.gov.br / saulov8 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080818/10c73541/attachment.html From phornung at gmail.com Mon Aug 18 19:39:47 2008 From: phornung at gmail.com (Patrick Hornung) Date: Mon, 18 Aug 2008 13:39:47 -0400 Subject: [Openvas-discuss] Openvas-server scripts In-Reply-To: <515c3e9d0808181002l6d3c3f13na50be2db49902158@mail.gmail.com> References: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> <9587e64c0808180827w5829de08q3ff5fb45b6b85cfe@mail.gmail.com> <515c3e9d0808181002l6d3c3f13na50be2db49902158@mail.gmail.com> Message-ID: <9587e64c0808181039j73d0b116ga33535597b2b2063@mail.gmail.com> I had something similar to this. Make sure /usr/local/lib is in your path! I vaguely remember another command I had to use to associate development files with the development environment, and I had to run that too. Not sure if it was for exactly the same issue, but it was certainly for a 'cannot find file' type issue. On Mon, Aug 18, 2008 at 1:02 PM, Saulo Medeiros de Ara?jo wrote: > In first time, thanks Jonas and Patrick!! > > I've sucesfully installed: > > openvas-libnasl-1.0.1 > openvas-libraries-1.0.2 > openvas-plugins-1.0.2 > openvas-server-1.0.1 > > Now i got this error when i run openvas: > * > # openvasd > > openvasd: error while loading shared libraries: libopenvasnasl.so.1: cannot > open shared object file: No such file or directory* > > I've looked for the libopenvasnasl.so.1 library and it was found in: > > */usr/local/lib/libopenvasnasl.so.1* > > So, whats wrong? > > On Mon, Aug 18, 2008 at 12:27 PM, Patrick Hornung wrote: > >> Hi, >> >> The only packages available for Etch are the library component, which you >> have installed. You'll need to install the libnasl, server, and plugins >> component before everything will work. >> >> -Patrick >> >> On Mon, Aug 18, 2008 at 10:34 AM, Saulo Medeiros de Ara?jo < >> saulov8 at gmail.com> wrote: >> >>> Hi, >>> >>> I just installed the openvas-server on Debian Etch from deb * >>> http://apt.intevation.de/ etch openvas *repository*. *Those packages are >>> installed: >>> >>> libopenvas1 >>> libopenvas1-dev >>> >>> But the openvas-client can't comunicate with openvas-server, so i looked >>> for docs and found the OpenVAS Compendium. In this doc, on page 17, there >>> the steps to configurate the openvas-server. It says: communication between >>> server and client is only possible through SSL encrypted connections. To do >>> this i have to use the openvas-mkcert script provided by the openvas-server >>> package, and to create new users i have to use the openvas-adduser provided >>> by the same package. >>> >>> So, where those scripts on Debian Etch? >>> >>> Thank a lot for any help. >>> >>> -- >>> Saulo Medeiros de Ara?jo >>> 61 2191-9821 / 61 9119-9893 >>> saulo.araujo at mda.gov.br / saulov8 at gmail.com >>> >>> _______________________________________________ >>> Openvas-discuss mailing list >>> Openvas-discuss at wald.intevation.org >>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>> >>> >> >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss at wald.intevation.org >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> > > > -- > Saulo Medeiros de Ara?jo > 61 2191-9821 / 61 9119-9893 > saulo.araujo at mda.gov.br / saulov8 at gmail.com > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080818/dd86448a/attachment.htm From saulov8 at gmail.com Mon Aug 18 22:41:15 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Mon, 18 Aug 2008 17:41:15 -0300 Subject: [Openvas-discuss] Openvas-server scripts In-Reply-To: <9587e64c0808181039j73d0b116ga33535597b2b2063@mail.gmail.com> References: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> <9587e64c0808180827w5829de08q3ff5fb45b6b85cfe@mail.gmail.com> <515c3e9d0808181002l6d3c3f13na50be2db49902158@mail.gmail.com> <9587e64c0808181039j73d0b116ga33535597b2b2063@mail.gmail.com> Message-ID: <515c3e9d0808181341raac7ffescc255268a14d6db1@mail.gmail.com> Patrick, Sorry about this newbe's question...but how can I make sure /usr/local/lib is in my path?? On Mon, Aug 18, 2008 at 2:39 PM, Patrick Hornung wrote: > I had something similar to this. Make sure /usr/local/lib is in your path! > > I vaguely remember another command I had to use to associate development > files with the development environment, and I had to run that too. Not sure > if it was for exactly the same issue, but it was certainly for a 'cannot > find file' type issue. > > > On Mon, Aug 18, 2008 at 1:02 PM, Saulo Medeiros de Ara?jo < > saulov8 at gmail.com> wrote: > >> In first time, thanks Jonas and Patrick!! >> >> I've sucesfully installed: >> >> openvas-libnasl-1.0.1 >> openvas-libraries-1.0.2 >> openvas-plugins-1.0.2 >> openvas-server-1.0.1 >> >> Now i got this error when i run openvas: >> * >> # openvasd >> >> openvasd: error while loading shared libraries: libopenvasnasl.so.1: >> cannot open shared object file: No such file or directory* >> >> I've looked for the libopenvasnasl.so.1 library and it was found in: >> >> */usr/local/lib/libopenvasnasl.so.1* >> >> So, whats wrong? >> >> On Mon, Aug 18, 2008 at 12:27 PM, Patrick Hornung wrote: >> >>> Hi, >>> >>> The only packages available for Etch are the library component, which you >>> have installed. You'll need to install the libnasl, server, and plugins >>> component before everything will work. >>> >>> -Patrick >>> >>> On Mon, Aug 18, 2008 at 10:34 AM, Saulo Medeiros de Ara?jo < >>> saulov8 at gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I just installed the openvas-server on Debian Etch from deb * >>>> http://apt.intevation.de/ etch openvas *repository*. *Those packages >>>> are installed: >>>> >>>> libopenvas1 >>>> libopenvas1-dev >>>> >>>> But the openvas-client can't comunicate with openvas-server, so i looked >>>> for docs and found the OpenVAS Compendium. In this doc, on page 17, there >>>> the steps to configurate the openvas-server. It says: communication between >>>> server and client is only possible through SSL encrypted connections. To do >>>> this i have to use the openvas-mkcert script provided by the openvas-server >>>> package, and to create new users i have to use the openvas-adduser provided >>>> by the same package. >>>> >>>> So, where those scripts on Debian Etch? >>>> >>>> Thank a lot for any help. >>>> >>>> >>>> _______________________________________________ >>>> Openvas-discuss mailing list >>>> Openvas-discuss at wald.intevation.org >>>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>>> >>>> >>> >>> _______________________________________________ >>> Openvas-discuss mailing list >>> Openvas-discuss at wald.intevation.org >>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>> >>> >> >> >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss at wald.intevation.org >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080818/bfa11edd/attachment.html From phornung at gmail.com Mon Aug 18 22:46:47 2008 From: phornung at gmail.com (Patrick Hornung) Date: Mon, 18 Aug 2008 16:46:47 -0400 Subject: [Openvas-discuss] Openvas-server scripts In-Reply-To: <515c3e9d0808181341raac7ffescc255268a14d6db1@mail.gmail.com> References: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> <9587e64c0808180827w5829de08q3ff5fb45b6b85cfe@mail.gmail.com> <515c3e9d0808181002l6d3c3f13na50be2db49902158@mail.gmail.com> <9587e64c0808181039j73d0b116ga33535597b2b2063@mail.gmail.com> <515c3e9d0808181341raac7ffescc255268a14d6db1@mail.gmail.com> Message-ID: <9587e64c0808181346x5523a1d3t2452f29dd3d054c9@mail.gmail.com> From jandradas at gmv.com Mon Aug 18 16:49:05 2008 From: jandradas at gmv.com (Jonas Andradas Arias) Date: Mon, 18 Aug 2008 16:49:05 +0200 Subject: [Openvas-discuss] Openvas-server scripts References: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> Message-ID: <37F4A378F4156446B5B25B616830B5A55BDAD3@GMVMAIL2.gmv.es> Hello Saulo, please find my response between your lines: -----Original Message----- >From: openvas-discuss-bounces at wald.intevation.org on behalf of Saulo Medeiros de Ara?jo >Sent: Mon 8/18/2008 4:34 PM >To: openvas-discuss at wald.intevation.org >Subject: [Openvas-discuss] Openvas-server scripts > >Hi, > >I just installed the openvas-server on Debian Etch from deb * >http://apt.intevation.de/ etch openvas *repository*. *Those packages are >installed: > >libopenvas1 >libopenvas1-dev > >But the openvas-client can't comunicate with openvas-server, so i looked for >docs and found the OpenVAS Compendium. In this doc, on page 17, there the >steps to configurate the openvas-server. It says: communication between >server and client is only possible through SSL encrypted connections. To do >this i have to use the openvas-mkcert script provided by the openvas-server >package, and to create new users i have to use the openvas-adduser provided >by the same package. > >So, where those scripts on Debian Etch? > I think you are missing the "openvas-server" package, which, as far as I know, is not yet provided as a Debian Package. You have to download the sources and compile it yourself. If I am not mistaken, those scripts can be found on the source package of openvas-server. > >Thank a lot for any help. > >-- >Saulo Medeiros de Ara?jo >61 2191-9821 / 61 9119-9893 >saulo.araujo at mda.gov.br / saulov8 at gmail.com Best Regards, Jon?s Andradas. ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080818/a25afd5d/attachment.htm From jan-oliver.wagner at intevation.de Tue Aug 19 14:08:46 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Tue, 19 Aug 2008 14:08:46 +0200 Subject: [Openvas-discuss] ubuntu openvasd ? In-Reply-To: <9587e64c0808151220s30b6da89i832f302b7f4dbe8a@mail.gmail.com> References: <1CA8273BEDC6F44BBB19F22139C53BB0019C78A2@postoffice.audit.local> <9587e64c0808151220s30b6da89i832f302b7f4dbe8a@mail.gmail.com> Message-ID: <200808191408.50575.jan-oliver.wagner@intevation.de> On Freitag, 15. August 2008, Patrick Hornung wrote: > The OpenVAS server component isn't integrated into Debian yet. > > http://www.openvas.org/openvas-server.html to be precise, half way is done (openvas-libraries and openvas-libnasl is there, openvas-server and openvas-plugins is missing). The mailing list "openvas-distro" is the place where the progress is discussed. Also, help is appreciated by the Ubuntu users and developers to integrate and test OpenVAS there. Progress for Debian is currently slow. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From jan-oliver.wagner at intevation.de Tue Aug 19 14:23:48 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Tue, 19 Aug 2008 14:23:48 +0200 Subject: [Openvas-discuss] existing nessus plugins/cutoff from free download In-Reply-To: <37F4A378F4156446B5B25B616830B5A55BDACC@GMVMAIL2.gmv.es> References: <1CA8273BEDC6F44BBB19F22139C53BB0019C78A3@postoffice.audit.local> <37F4A378F4156446B5B25B616830B5A55BDACC@GMVMAIL2.gmv.es> Message-ID: <200808191423.50248.jan-oliver.wagner@intevation.de> On Samstag, 16. August 2008, Jonas Andradas Arias wrote: > >From: openvas-discuss-bounces at wald.intevation.org on behalf of Barry Smoke > >I know nessus 3 was not released under gpl... > > > >did the plugins licensing change at that point also...? > > As far as I know, Nessus Plugins stopped being GPL since version 2.2. There still remained a set of GPLed plugins in the Nessus distributions and the feed for a while. I guess there are still some in there. > Only a handful of them (the ones included in the nessus-plugins debian package, and I suppose those are the ones included in OpenVAS) were GPL. OpenVAS tries its best to have all NASL routines that were ever released under GPL in the plugins modul. Also any new plugins should be GPL or GPL compatible. > >Can I take my current plugins, and move them over to openvas, or are all > >the gpl ones already included? > > With the current license, I think you can *NOT* move them over to OpenVAS, but probably you could rewrite them for OpenVAS, but that is somewhat tricky... Where is the thin line that separates when you are just making a plugin that does the same as a Nessus one does, and when are you "making a derivate work" of their plugin (and thus, might not be allowed to do that based on their license). Indeed I think you are _not_ permitted by Tenable to use them with OpenVAS. In fact, for quite a long time, the plugins license required to use a Nessus retrieved from nessus.org which made use of these plugins with any GNU/Linux distibution binary packages illegal anyway. For trivial plugins I do not expect troublemaking by Tenable. If there is only one way to implement it, there is only one way to implement it. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From hl at omhe.org Tue Aug 19 14:41:48 2008 From: hl at omhe.org (Hector Lopez - OMHE) Date: Tue, 19 Aug 2008 07:41:48 -0500 Subject: [Openvas-discuss] Having a problem compiling openvas-libraries on a Clarkconnect server. Message-ID: <0E73B1E0-175B-4019-B8D1-47EFFBD02C3E@omhe.org> Hello guys, i'm new on the list, my name is H?ctor. I have a problem compiling the openvas-libraries on a Clarkconnect distribution. I get the sources via subversion and then i install the gnutls-devel via apt. I pass the ./configure stage but then when i tried to compile i get this output: [root at server openvas-libraries]# make cd libopenvas && make make[1]: Entering directory `/opt/openvas/openvas-libraries/libopenvas' /bin/sh /opt/openvas/openvas-libraries/libtool gcc -pipe -I../ - DHAVE_CONFIG_H -I. -I/opt/openvas/openvas-libraries/include -I/usr/ local/include -g -Wall -c network.c rm -f .libs/network.lo gcc -pipe -I../ -DHAVE_CONFIG_H -I. -I/opt/openvas/openvas-libraries/ include -I/usr/local/include -g -Wall -c network.c -fPIC -DPIC - o .libs/network.lo network.c:72: error: syntax error before "gnutls_session_t" network.c:72: warning: no semicolon at end of struct or union network.c:73: warning: type defaults to `int' in declaration of `tls_cred' network.c:73: warning: data definition has no type or storage class network.c:80: error: syntax error before '}' token network.c:80: warning: type defaults to `int' in declaration of `nessus_connection' network.c:80: warning: data definition has no type or storage class network.c:91: error: syntax error before "connections" network.c:91: warning: type defaults to `int' in declaration of `connections' network.c:91: warning: data definition has no type or storage class network.c: In function `stream_get_err': network.c:148: error: `p' undeclared (first use in this function) network.c:148: error: (Each undeclared identifier is reported only once network.c:148: error: for each function it appears in.) network.c: In function `get_connection_fd': network.c:171: error: request for member `transport' in something not a structure or union network.c:174: error: request for member `pid' in something not a structure or union network.c: In function `release_connection_fd': network.c:190: error: `p' undeclared (first use in this function) network.c: In function `ovas_allocate_connection': network.c:246: error: `p' undeclared (first use in this function) network.c: In function `nessus_deregister_connection': network.c:278: error: `p' undeclared (first use in this function) network.c: In function `nessus_get_socket_from_connection': network.c:408: error: `fp' undeclared (first use in this function) network.c: At top level: network.c:427: error: syntax error before "session" network.c: In function `set_gnutls_priorities': network.c:436: error: `session' undeclared (first use in this function) network.c:436: error: `protocol_priority' undeclared (first use in this function) network.c:437: error: `cipher_priority' undeclared (first use in this function) network.c:438: error: `comp_priority' undeclared (first use in this function) network.c:439: error: `kx_priority' undeclared (first use in this function) network.c:440: error: `mac_priority' undeclared (first use in this function) network.c: At top level: network.c:449: error: syntax error before "session" network.c: In function `set_gnutls_sslv23': network.c:466: error: `GNUTLS_MAC_SHA1' undeclared (first use in this function) network.c:466: error: initializer element is not constant network.c:466: error: (near initialization for `mac_priority[0]') network.c:470: error: `session' undeclared (first use in this function) network.c: At top level: network.c:475: error: syntax error before "session" network.c: In function `set_gnutls_sslv3': network.c:491: error: `GNUTLS_MAC_SHA1' undeclared (first use in this function) network.c:491: error: initializer element is not constant network.c:491: error: (near initialization for `mac_priority[0]') network.c:495: error: `session' undeclared (first use in this function) network.c: At top level: network.c:500: error: syntax error before "session" network.c: In function `set_gnutls_tlsv1': network.c:516: error: `GNUTLS_MAC_SHA1' undeclared (first use in this function) network.c:516: error: initializer element is not constant network.c:516: error: (near initialization for `mac_priority[0]') network.c:520: error: `session' undeclared (first use in this function) network.c: At top level: network.c:529: error: syntax error before "session" network.c: In function `set_gnutls_protocol': network.c:531: error: `encaps' undeclared (first use in this function) network.c:534: error: `session' undeclared (first use in this function) network.c: At top level: network.c:563: error: syntax error before "session" network.c: In function `verify_peer_certificate': network.c:571: error: `GNUTLS_CERT_INSECURE_ALGORITHM' undeclared (first use in this function) network.c:571: error: initializer element is not constant network.c:571: error: (near initialization for `messages[4].flag') network.c:572: error: initializer element is not constant network.c:572: error: (near initialization for `messages[4]') network.c:573: error: initializer element is not constant network.c:573: error: (near initialization for `messages[5]') network.c:579: error: `session' undeclared (first use in this function) network.c: At top level: network.c:647: error: syntax error before "xcred" network.c: In function `load_cert_and_key': network.c:650: error: `gnutls_x509_crt_t' undeclared (first use in this function) network.c:650: error: syntax error before "x509_crt" network.c:651: error: `gnutls_x509_privkey_t' undeclared (first use in this function) network.c:656: error: `cert' undeclared (first use in this function) network.c:665: error: `x509_crt' undeclared (first use in this function) network.c:685: error: `key' undeclared (first use in this function) network.c:694: error: `x509_key' undeclared (first use in this function) network.c:704: error: `passwd' undeclared (first use in this function) network.c:728: error: `xcred' undeclared (first use in this function) network.c: At top level: network.c:748: error: syntax error before '*' token network.c: In function `open_SSL_connection': network.c:759: error: `fp' undeclared (first use in this function) network.c:790: error: `cert' undeclared (first use in this function) network.c:790: error: `key' undeclared (first use in this function) network.c:792: error: `passwd' undeclared (first use in this function) network.c:796: error: `cafile' undeclared (first use in this function) network.c:811: error: `gnutls_transport_ptr_t' undeclared (first use in this function) network.c:811: error: syntax error before "fp" network.c:840: error: `timeout' undeclared (first use in this function) network.c: In function `set_ids_evasion_mode': network.c:871: error: syntax error before "nessus_connection" network.c:904: error: invalid type argument of `->' network.c:906: error: invalid type argument of `->' network.c: In function `open_stream_connection': network.c:915: error: `fp' undeclared (first use in this function) network.c: At top level: network.c:1095: error: syntax error before "gnutls_certificate_credentials_t" network.c:1095: warning: no semicolon at end of struct or union network.c: In function `ovas_server_context_new': network.c:1125: error: invalid application of `sizeof' to incomplete type `ovas_server_context_s' network.c:1129: error: dereferencing pointer to incomplete type network.c:1130: error: dereferencing pointer to incomplete type network.c:1132: error: dereferencing pointer to incomplete type network.c:1134: error: dereferencing pointer to incomplete type network.c:1138: error: dereferencing pointer to incomplete type network.c:1144: error: dereferencing pointer to incomplete type network.c:1150: error: dereferencing pointer to incomplete type network.c: In function `ovas_server_context_free': network.c:1179: error: dereferencing pointer to incomplete type network.c:1180: error: dereferencing pointer to incomplete type network.c: In function `ovas_server_context_attach': network.c:1206: error: `fp' undeclared (first use in this function) network.c:1209: error: dereferencing pointer to incomplete type network.c:1230: error: dereferencing pointer to incomplete type network.c:1237: error: dereferencing pointer to incomplete type network.c:1248: error: dereferencing pointer to incomplete type network.c:1253: error: `gnutls_transport_ptr_t' undeclared (first use in this function) network.c:1253: error: syntax error before "fp" network.c: In function `stream_set_timeout': network.c:1295: error: `fp' undeclared (first use in this function) network.c: In function `stream_set_options': network.c:1311: error: `fp' undeclared (first use in this function) network.c: In function `read_stream_connection_unbuffered': network.c:1333: error: `fp' undeclared (first use in this function) network.c: In function `read_stream_connection_min': network.c:1518: error: `fp' undeclared (first use in this function) network.c: In function `write_stream_connection4': network.c:1591: error: `fp' undeclared (first use in this function) network.c: In function `nsend': network.c:1742: error: request for member `fd' in something not a structure or union network.c: In function `nrecv': network.c:1797: error: request for member `fd' in something not a structure or union network.c: In function `get_encaps': network.c:1854: error: request for member `transport' in something not a structure or union network.c: In function `stream_get_buffer_sz': network.c:2475: error: `p' undeclared (first use in this function) network.c: In function `stream_set_buffer': network.c:2487: error: `p' undeclared (first use in this function) network.c: In function `stream_pending': network.c:2665: error: `fp' undeclared (first use in this function) make[1]: *** [network.o] Error 1 make[1]: Leaving directory `/opt/openvas/openvas-libraries/libopenvas' make: *** [all] Error 2 Thanks a lot for your time. H?ctor L?pez - Fundador OMHE www.omhe.org (477) 1583003 From saulov8 at gmail.com Tue Aug 19 14:52:04 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Tue, 19 Aug 2008 09:52:04 -0300 Subject: [Openvas-discuss] Openvas-server scripts In-Reply-To: <9587e64c0808181346x5523a1d3t2452f29dd3d054c9@mail.gmail.com> References: <515c3e9d0808180734q7238df75q15eea554e60ae78b@mail.gmail.com> <9587e64c0808180827w5829de08q3ff5fb45b6b85cfe@mail.gmail.com> <515c3e9d0808181002l6d3c3f13na50be2db49902158@mail.gmail.com> <9587e64c0808181039j73d0b116ga33535597b2b2063@mail.gmail.com> <515c3e9d0808181341raac7ffescc255268a14d6db1@mail.gmail.com> <9587e64c0808181346x5523a1d3t2452f29dd3d054c9@mail.gmail.com> Message-ID: <515c3e9d0808190552hd9cddf3u597280d502ff3b18@mail.gmail.com> To resolve this problem i had to set this path: *# export LD_LIBRARY_PATH=/usr/local/lib* And everything is running just fine. On Mon, Aug 18, 2008 at 5:46 PM, Patrick Hornung wrote: > From the shell, you'll want to run this command. What it does is appends > /usr/local/lib to the end of your path. There's a way to add it permanently > to your profile, but I don't know it off the top of my head. > > PATH=$PATH:/usr/local/lib > > > > On Mon, Aug 18, 2008 at 4:41 PM, Saulo Medeiros de Ara?jo < > saulov8 at gmail.com> wrote: > >> Patrick, >> >> Sorry about this newbe's question...but how can I make sure /usr/local/lib >> is in my path?? >> >> >> >> On Mon, Aug 18, 2008 at 2:39 PM, Patrick Hornung wrote: >> >>> I had something similar to this. Make sure /usr/local/lib is in your >>> path! >>> >>> I vaguely remember another command I had to use to associate development >>> files with the development environment, and I had to run that too. Not sure >>> if it was for exactly the same issue, but it was certainly for a 'cannot >>> find file' type issue. >>> >>> >>> On Mon, Aug 18, 2008 at 1:02 PM, Saulo Medeiros de Ara?jo < >>> saulov8 at gmail.com> wrote: >>> >>>> In first time, thanks Jonas and Patrick!! >>>> >>>> I've sucesfully installed: >>>> >>>> openvas-libnasl-1.0.1 >>>> openvas-libraries-1.0.2 >>>> openvas-plugins-1.0.2 >>>> openvas-server-1.0.1 >>>> >>>> Now i got this error when i run openvas: >>>> * >>>> # openvasd >>>> >>>> openvasd: error while loading shared libraries: libopenvasnasl.so.1: >>>> cannot open shared object file: No such file or directory* >>>> >>>> I've looked for the libopenvasnasl.so.1 library and it was found in: >>>> >>>> */usr/local/lib/libopenvasnasl.so.1* >>>> >>>> So, whats wrong? >>>> >>>> >>>> On Mon, Aug 18, 2008 at 12:27 PM, Patrick Hornung wrote: >>>> >>>>> Hi, >>>>> >>>>> The only packages available for Etch are the library component, which >>>>> you have installed. You'll need to install the libnasl, server, and plugins >>>>> component before everything will work. >>>>> >>>>> -Patrick >>>>> >>>>> On Mon, Aug 18, 2008 at 10:34 AM, Saulo Medeiros de Ara?jo < >>>>> saulov8 at gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I just installed the openvas-server on Debian Etch from deb * >>>>>> http://apt.intevation.de/ etch openvas *repository*. *Those packages >>>>>> are installed: >>>>>> >>>>>> libopenvas1 >>>>>> libopenvas1-dev >>>>>> >>>>>> But the openvas-client can't comunicate with openvas-server, so i >>>>>> looked for docs and found the OpenVAS Compendium. In this doc, on page 17, >>>>>> there the steps to configurate the openvas-server. It says: communication >>>>>> between server and client is only possible through SSL encrypted >>>>>> connections. To do this i have to use the openvas-mkcert script provided by >>>>>> the openvas-server package, and to create new users i have to use the >>>>>> openvas-adduser provided by the same package. >>>>>> >>>>>> So, where those scripts on Debian Etch? >>>>>> >>>>>> Thank a lot for any help. >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Openvas-discuss mailing list >>>>>> Openvas-discuss at wald.intevation.org >>>>>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Openvas-discuss mailing list >>>>> Openvas-discuss at wald.intevation.org >>>>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>>>> >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Openvas-discuss mailing list >>>> Openvas-discuss at wald.intevation.org >>>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>>> >>>> >>> >>> _______________________________________________ >>> Openvas-discuss mailing list >>> Openvas-discuss at wald.intevation.org >>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>> >>> >> >> >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss at wald.intevation.org >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -- Saulo Medeiros de Ara?jo 61 2191-9821 / 61 9119-9893 saulo.araujo at mda.gov.br / saulov8 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/385fb8b4/attachment-0001.html From saulov8 at gmail.com Tue Aug 19 15:44:30 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Tue, 19 Aug 2008 10:44:30 -0300 Subject: [Openvas-discuss] openvas-adduser Message-ID: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> Im having a problem to access the openvas-client with the users created with openvas-adduser. * oink:~# openvas-adduser Using /var/tmp as a temporary file holder. Add a new openvasd user --------------------------------- Login : teste3 Authentication (pass/cert) [pass] : Login password : Login password (again) : User rules --------------- openvasd has a rules system which allows you to restrict the hosts that teste3 has the right to test. For instance, you may want him to be able to scan his own host only. Please see the openvas-adduser(8) man page for the rules syntax. Enter the rules for this user, and hit ctrl-D once you are done: (the user can have an empty rules set) default accept Login : teste3 Password : *********** Rules : default accept Is that ok? (y/n) [y] y user added.* In the openvas-client i got this error message when i use the user teste3: *Error: Login failed* Any help?? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/43da8756/attachment.htm From augusto.ferronato at gmail.com Tue Aug 19 15:52:00 2008 From: augusto.ferronato at gmail.com (Augusto Ferronato) Date: Tue, 19 Aug 2008 10:52:00 -0300 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> Message-ID: <50761acd0808190652r501dc0abyb7fee2ed90a9f1af@mail.gmail.com> you need set the rules #man openvas-adduser RULES Each user has his own set of rules. Rules are here to restrict the rights of the users. For instance, you can add user ?joe? that he can only test the host ?192.168.1.1?bob? Each rule fits on one line. A user can have an unlimited amount of rules (and can even have no rule at all). The syntax is: accept|deny ip/mask and default accept|deny Where mask is the CIDR netmask of the rule. The default statement must be the last rule and defines the policy of the user. The following rule set will allow the user to test 192.168.1.0/24, 192.168.3.0/24 and 172.22.0.0/16, but nothing else: accept 192.168.1.0/24 accept 192.168.3.0/24 accept 172.22.0.0/16 default deny The following rule set will allow the user to test whatever he wants, except the network 192.168.1.0/24: deny 192.168.1.0/24 default accept The keyword client_ip has been defined, and is replaced at run time by the IP address of the openvasd user. For instance, if you want your users to be able to only be able to scan the system they come from, then you want them to have the following ruleset: accept client_ip default deny Best Regards, On Tue, Aug 19, 2008 at 10:44 AM, Saulo Medeiros de Ara?jo < saulov8 at gmail.com> wrote: > Im having a problem to access the openvas-client with the users created > with openvas-adduser. > * > oink:~# openvas-adduser > Using /var/tmp as a temporary file holder. > > Add a new openvasd user > --------------------------------- > > > Login : teste3 > Authentication (pass/cert) [pass] : > Login password : > Login password (again) : > > User rules > --------------- > openvasd has a rules system which allows you to restrict the hosts that > teste3 has the right to test. > For instance, you may want him to be able to scan his own host only. > > Please see the openvas-adduser(8) man page for the rules syntax. > > Enter the rules for this user, and hit ctrl-D once you are done: > (the user can have an empty rules set) > default accept > > > Login : teste3 > Password : *********** > > Rules : > default accept > > > Is that ok? (y/n) [y] y > user added.* > > In the openvas-client i got this error message when i use the user teste3: > > *Error: Login failed* > > Any help?? > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -- ------------------------------ "Seguran?a da Informa??o se faz com tecnologia, processos e pessoas, e a forma??o destas exige mais que uma seq??ncia de treinamentos. Porque voc? treina macacos. Pessoas,voc? educa." FreeBSD: The Freedom to Perform! http://www.spreadbsd.org/aff/40/1 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/bc19f61e/attachment.html From saulov8 at gmail.com Tue Aug 19 15:58:52 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Tue, 19 Aug 2008 10:58:52 -0300 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <50761acd0808190652r501dc0abyb7fee2ed90a9f1af@mail.gmail.com> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> <50761acd0808190652r501dc0abyb7fee2ed90a9f1af@mail.gmail.com> Message-ID: <515c3e9d0808190658t220a6e75p7ee1df1e57c0bdc8@mail.gmail.com> I've set those rules: ?Enter the rules for this user, and hit ctrl-D once you are done: (the user can have an empty rules set) accept client_ip accept 10.0.0.0/16 default deny But im still getting the error message... On Tue, Aug 19, 2008 at 10:52 AM, Augusto Ferronato < augusto.ferronato at gmail.com> wrote: > you need set the rules > > #man openvas-adduser > > RULES > Each user has his own set of rules. Rules are here to restrict > the rights of the users. For instance, you can add user ?joe? > that he can only test the host ?192.168.1.1?bob? > > Each rule fits on one line. A user can have an unlimited amount of > rules (and can even have no rule at all). > > The syntax is: > accept|deny ip/mask > and > default accept|deny > > Where mask is the CIDR netmask of the rule. > > The default statement must be the last rule and defines the policy > of the user. > > The following rule set will allow the user to test 192.168.1.0/24, > 192.168.3.0/24 and 172.22.0.0/16, but nothing else: > accept 192.168.1.0/24 > accept 192.168.3.0/24 > accept 172.22.0.0/16 > default deny > > The following rule set will allow the user to test whatever he > wants, except the network 192.168.1.0/24: > deny 192.168.1.0/24 > default accept > > The keyword client_ip has been defined, and is replaced at run time > by the IP address of the openvasd user. For instance, if you > want your users to be able to only be able to scan the system they > come from, then you want them to have the following ruleset: > accept client_ip > default deny > > Best Regards, > > On Tue, Aug 19, 2008 at 10:44 AM, Saulo Medeiros de Ara?jo < > saulov8 at gmail.com> wrote: > >> Im having a problem to access the openvas-client with the users created >> with openvas-adduser. >> * >> oink:~# openvas-adduser >> Using /var/tmp as a temporary file holder. >> >> Add a new openvasd user >> --------------------------------- >> >> >> Login : teste3 >> Authentication (pass/cert) [pass] : >> Login password : >> Login password (again) : >> >> User rules >> --------------- >> openvasd has a rules system which allows you to restrict the hosts that >> teste3 has the right to test. >> For instance, you may want him to be able to scan his own host only. >> >> Please see the openvas-adduser(8) man page for the rules syntax. >> >> Enter the rules for this user, and hit ctrl-D once you are done: >> (the user can have an empty rules set) >> default accept >> >> >> Login : teste3 >> Password : *********** >> >> Rules : >> default accept >> >> >> Is that ok? (y/n) [y] y >> user added.* >> >> In the openvas-client i got this error message when i use the user teste3: >> >> *Error: Login failed* >> >> Any help?? >> >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss at wald.intevation.org >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> > > > -- > ------------------------------ > "Seguran?a da Informa??o se faz com tecnologia, processos e pessoas, e a > forma??o destas exige mais que uma seq??ncia de treinamentos. Porque voc? > treina macacos. Pessoas,voc? educa." > > FreeBSD: The Freedom to Perform! > http://www.spreadbsd.org/aff/40/1 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/15226f02/attachment-0001.htm From phornung at gmail.com Tue Aug 19 16:05:13 2008 From: phornung at gmail.com (Patrick Hornung) Date: Tue, 19 Aug 2008 10:05:13 -0400 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <515c3e9d0808190658t220a6e75p7ee1df1e57c0bdc8@mail.gmail.com> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> <50761acd0808190652r501dc0abyb7fee2ed90a9f1af@mail.gmail.com> <515c3e9d0808190658t220a6e75p7ee1df1e57c0bdc8@mail.gmail.com> Message-ID: <9587e64c0808190705h6fcaac5dgd3c702b74d55263d@mail.gmail.com> Can't speak for anyone else, but I've had success by not specifying any rules. Based on the error, my suspicion is more likely a login problem than a rules-based problem. Does it work if you try it with a blank ruleset? On Tue, Aug 19, 2008 at 9:58 AM, Saulo Medeiros de Ara?jo wrote: > I've set those rules: > > ?Enter the rules for this user, and hit ctrl-D once you are done: > (the user can have an empty rules set) > accept client_ip > accept 10.0.0.0/16 > default deny > > But im still getting the error message... > > > > On Tue, Aug 19, 2008 at 10:52 AM, Augusto Ferronato < > augusto.ferronato at gmail.com> wrote: > >> you need set the rules >> >> #man openvas-adduser >> >> RULES >> Each user has his own set of rules. Rules are here to restrict >> the rights of the users. For instance, you can add user ?joe? >> that he can only test the host ?192.168.1.1?bob? >> >> Each rule fits on one line. A user can have an unlimited amount of >> rules (and can even have no rule at all). >> >> The syntax is: >> accept|deny ip/mask >> and >> default accept|deny >> >> Where mask is the CIDR netmask of the rule. >> >> The default statement must be the last rule and defines the policy >> of the user. >> >> The following rule set will allow the user to test 192.168.1.0/24, >> 192.168.3.0/24 and 172.22.0.0/16, but nothing else: >> accept 192.168.1.0/24 >> accept 192.168.3.0/24 >> accept 172.22.0.0/16 >> default deny >> >> The following rule set will allow the user to test whatever he >> wants, except the network 192.168.1.0/24: >> deny 192.168.1.0/24 >> default accept >> >> The keyword client_ip has been defined, and is replaced at run time >> by the IP address of the openvasd user. For instance, if you >> want your users to be able to only be able to scan the system they >> come from, then you want them to have the following ruleset: >> accept client_ip >> default deny >> >> Best Regards, >> >> On Tue, Aug 19, 2008 at 10:44 AM, Saulo Medeiros de Ara?jo < >> saulov8 at gmail.com> wrote: >> >>> Im having a problem to access the openvas-client with the users created >>> with openvas-adduser. >>> * >>> oink:~# openvas-adduser >>> Using /var/tmp as a temporary file holder. >>> >>> Add a new openvasd user >>> --------------------------------- >>> >>> >>> Login : teste3 >>> Authentication (pass/cert) [pass] : >>> Login password : >>> Login password (again) : >>> >>> User rules >>> --------------- >>> openvasd has a rules system which allows you to restrict the hosts that >>> teste3 has the right to test. >>> For instance, you may want him to be able to scan his own host only. >>> >>> Please see the openvas-adduser(8) man page for the rules syntax. >>> >>> Enter the rules for this user, and hit ctrl-D once you are done: >>> (the user can have an empty rules set) >>> default accept >>> >>> >>> Login : teste3 >>> Password : *********** >>> >>> Rules : >>> default accept >>> >>> >>> Is that ok? (y/n) [y] y >>> user added.* >>> >>> In the openvas-client i got this error message when i use the user >>> teste3: >>> >>> *Error: Login failed* >>> >>> Any help?? >>> >>> _______________________________________________ >>> Openvas-discuss mailing list >>> Openvas-discuss at wald.intevation.org >>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>> >>> >> >> >> -- >> ------------------------------ >> "Seguran?a da Informa??o se faz com tecnologia, processos e pessoas, e a >> forma??o destas exige mais que uma seq??ncia de treinamentos. Porque voc? >> treina macacos. Pessoas,voc? educa." >> >> FreeBSD: The Freedom to Perform! >> http://www.spreadbsd.org/aff/40/1 >> > > > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/31b3fb63/attachment.html From saulov8 at gmail.com Tue Aug 19 16:09:56 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Tue, 19 Aug 2008 11:09:56 -0300 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <9587e64c0808190705h6fcaac5dgd3c702b74d55263d@mail.gmail.com> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> <50761acd0808190652r501dc0abyb7fee2ed90a9f1af@mail.gmail.com> <515c3e9d0808190658t220a6e75p7ee1df1e57c0bdc8@mail.gmail.com> <9587e64c0808190705h6fcaac5dgd3c702b74d55263d@mail.gmail.com> Message-ID: <515c3e9d0808190709g39e83249l6b3b11cc7247255f@mail.gmail.com> I got the same error message with a blank ruleset. I agree with you. I think this issue is not a rules problem. Anyway, im still looking for a solution. On Tue, Aug 19, 2008 at 11:05 AM, Patrick Hornung wrote: > Can't speak for anyone else, but I've had success by not specifying any > rules. Based on the error, my suspicion is more likely a login problem than > a rules-based problem. Does it work if you try it with a blank ruleset? > > > On Tue, Aug 19, 2008 at 9:58 AM, Saulo Medeiros de Ara?jo < > saulov8 at gmail.com> wrote: > >> I've set those rules: >> >> ?Enter the rules for this user, and hit ctrl-D once you are done: >> (the user can have an empty rules set) >> accept client_ip >> accept 10.0.0.0/16 >> default deny >> >> But im still getting the error message... >> >> >> >> On Tue, Aug 19, 2008 at 10:52 AM, Augusto Ferronato < >> augusto.ferronato at gmail.com> wrote: >> >>> you need set the rules >>> >>> #man openvas-adduser >>> >>> RULES >>> Each user has his own set of rules. Rules are here to restrict >>> the rights of the users. For instance, you can add user ?joe? >>> that he can only test the host ?192.168.1.1?bob? >>> >>> Each rule fits on one line. A user can have an unlimited amount of >>> rules (and can even have no rule at all). >>> >>> The syntax is: >>> accept|deny ip/mask >>> and >>> default accept|deny >>> >>> Where mask is the CIDR netmask of the rule. >>> >>> The default statement must be the last rule and defines the policy >>> of the user. >>> >>> The following rule set will allow the user to test 192.168.1.0/24, >>> 192.168.3.0/24 and 172.22.0.0/16, but nothing else: >>> accept 192.168.1.0/24 >>> accept 192.168.3.0/24 >>> accept 172.22.0.0/16 >>> default deny >>> >>> The following rule set will allow the user to test whatever he >>> wants, except the network 192.168.1.0/24: >>> deny 192.168.1.0/24 >>> default accept >>> >>> The keyword client_ip has been defined, and is replaced at run >>> time by the IP address of the openvasd user. For instance, if you >>> want your users to be able to only be able to scan the system they >>> come from, then you want them to have the following ruleset: >>> accept client_ip >>> default deny >>> >>> Best Regards, >>> >>> On Tue, Aug 19, 2008 at 10:44 AM, Saulo Medeiros de Ara?jo < >>> saulov8 at gmail.com> wrote: >>> >>>> Im having a problem to access the openvas-client with the users created >>>> with openvas-adduser. >>>> * >>>> oink:~# openvas-adduser >>>> Using /var/tmp as a temporary file holder. >>>> >>>> Add a new openvasd user >>>> --------------------------------- >>>> >>>> >>>> Login : teste3 >>>> Authentication (pass/cert) [pass] : >>>> Login password : >>>> Login password (again) : >>>> >>>> User rules >>>> --------------- >>>> openvasd has a rules system which allows you to restrict the hosts that >>>> teste3 has the right to test. >>>> For instance, you may want him to be able to scan his own host only. >>>> >>>> Please see the openvas-adduser(8) man page for the rules syntax. >>>> >>>> Enter the rules for this user, and hit ctrl-D once you are done: >>>> (the user can have an empty rules set) >>>> default accept >>>> >>>> >>>> Login : teste3 >>>> Password : *********** >>>> >>>> Rules : >>>> default accept >>>> >>>> >>>> Is that ok? (y/n) [y] y >>>> user added.* >>>> >>>> In the openvas-client i got this error message when i use the user >>>> teste3: >>>> >>>> *Error: Login failed* >>>> >>>> Any help?? >>>> >>>> _______________________________________________ >>>> Openvas-discuss mailing list >>>> Openvas-discuss at wald.intevation.org >>>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>>> >>>> >>> >>> >>> -- >>> ------------------------------ >>> "Seguran?a da Informa??o se faz com tecnologia, processos e pessoas, e a >>> forma??o destas exige mais que uma seq??ncia de treinamentos. Porque voc? >>> treina macacos. Pessoas,voc? educa." >>> >>> FreeBSD: The Freedom to Perform! >>> http://www.spreadbsd.org/aff/40/1 >>> >> >> >> >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss at wald.intevation.org >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/4a8b9050/attachment-0001.htm From phornung at gmail.com Tue Aug 19 16:15:28 2008 From: phornung at gmail.com (Patrick Hornung) Date: Tue, 19 Aug 2008 10:15:28 -0400 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <515c3e9d0808190709g39e83249l6b3b11cc7247255f@mail.gmail.com> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> <50761acd0808190652r501dc0abyb7fee2ed90a9f1af@mail.gmail.com> <515c3e9d0808190658t220a6e75p7ee1df1e57c0bdc8@mail.gmail.com> <9587e64c0808190705h6fcaac5dgd3c702b74d55263d@mail.gmail.com> <515c3e9d0808190709g39e83249l6b3b11cc7247255f@mail.gmail.com> Message-ID: <9587e64c0808190715l1e3cd747s3859ad8f99984345@mail.gmail.com> Another thing I'd try is selecting the first option below the password section, which I believe is using a certificate to connect even though you chose password-based authentication. (I don't have a client available to see right now, sorry). I found using a certificate allowed me to connect with the GUI. Besides that, I've always been able to connect with the command-line OpenVAS-Client command without using a certificate. The work I do with openvas is usually from the command line, so I have slightly different experience with the GUI, but that's what worked for me. On Tue, Aug 19, 2008 at 10:09 AM, Saulo Medeiros de Ara?jo < saulov8 at gmail.com> wrote: > I got the same error message with a blank ruleset. > > I agree with you. I think this issue is not a rules problem. > > Anyway, im still looking for a solution. > > > On Tue, Aug 19, 2008 at 11:05 AM, Patrick Hornung wrote: > >> Can't speak for anyone else, but I've had success by not specifying any >> rules. Based on the error, my suspicion is more likely a login problem than >> a rules-based problem. Does it work if you try it with a blank ruleset? >> >> >> On Tue, Aug 19, 2008 at 9:58 AM, Saulo Medeiros de Ara?jo < >> saulov8 at gmail.com> wrote: >> >>> I've set those rules: >>> >>> ?Enter the rules for this user, and hit ctrl-D once you are done: >>> (the user can have an empty rules set) >>> accept client_ip >>> accept 10.0.0.0/16 >>> default deny >>> >>> But im still getting the error message... >>> >>> >>> >>> On Tue, Aug 19, 2008 at 10:52 AM, Augusto Ferronato < >>> augusto.ferronato at gmail.com> wrote: >>> >>>> you need set the rules >>>> >>>> #man openvas-adduser >>>> >>>> RULES >>>> Each user has his own set of rules. Rules are here to >>>> restrict the rights of the users. For instance, you can add user ?joe? >>>> that he can only test the host ?192.168.1.1?bob? >>>> >>>> Each rule fits on one line. A user can have an unlimited amount >>>> of rules (and can even have no rule at all). >>>> >>>> The syntax is: >>>> accept|deny ip/mask >>>> and >>>> default accept|deny >>>> >>>> Where mask is the CIDR netmask of the rule. >>>> >>>> The default statement must be the last rule and defines the >>>> policy of the user. >>>> >>>> The following rule set will allow the user to test >>>> 192.168.1.0/24, 192.168.3.0/24 and 172.22.0.0/16, but nothing else: >>>> accept 192.168.1.0/24 >>>> accept 192.168.3.0/24 >>>> accept 172.22.0.0/16 >>>> default deny >>>> >>>> The following rule set will allow the user to test whatever he >>>> wants, except the network 192.168.1.0/24: >>>> deny 192.168.1.0/24 >>>> default accept >>>> >>>> The keyword client_ip has been defined, and is replaced at run >>>> time by the IP address of the openvasd user. For instance, if you >>>> want your users to be able to only be able to scan the system >>>> they come from, then you want them to have the following ruleset: >>>> accept client_ip >>>> default deny >>>> >>>> Best Regards, >>>> >>>> On Tue, Aug 19, 2008 at 10:44 AM, Saulo Medeiros de Ara?jo < >>>> saulov8 at gmail.com> wrote: >>>> >>>>> Im having a problem to access the openvas-client with the users created >>>>> with openvas-adduser. >>>>> * >>>>> oink:~# openvas-adduser >>>>> Using /var/tmp as a temporary file holder. >>>>> >>>>> Add a new openvasd user >>>>> --------------------------------- >>>>> >>>>> >>>>> Login : teste3 >>>>> Authentication (pass/cert) [pass] : >>>>> Login password : >>>>> Login password (again) : >>>>> >>>>> User rules >>>>> --------------- >>>>> openvasd has a rules system which allows you to restrict the hosts that >>>>> teste3 has the right to test. >>>>> For instance, you may want him to be able to scan his own host only. >>>>> >>>>> Please see the openvas-adduser(8) man page for the rules syntax. >>>>> >>>>> Enter the rules for this user, and hit ctrl-D once you are done: >>>>> (the user can have an empty rules set) >>>>> default accept >>>>> >>>>> >>>>> Login : teste3 >>>>> Password : *********** >>>>> >>>>> Rules : >>>>> default accept >>>>> >>>>> >>>>> Is that ok? (y/n) [y] y >>>>> user added.* >>>>> >>>>> In the openvas-client i got this error message when i use the user >>>>> teste3: >>>>> >>>>> *Error: Login failed* >>>>> >>>>> Any help?? >>>>> >>>>> _______________________________________________ >>>>> Openvas-discuss mailing list >>>>> Openvas-discuss at wald.intevation.org >>>>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>>>> >>>>> >>>> >>>> >>>> -- >>>> ------------------------------ >>>> "Seguran?a da Informa??o se faz com tecnologia, processos e pessoas, e a >>>> forma??o destas exige mais que uma seq??ncia de treinamentos. Porque voc? >>>> treina macacos. Pessoas,voc? educa." >>>> >>>> FreeBSD: The Freedom to Perform! >>>> http://www.spreadbsd.org/aff/40/1 >>>> >>> >>> >>> >>> _______________________________________________ >>> Openvas-discuss mailing list >>> Openvas-discuss at wald.intevation.org >>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>> >>> >> >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss at wald.intevation.org >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> > > > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/ef3d1522/attachment.html From barry.smoke at arklegaudit.gov Tue Aug 19 16:54:52 2008 From: barry.smoke at arklegaudit.gov (Barry Smoke) Date: Tue, 19 Aug 2008 09:54:52 -0500 Subject: [Openvas-discuss] error rebuilding openvas-server for fedora core 10 Message-ID: <1CA8273BEDC6F44BBB19F22139C53BB0019C78B1@postoffice.audit.local> I know fedora core 10 is alpha(strange that installing core9, then running an update got us fedora core10)... anyway, I was doing an rpmbuild -rebuild on all the fedora source rpm's, and I get this error when recompiling the server rpm: gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables `sh ./cflags` -c save_kb.c save_kb.c: In function 'save_kb_load_kb': save_kb.c:652: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables `sh ./cflags` -c detached.c detached.c: In function 'detached_new_session': detached.c:422: warning: ignoring return value of 'write', declared with attribute warn_unused_result detached.c: In function 'detached_send_sessions': detached.c:475: warning: ignoring return value of 'read', declared with attribute warn_unused_result In function 'open', inlined from 'detached_new_session' at detached.c:419: /usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT in second argument needs 3 arguments make[1]: *** [detached.o] Error 1 make[1]: Leaving directory `/root/rpmbuild/BUILD/openvas-server-1.0.0/openvasd' make: *** [server] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.fCjuPC (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.fCjuPC (%build) Just FYI, we are going to download fc8, and try the binaries... Barry Smoke Network Administrator AR Division of Legislative Audit -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/2b9c92b9/attachment-0001.htm From saulov8 at gmail.com Tue Aug 19 19:12:50 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Tue, 19 Aug 2008 14:12:50 -0300 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <9587e64c0808190715l1e3cd747s3859ad8f99984345@mail.gmail.com> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> <50761acd0808190652r501dc0abyb7fee2ed90a9f1af@mail.gmail.com> <515c3e9d0808190658t220a6e75p7ee1df1e57c0bdc8@mail.gmail.com> <9587e64c0808190705h6fcaac5dgd3c702b74d55263d@mail.gmail.com> <515c3e9d0808190709g39e83249l6b3b11cc7247255f@mail.gmail.com> <9587e64c0808190715l1e3cd747s3859ad8f99984345@mail.gmail.com> Message-ID: <515c3e9d0808191012p36d8fbc0g7ae688876a8d350e@mail.gmail.com> I?ve found something weird: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ oink:~# openvas-adduser Using /var/tmp as a temporary file holder. Add a new openvasd user --------------------------------- Login : teste8 Authentication (pass/cert) [pass] : Login password : Login password (again) : User rules --------------- openvasd has a rules system which allows you to restrict the hosts that teste8 has the right to test. For instance, you may want him to be able to scan his own host only. Please see the openvas-adduser(8) man page for the rules syntax. Enter the rules for this user, and hit ctrl-D once you are done: (the user can have an empty rules set) Login : teste8 Password : *********** Rules : Is that ok? (y/n) [y] y *user added.* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ oink:~# openvas-rmuser Login to remove : teste8 *user does not exist* oink:~# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ oink:~# openvas-adduser Using /var/tmp as a temporary file holder. Add a new openvasd user --------------------------------- Login : teste8 *This login already exists. Choose another one.* Login : oink:~# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Whats wrong??? On Tue, Aug 19, 2008 at 11:15 AM, Patrick Hornung wrote: > Another thing I'd try is selecting the first option below the password > section, which I believe is using a certificate to connect even though you > chose password-based authentication. (I don't have a client available to > see right now, sorry). I found using a certificate allowed me to connect > with the GUI. Besides that, I've always been able to connect with the > command-line OpenVAS-Client command without using a certificate. The work I > do with openvas is usually from the command line, so I have slightly > different experience with the GUI, but that's what worked for me. > > > On Tue, Aug 19, 2008 at 10:09 AM, Saulo Medeiros de Ara?jo < > saulov8 at gmail.com> wrote: > >> I got the same error message with a blank ruleset. >> >> I agree with you. I think this issue is not a rules problem. >> >> Anyway, im still looking for a solution. >> >> >> On Tue, Aug 19, 2008 at 11:05 AM, Patrick Hornung wrote: >> >>> Can't speak for anyone else, but I've had success by not specifying any >>> rules. Based on the error, my suspicion is more likely a login problem than >>> a rules-based problem. Does it work if you try it with a blank ruleset? >>> >>> >>> On Tue, Aug 19, 2008 at 9:58 AM, Saulo Medeiros de Ara?jo < >>> saulov8 at gmail.com> wrote: >>> >>>> I've set those rules: >>>> >>>> ?Enter the rules for this user, and hit ctrl-D once you are done: >>>> (the user can have an empty rules set) >>>> accept client_ip >>>> accept 10.0.0.0/16 >>>> default deny >>>> >>>> But im still getting the error message... >>>> >>>> >>>> >>>> On Tue, Aug 19, 2008 at 10:52 AM, Augusto Ferronato < >>>> augusto.ferronato at gmail.com> wrote: >>>> >>>>> you need set the rules >>>>> >>>>> #man openvas-adduser >>>>> >>>>> RULES >>>>> Each user has his own set of rules. Rules are here to >>>>> restrict the rights of the users. For instance, you can add user ?joe? >>>>> that he can only test the host ?192.168.1.1?bob? >>>>> >>>>> Each rule fits on one line. A user can have an unlimited amount >>>>> of rules (and can even have no rule at all). >>>>> >>>>> The syntax is: >>>>> accept|deny ip/mask >>>>> and >>>>> default accept|deny >>>>> >>>>> Where mask is the CIDR netmask of the rule. >>>>> >>>>> The default statement must be the last rule and defines the >>>>> policy of the user. >>>>> >>>>> The following rule set will allow the user to test >>>>> 192.168.1.0/24, 192.168.3.0/24 and 172.22.0.0/16, but nothing else: >>>>> accept 192.168.1.0/24 >>>>> accept 192.168.3.0/24 >>>>> accept 172.22.0.0/16 >>>>> default deny >>>>> >>>>> The following rule set will allow the user to test whatever he >>>>> wants, except the network 192.168.1.0/24: >>>>> deny 192.168.1.0/24 >>>>> default accept >>>>> >>>>> The keyword client_ip has been defined, and is replaced at run >>>>> time by the IP address of the openvasd user. For instance, if you >>>>> want your users to be able to only be able to scan the system >>>>> they come from, then you want them to have the following ruleset: >>>>> accept client_ip >>>>> default deny >>>>> >>>>> Best Regards, >>>>> >>>>> On Tue, Aug 19, 2008 at 10:44 AM, Saulo Medeiros de Ara?jo < >>>>> saulov8 at gmail.com> wrote: >>>>> >>>>>> Im having a problem to access the openvas-client with the users >>>>>> created with openvas-adduser. >>>>>> * >>>>>> oink:~# openvas-adduser >>>>>> Using /var/tmp as a temporary file holder. >>>>>> >>>>>> Add a new openvasd user >>>>>> --------------------------------- >>>>>> >>>>>> >>>>>> Login : teste3 >>>>>> Authentication (pass/cert) [pass] : >>>>>> Login password : >>>>>> Login password (again) : >>>>>> >>>>>> User rules >>>>>> --------------- >>>>>> openvasd has a rules system which allows you to restrict the hosts >>>>>> that teste3 has the right to test. >>>>>> For instance, you may want him to be able to scan his own host only. >>>>>> >>>>>> Please see the openvas-adduser(8) man page for the rules syntax. >>>>>> >>>>>> Enter the rules for this user, and hit ctrl-D once you are done: >>>>>> (the user can have an empty rules set) >>>>>> default accept >>>>>> >>>>>> >>>>>> Login : teste3 >>>>>> Password : *********** >>>>>> >>>>>> Rules : >>>>>> default accept >>>>>> >>>>>> >>>>>> Is that ok? (y/n) [y] y >>>>>> user added.* >>>>>> >>>>>> In the openvas-client i got this error message when i use the user >>>>>> teste3: >>>>>> >>>>>> *Error: Login failed* >>>>>> >>>>>> Any help?? >>>>>> >>>>>> _______________________________________________ >>>>>> Openvas-discuss mailing list >>>>>> Openvas-discuss at wald.intevation.org >>>>>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ------------------------------ >>>>> "Seguran?a da Informa??o se faz com tecnologia, processos e pessoas, e >>>>> a forma??o destas exige mais que uma seq??ncia de treinamentos. Porque voc? >>>>> treina macacos. Pessoas,voc? educa." >>>>> >>>>> FreeBSD: The Freedom to Perform! >>>>> http://www.spreadbsd.org/aff/40/1 >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Openvas-discuss mailing list >>>> Openvas-discuss at wald.intevation.org >>>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>>> >>>> >>> >>> _______________________________________________ >>> Openvas-discuss mailing list >>> Openvas-discuss at wald.intevation.org >>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>> >>> >> >> >> >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss at wald.intevation.org >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080819/5caffbbc/attachment.html From jan-oliver.wagner at intevation.de Tue Aug 19 22:25:28 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Tue, 19 Aug 2008 22:25:28 +0200 Subject: [Openvas-discuss] Having a problem compiling openvas-libraries on a Clarkconnect server. In-Reply-To: <0E73B1E0-175B-4019-B8D1-47EFFBD02C3E@omhe.org> References: <0E73B1E0-175B-4019-B8D1-47EFFBD02C3E@omhe.org> Message-ID: <200808192225.30554.jan-oliver.wagner@intevation.de> Hello Hector, On Dienstag, 19. August 2008, Hector Lopez - OMHE wrote: > I have a problem compiling the openvas-libraries on a Clarkconnect > distribution. > > I get the sources via subversion and then i install the gnutls-devel > via apt. > > I pass the ./configure stage but then when i tried to compile i get I do not know Clarkconnect. Which version of gnutls have you installed? Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From jan-oliver.wagner at intevation.de Tue Aug 19 22:34:26 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Tue, 19 Aug 2008 22:34:26 +0200 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <515c3e9d0808191012p36d8fbc0g7ae688876a8d350e@mail.gmail.com> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> <9587e64c0808190715l1e3cd747s3859ad8f99984345@mail.gmail.com> <515c3e9d0808191012p36d8fbc0g7ae688876a8d350e@mail.gmail.com> Message-ID: <200808192234.28525.jan-oliver.wagner@intevation.de> On Dienstag, 19. August 2008, Saulo Medeiros de Ara?jo wrote: > I?ve found something weird: I guess openvas-adduser and openvas-rmuser expect the user directory not at the same place. There should be a directory /var/lib/openvas/users/teste8 for your case. Apparently, the openvasd searches also in another directory and thus does not find your user. This problem might be on your side and as well it might be a problem in the OpenVAS configuration routines. We have to investigate this. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From jan-oliver.wagner at intevation.de Tue Aug 19 22:39:51 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Tue, 19 Aug 2008 22:39:51 +0200 Subject: [Openvas-discuss] error rebuilding openvas-server for fedora core 10 In-Reply-To: <1CA8273BEDC6F44BBB19F22139C53BB0019C78B1@postoffice.audit.local> References: <1CA8273BEDC6F44BBB19F22139C53BB0019C78B1@postoffice.audit.local> Message-ID: <200808192239.54450.jan-oliver.wagner@intevation.de> On Dienstag, 19. August 2008, Barry Smoke wrote: > I know fedora core 10 is alpha(strange that installing core9, then > running an update got us fedora core10)... > > anyway, I was doing an rpmbuild -rebuild on all the fedora source rpm's, > > > and I get this error when recompiling the server rpm: > In function 'open', > > inlined from 'detached_new_session' at detached.c:419: > > /usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' > declared with attribute error: open with O_CREAT in second argument > needs 3 arguments > > make[1]: *** [detached.o] Error 1 > > make[1]: Leaving directory > `/root/rpmbuild/BUILD/openvas-server-1.0.0/openvasd' your are still using 1.0.0 from 2008-01-31. The SVN ChangeLog file of openvas-server shows: 2008-07-01 Jan-Oliver Wagner * MANIFEST: Updated. * openvasd/detached.c (detached_new_session): Fixed wrong use of system call "open" (if O_CREAT is applied, the command needs specification of access flags). 1.0.1 was released 2008-07-03 and thus includes the fix. Hope this helps. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From hl at omhe.org Wed Aug 20 03:03:22 2008 From: hl at omhe.org (Hector Lopez - OMHE) Date: Tue, 19 Aug 2008 20:03:22 -0500 Subject: [Openvas-discuss] Having a problem compiling openvas-libraries on a Clarkconnect server. In-Reply-To: References: Message-ID: Hello Jan, this is the version of gnutls version 1.0.20. Libgnutls 1.0.20 Thanks a lot for your reply > From: "Jan-Oliver Wagner" > Subject: Re: [Openvas-discuss] Having a problem compiling > openvas-libraries on a Clarkconnect server. > To: openvas-discuss at wald.intevation.org > Message-ID: <200808192225.30554.jan-oliver.wagner at intevation.de> > Content-Type: text/plain; charset="iso-8859-1" > > Hello Hector, > > On Dienstag, 19. August 2008, Hector Lopez - OMHE wrote: >> I have a problem compiling the openvas-libraries on a Clarkconnect >> distribution. >> >> I get the sources via subversion and then i install the gnutls-devel >> via apt. >> >> I pass the ./configure stage but then when i tried to compile i get > > I do not know Clarkconnect. > Which version of gnutls have you installed? > > Best > > Jan From michael.wiegand at intevation.de Wed Aug 20 11:47:06 2008 From: michael.wiegand at intevation.de (Michael Wiegand) Date: Wed, 20 Aug 2008 11:47:06 +0200 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <200808192234.28525.jan-oliver.wagner@intevation.de> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> <515c3e9d0808191012p36d8fbc0g7ae688876a8d350e@mail.gmail.com> <200808192234.28525.jan-oliver.wagner@intevation.de> Message-ID: <200808201147.06304.michael.wiegand@intevation.de> Am Dienstag, 19. August 2008 22:34:26 schrieb Jan-Oliver Wagner: > I guess openvas-adduser and openvas-rmuser expect the > user directory not at the same place. > > There should be a directory /var/lib/openvas/users/teste8 for your case. > > Apparently, the openvasd searches also in another directory and thus does > not find your user. I just found the cause: There is a bug in openvas-server 1.0.1 that causes the openvas-adduser script to ignore the configured prefix. So if you have configured openvas-server to use a non-standard path (i.e. by using "./configure --prefix=/home/michael/openvas-testing"), openvas-adduser will ignore the prefix and place the user files under /var/lib/openvas/users/. The remaining components of openvas-server honor the prefix and will look for the user files in $prefix/var/lib/openvas/users/, which will be empty of course. The bug is already fixed in SVN (both trunk and 1-0 branch) and will be fixed in the next release of openvas-server. Saulo, could you check out the SVN version and tell me if that solves your problem? Regards, Michael -- Michael Wiegand OpenPGP key: D7D049EC Intevation GmbH, Osnabr?ck http://www.intevation.de/ Amtsgericht Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From saulov8 at gmail.com Wed Aug 20 14:57:57 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Wed, 20 Aug 2008 09:57:57 -0300 Subject: [Openvas-discuss] openvas-adduser In-Reply-To: <200808201147.06304.michael.wiegand@intevation.de> References: <515c3e9d0808190644h8eeb98fuc082f546b31a62e5@mail.gmail.com> <515c3e9d0808191012p36d8fbc0g7ae688876a8d350e@mail.gmail.com> <200808192234.28525.jan-oliver.wagner@intevation.de> <200808201147.06304.michael.wiegand@intevation.de> Message-ID: <515c3e9d0808200557q112f2d86n567a45dbfe35e027@mail.gmail.com> Thanks a lot Michael, With the SVN version the openvas-adduser worked just fine. But, im still got this issue: *oink:~# openvas-adduser openvasd: error while loading shared libraries: libopenvasnasl.so.1: cannot open shared object file: No such file or directory Executing openvasd failed. Make sure your library loader is configured properly and that openvasd is in your $PATH.* And its solved by executing this command: *oink:~# export LD_LIBRARY_PATH=/usr/local/lib* Now i have to find out what's openvas is capable to do.. On Wed, Aug 20, 2008 at 6:47 AM, Michael Wiegand < michael.wiegand at intevation.de> wrote: > Am Dienstag, 19. August 2008 22:34:26 schrieb Jan-Oliver Wagner: > > I guess openvas-adduser and openvas-rmuser expect the > > user directory not at the same place. > > > > There should be a directory /var/lib/openvas/users/teste8 for your case. > > > > Apparently, the openvasd searches also in another directory and thus does > > not find your user. > > I just found the cause: There is a bug in openvas-server 1.0.1 that causes > the > openvas-adduser script to ignore the configured prefix. > > So if you have configured openvas-server to use a non-standard path (i.e. > by > using "./configure --prefix=/home/michael/openvas-testing"), > openvas-adduser > will ignore the prefix and place the user files > under /var/lib/openvas/users/. The remaining components of openvas-server > honor the prefix and will look for the user files in > $prefix/var/lib/openvas/users/, which will be empty of course. > > The bug is already fixed in SVN (both trunk and 1-0 branch) and will be > fixed > in the next release of openvas-server. > > Saulo, could you check out the SVN version and tell me if that solves your > problem? > > Regards, > > Michael > > -- > Michael Wiegand OpenPGP key: D7D049EC > Intevation GmbH, Osnabr?ck http://www.intevation.de/ > Amtsgericht Osnabr?ck, HR B 18998 > Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080820/304db3b4/attachment.htm From jan-oliver.wagner at intevation.de Wed Aug 20 16:49:52 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Wed, 20 Aug 2008 16:49:52 +0200 Subject: [Openvas-discuss] tcp scanner In-Reply-To: <771357.96310.qm@web59605.mail.ac4.yahoo.com> References: <771357.96310.qm@web59605.mail.ac4.yahoo.com> Message-ID: <200808201649.54963.jan-oliver.wagner@intevation.de> Hell Boris, On Sonntag, 10. August 2008, Boris Chernenko wrote: > --- On Mon, 7/28/08, Jan-Oliver Wagner wrote: > > > I wonder how you are going to rewrite the TCP & > > SYN scanners... Just > > > curious. > > > > thats easy: Pull those C-parts that are not implementable > > in NASL into the > > language/API of NASL. > > Well, we can write a scanner in NASL. It would not be so slow. yes, your implementation looks very straight forward :-) openvas_tcp_scanner.c however also collects banners and it tries to give the impression that it is an elegantly performant implementation to cope with firewalls. Not sure how much truth is in this. However, IMHO it is worth establishing a NASL tcp scanner. So, it would be good to integrate your scanner with OpenVAS. The only problem I see is the Affero V3 license. AFAIU, this is incompatible with GPLv2. Any special reason why using Affero? Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From jan-oliver.wagner at intevation.de Wed Aug 20 17:04:18 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Wed, 20 Aug 2008 17:04:18 +0200 Subject: [Openvas-discuss] Contest 'Best Advances for OpenVAS Network Vulnerability Tests' In-Reply-To: <200808011109.47470.jan-oliver.wagner@intevation.de> References: <200806261551.11333.jan-oliver.wagner@intevation.de> <200808011109.47470.jan-oliver.wagner@intevation.de> Message-ID: <200808201704.21922.jan-oliver.wagner@intevation.de> Hi, after our recent news about OpenVAS 1.0, IMHO it is now time to start the contest. On Freitag, 1. August 2008, Jan-Oliver Wagner wrote: > On Donnerstag, 26. Juni 2008, Jan-Oliver Wagner wrote: > Please feel free to fix or improve the actual announcement of the contest > (we have already two additional sponsorts :-) : so here is my latest proposal. If no concerns are expressed I am all for releasing it end of this week. """ Contest: Best Advances for OpenVAS Network Vulnerability Tests The OpenVAS Team (Open Vulnerability Assessment System, [1]) calls for submission of patches, scripts, converters or anything else that significantly improves the OpenVAS framework for extended Open Source Network Vulnerability Testing. Basically you are free to choose the area of improvements, examples are: * New .nasl scripts for recent security alerts * NASL libraries for simplifying development of new test scripts * Converter routines that (semi-)automatically create NASL scripts from formal security alerts. * Performance improvements for the current tests. There are may other ways to extend/improve the OpenVAS framework. The only hard requirement is that your solution is published as Free Software under GNU GPLv2+. The following rewards have already been offered by the contest sponsors: 1st place: 500 Euro 2nd place: 300 Euro 3rd place: 200 Euro The rewards might increase because additional sponsors are welcome to add to the rewards as along as the contest is open. The OpenVAS homepage [1] will inform about the current status. New sponsors find project contacts under [2]. The sponsors and OpenVAS steering team will jointly choose the winners inspired by these criteria: * number of CVEs/BIDs covered * relevance of the covered alerts * sustainable future benefit (e.g. in the case of supporting APIs) * how well the development was coordinated via the public OpenVAS mailing lists (teams may win as well) * code quality (documentation, design, style) Contest sponsors are (sorted by sponsored amount): * Intevation GmbH, www.intevation.net * DN-Systems GmbH, www.dn-systems.de * Tim Brown Time table: 2008-08-23: Contest started 2008-10-15: Contest closes 2008-10-30: Winners nominated How to participate: * express you wish to participate on the OpenVAS mailing list and what you plan to work on * summarize you contribution before contests closes and submit it on the OpenVAS mailing list [1] www.openvas.org [2] http://www.openvas.org/constitution.html """ -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From saulov8 at gmail.com Wed Aug 20 20:42:48 2008 From: saulov8 at gmail.com (=?ISO-8859-1?Q?Saulo_Medeiros_de_Ara=FAjo?=) Date: Wed, 20 Aug 2008 15:42:48 -0300 Subject: [Openvas-discuss] openvas-client isn't getting information Message-ID: <515c3e9d0808201142g6dd3ef09xef5ec3abd001653a@mail.gmail.com> Folks, Now i got another problem. The openvas-client doesn't get any information/issues/vulnerabilities from the targets. I created two users for openvas-client, and set those following rules for witch one: # Login : saulo # Password : *********** # # Rules : # accept client_ip # accept 10.0.0.0/16 # default deny # # # Is that ok? (y/n) [y] y # user added. # Login : admin # Password : *********** # # Rules : # # # Is that ok? (y/n) [y] y # user added. But with both users openvas-client doens't get any information. Thanks for any help. Cheers! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080820/eeed09e0/attachment.htm From phornung at gmail.com Wed Aug 20 20:49:37 2008 From: phornung at gmail.com (Patrick Hornung) Date: Wed, 20 Aug 2008 14:49:37 -0400 Subject: [Openvas-discuss] openvas-client isn't getting information In-Reply-To: <515c3e9d0808201142g6dd3ef09xef5ec3abd001653a@mail.gmail.com> References: <515c3e9d0808201142g6dd3ef09xef5ec3abd001653a@mail.gmail.com> Message-ID: <9587e64c0808201149v57959567y80655decf70b8ee5@mail.gmail.com> Which plugins are you using? So far, it seems you've made it as far as I have with the included plugins. If you search in your openvasd log directory (I think /usr/share/openvas/var/log or something similar) the error log may show the scan quit with a SIGSEGV error. Once I cleaned out the default plugins (wiped out everything in the plugins directory) and ran the openvas-nvt-sync command, it pulls in only the new and approved plugins. From there, scans can complete and vulnerabilities will be listed. This is what happened for me, anyway. Not sure if it applies in your case or not... On Wed, Aug 20, 2008 at 2:42 PM, Saulo Medeiros de Ara?jo wrote: > Folks, > > Now i got another problem. The openvas-client doesn't get any > information/issues/vulnerabilities from the targets. I created two users for > openvas-client, and set those following rules for witch one: > > # Login : saulo > # Password : *********** > # > # Rules : > # accept client_ip > # accept 10.0.0.0/16 > # default deny > # > # > # Is that ok? (y/n) [y] y > # user added. > > > # Login : admin > # Password : *********** > # > # Rules : > # > # > # Is that ok? (y/n) [y] y > # user added. > > > But with both users openvas-client doens't get any information. > > Thanks for any help. > > Cheers! > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080820/90680024/attachment.html From l.grunwald at dn-systems.de Wed Aug 20 22:03:18 2008 From: l.grunwald at dn-systems.de (Lukas Grunwald) Date: Wed, 20 Aug 2008 13:03:18 -0700 Subject: [Openvas-discuss] tcp scanner In-Reply-To: <200808201649.54963.jan-oliver.wagner@intevation.de> References: <771357.96310.qm@web59605.mail.ac4.yahoo.com> <200808201649.54963.jan-oliver.wagner@intevation.de> Message-ID: <48AC7886.6090804@dn-systems.de> Hi, >>> thats easy: Pull those C-parts that are not implementable >>> in NASL into the >>> language/API of NASL. >>> >> Well, we can write a scanner in NASL. It would not be so slow. >> > > yes, your implementation looks very straight forward :-) > > openvas_tcp_scanner.c however also collects banners > and it tries to give the impression that it is an elegantly > performant implementation to cope with firewalls. > Not sure how much truth is in this. > > However, IMHO it is worth establishing a NASL tcp scanner. > The problem is, you need very different timings to go with this, and be below triggers of firewalls in some cases, it is not that simple. -- Gruss Lukas Grunwald aka REG lg1 http://www.dn-systems.de mail: l.grunwald at dn-systems.de DN-Systems Enterprise Internet Solutions GmbH Hornemannstr. 11 31137 Hildesheim, Germany -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080820/da2f494b/attachment.htm From zangds at netpower.com.cn Thu Aug 21 03:42:07 2008 From: zangds at netpower.com.cn (=?gb2312?B?6rC2rMvJ?=) Date: Thu, 21 Aug 2008 09:42:07 +0800 Subject: [Openvas-discuss] login failed Message-ID: <200808210942067893949@netpower.com.cn> hello, I'm a beginer to openvas. I have just install openvas-server(openvasd (OpenVAS) 1.0.1 for Linux ) on a machine with debian. and then I add a user with openvas-adduser,create a cert with openvas-mkcert . Next I installed OpenVAS-Client 1.0.3. on another machine running win xp. But when a connect the server use the username,it tells me Error:login failed. ps:I choose "Use SSL Encryption" and select the cacert.pem file created on the server. Is anything I did wrong? Thx. 2008-08-21 ê°¶¬ËÉ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080821/669fe49b/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: man_018.gif Type: image/gif Size: 2079 bytes Desc: not available Url : http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080821/669fe49b/man_018.gif From jan-oliver.wagner at intevation.de Thu Aug 21 09:48:41 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Thu, 21 Aug 2008 09:48:41 +0200 Subject: [Openvas-discuss] login failed In-Reply-To: <200808210942067893949@netpower.com.cn> References: <200808210942067893949@netpower.com.cn> Message-ID: <200808210948.43853.jan-oliver.wagner@intevation.de> Hello, On Donnerstag, 21. August 2008, ??? wrote: > I'm a beginer to openvas. > I have just install openvas-server(openvasd (OpenVAS) 1.0.1 for Linux ) on a machine with debian. > and then I add a user with openvas-adduser,create a cert with openvas-mkcert . > > Next I installed OpenVAS-Client 1.0.3. on another machine running win xp. > But when a connect the server use the username,it tells me Error:login failed. > ps:I choose "Use SSL Encryption" and select the cacert.pem file created on the server. > > Is anything I did wrong? you probably have been hit by the same problem discussed recently. openvas-add-user might have failed to create the user in the correct directory. Please see in /var/lib/openvas/users whether there is a directory with the name of the user. If you have used a different prefix for compilation, you now have to move the user directory to whereever you have prefixed. This problem is already fixed and will not occur with the next release. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From jan-oliver.wagner at intevation.de Thu Aug 21 09:52:03 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Thu, 21 Aug 2008 09:52:03 +0200 Subject: [Openvas-discuss] tcp scanner In-Reply-To: <48AC7886.6090804@dn-systems.de> References: <771357.96310.qm@web59605.mail.ac4.yahoo.com> <200808201649.54963.jan-oliver.wagner@intevation.de> <48AC7886.6090804@dn-systems.de> Message-ID: <200808210952.06335.jan-oliver.wagner@intevation.de> On Mittwoch, 20. August 2008, Lukas Grunwald wrote: > >>> thats easy: Pull those C-parts that are not implementable > >>> in NASL into the > >>> language/API of NASL. > >>> > >> Well, we can write a scanner in NASL. It would not be so slow. > >> > > > > yes, your implementation looks very straight forward :-) > > > > openvas_tcp_scanner.c however also collects banners > > and it tries to give the impression that it is an elegantly > > performant implementation to cope with firewalls. > > Not sure how much truth is in this. > > > > However, IMHO it is worth establishing a NASL tcp scanner. > > > The problem is, you need very different timings to go with this, and be > below triggers of firewalls in some cases, it is not that simple. thanks for the hint. That means it does make sense to eventually pull in some timing tricks into NASL API. Might help for other tests as well. Personally, I do currently have other priorities, but if any taker is out there :-) Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From zangds at netpower.com.cn Fri Aug 22 11:46:24 2008 From: zangds at netpower.com.cn (=?gb2312?B?6rC2rMvJ?=) Date: Fri, 22 Aug 2008 17:46:24 +0800 Subject: [Openvas-discuss] openvas-nvt-sync only get "debian local security checks" Message-ID: <200808221746242420515@netpower.com.cn> when I run openvas-nvt-sync ,I only get deb_***_*.nasl in /usr/local/lib/openvas/plugins directory.Is that normal ? 2008-08-22 ê°¶¬ËÉ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080822/7c4ac44d/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: man_018.gif Type: image/gif Size: 2079 bytes Desc: not available Url : http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080822/7c4ac44d/man_018.gif From jan-oliver.wagner at intevation.de Fri Aug 22 13:57:59 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Fri, 22 Aug 2008 13:57:59 +0200 Subject: [Openvas-discuss] openvas-nvt-sync only get "debian local security checks" In-Reply-To: <200808221746242420515@netpower.com.cn> References: <200808221746242420515@netpower.com.cn> Message-ID: <200808221358.01545.jan-oliver.wagner@intevation.de> On Freitag, 22. August 2008, ??? wrote: > when I run openvas-nvt-sync ,I only get deb_***_*.nasl in /usr/local/lib/openvas/plugins directory.Is that normal ? yes. Currently only the debian Local Security Checks are served by the feed. This might drastically change in the near future, though. You should also install openvas-plugins, of course. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From jan-oliver.wagner at intevation.de Fri Aug 22 15:38:51 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Fri, 22 Aug 2008 15:38:51 +0200 Subject: [Openvas-discuss] Next Tier for the OpenVAS feed: join with OSSIM/AlienVault Message-ID: <200808221538.53802.jan-oliver.wagner@intevation.de> Hello, currently there are two NVT feed for OpenVAS available: * The OpenVAS NVT Feed: http://www.openvas.org/openvas-nvt-feed.html * The AlienVault Feed: http://www.ossim.com/free_nessus_feed.php The OpenVAS feed was limited to a consistent feed for the Debian Local Security Checks so far and was permanently updated. The AlienVault Feed derives from the needs of the OSSIM project that incorporated Nessus in the past and now is going for OpenVAS. It was created recently and uses the OpenVAS concept based on RSYNC and GnuPG detached signatures. Additional to openvas-plugins and the OpenVAS NVT feed it contained several NVTs from SecPod and AlienVault. Vital discussion has established recently between OpenVAS and OSSIM and the bottom line is to join forces. Not a surprise for cooperative-minded Free Software people ;-) IMHO, there is no reason why OpenVAS NVT feed shouldn't be changed/extended in its contents/mission in order to suffice the needs of the OSSIM users. Basically this would mean to simply add any available .nasl script that is committed to openvas-plugins (all the SecPod scripts arrived in openvas-plugins trunk already today - thanks to Chandra). The mission of the OpenVAS NVT Feed would then be changed to something like "Newest NVTs from Developer Team's Repository". There are some smaller issues that would need to be discussed (like clever structuring of families, OIDs and so on). In fact I do not see any major blocker why we shouldn't start this right away. Quite the opposite - (even slightly) diverging feed contents, would cause a lot of headache over time when trying to understand/discuss with other some scanning results. Opinions welcome. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From nisudoj at yahoo.com Fri Aug 22 21:10:50 2008 From: nisudoj at yahoo.com (NISU DOJ) Date: Fri, 22 Aug 2008 12:10:50 -0700 (PDT) Subject: [Openvas-discuss] gnutls error message Message-ID: <621742.36716.qm@web53602.mail.re2.yahoo.com> I am new to openvas.? I finally got it to work by installing the RPM's for Suse 10.2.? I had failed login errors after installing it via tar file.? Most likely because things were stored in different paths that it expected to be. After connecting and creating a scope to scan my laptop, which is running the client and server, it does the scan and then immediately produces a report which only contains port scan data and no vulnerabilities.? Looks like scan terminates permaturely.? I also installed all the RPMs needed, such as libnasl etc...whats going on here, is my cert not correct??? Check /etc/openvas/openvasd.conf [26411] gnutls_handshake: A TLS packet with unexpected length was received. [26442] gnutls_handshake: A record packet with illegal version was received. [26444] gnutls_handshake: Function was interrupted -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080822/d7d165da/attachment.html From boris.chernenko at yahoo.com Sat Aug 23 18:46:21 2008 From: boris.chernenko at yahoo.com (Boris Chernenko) Date: Sat, 23 Aug 2008 09:46:21 -0700 (PDT) Subject: [Openvas-discuss] tcp scanner In-Reply-To: <200808201649.54963.jan-oliver.wagner@intevation.de> Message-ID: <739516.43200.qm@web59606.mail.ac4.yahoo.com> --- On Wed, 8/20/08, Jan-Oliver Wagner wrote: > So, it would be good to integrate your scanner with > OpenVAS. You may do it, of course. > The only problem I see is the Affero V3 license. AFAIU, > this is incompatible with GPLv2. > Any special reason why using Affero? No special reason. I just copied the license from another program. I can change it if this is a problem. From phornung at gmail.com Thu Aug 28 04:30:27 2008 From: phornung at gmail.com (Patrick Hornung) Date: Wed, 27 Aug 2008 22:30:27 -0400 Subject: [Openvas-discuss] OpenVAS VMware appliance - very basic version Message-ID: <9587e64c0808271930v4b2f195dt3aac6e4472660c58@mail.gmail.com> Although this isn't my finished project, I've built a VMware-based debian install that includes OpenVAS preinstalled. It should help for beginners or new developers that don't want to go through the hassle of building their own server for testing. The download (via torrent) is just under 100MB and is zipped using 7-zip. OpenVAS vulnerability scanner http://www.openvas.org Root password=osva OpenVAS user=osva password=osva This VMware server appliance is built from a minimal Debian installation and contains the following packages installed from source: openvas-libraries 1.02 openvas-libnasl 1.01 openvas-server 1.02 openvas-plugins 1.02 openvas-client 1.04 Instructions: Unzip the virtual machine and open it with either vmware-server or vmware-player. When asked to create or keep identifiers, choose keep. Run the command: export LD_LIBRARY_PATH=/usr/local/lib Run the command: openvasd -D Now you can connect using either the local client or a client on your desktop. If you'd like to download and use the virtual machine, you can download the .torrent from here: http://torrents.thepiratebay.org/4366032/OpenVAS_Server_on_Debian_Etch.4366032.TPB.torrent Hope this helps those who want to try things out, but are having install problems! -Patrick From michael.wiegand at intevation.de Thu Aug 28 08:11:31 2008 From: michael.wiegand at intevation.de (Michael Wiegand) Date: Thu, 28 Aug 2008 08:11:31 +0200 Subject: [Openvas-discuss] gnutls error message In-Reply-To: <366984.32730.qm@web53608.mail.re2.yahoo.com> References: <366984.32730.qm@web53608.mail.re2.yahoo.com> Message-ID: <200808280811.31270.michael.wiegand@intevation.de> Am Mittwoch, 27. August 2008 23:18:23 schrieb NISU DOJ: > I have uninstalled the software and will reinstall the newer version when > available.? However, please do review this information to see if it is > consistent with previous issues. Thank you > > [Fri Aug 22 15:07:51 2008][27630] connection from 127.0.0.1 > [Fri Aug 22 15:07:57 2008][27690] SIGSEGV occured ! > [Fri Aug 22 15:07:57 2008][27686] user (deleted) : test complete > [Fri Aug 22 15:07:57 2008][27686] SIGSEGV occured ! > [Fri Aug 22 15:13:57 2008][27630] Caught HUP signal - reconfiguring Yes, this is consistent with the issue present in OpenVAS-Server 1.0.1. We have released 1.0.2 on Monday, it is available for download at http://wald.intevation.org/frs/?group_id=29&release_id=196 and fixes this bug. Could you test your setup with 1.0.2 and tell me if it works for you? > [26411] gnutls_handshake: A TLS packet with unexpected length was > received. > [26442] gnutls_handshake: A record packet with illegal version was > received. > [26444] gnutls_handshake: Function was interrupted I have looked into this issue and my current observation is that these messages only occur when the server is subject to a scan, i.e. when you are scanning localhost. Can anybody confirm this observation? If that is the case, this is most likely just gnutls noticing the scan and the messages can be ignored. (They should probably be hidden behind an #ifdef DEBUG in that case.) Regards, Michael -- Michael Wiegand OpenPGP key: D7D049EC Intevation GmbH, Osnabr?ck http://www.intevation.de/ Amtsgericht Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From jan-oliver.wagner at intevation.de Fri Aug 29 16:06:15 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Fri, 29 Aug 2008 16:06:15 +0200 Subject: [Openvas-discuss] Next Tier for the OpenVAS feed: join with OSSIM/AlienVault In-Reply-To: <200808221538.53802.jan-oliver.wagner@intevation.de> References: <200808221538.53802.jan-oliver.wagner@intevation.de> Message-ID: <200808291606.17809.jan-oliver.wagner@intevation.de> On Freitag, 22. August 2008, Jan-Oliver Wagner wrote: > IMHO, there is no reason why OpenVAS NVT feed shouldn't be changed/extended > in its contents/mission in order to suffice the needs of the OSSIM users. > Basically this would mean to simply add any available .nasl script that is committed > to openvas-plugins (all the SecPod scripts arrived in openvas-plugins trunk > already today - thanks to Chandra). > The mission of the OpenVAS NVT Feed would then be changed to something like > "Newest NVTs from Developer Team's Repository". > > There are some smaller issues that would need to be discussed (like > clever structuring of families, OIDs and so on). > In fact I do not see any major blocker why we shouldn't start this right away. > Quite the opposite - (even slightly) diverging ?feed contents, would cause > a lot of headache over time when trying to understand/discuss with other some > scanning ?results. > > Opinions welcome. if no concerns are expressed, I will do this change as proposed. Of course we'd need to announce this prior to the change on openvas-announce. -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabr?ck Amtsgericht Osnabr?ck, HR B 18998 http://www.intevation.de/ Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From phornung at gmail.com Sun Aug 31 05:08:36 2008 From: phornung at gmail.com (Patrick Hornung) Date: Sat, 30 Aug 2008 23:08:36 -0400 Subject: [Openvas-discuss] OpenVAS VMware appliance - very basic version In-Reply-To: <9587e64c0808271930v4b2f195dt3aac6e4472660c58@mail.gmail.com> References: <9587e64c0808271930v4b2f195dt3aac6e4472660c58@mail.gmail.com> Message-ID: <9587e64c0808302008q18255937nc9b07cbe5a095eb9@mail.gmail.com> Ok, so things aren't quite as nice as I was hoping they'd be. While the server portion should work fine as a quick and dirty way to get openvas running, the client portion still can't compile right. Here's where I've been stuck for a few days: osva:~/openvas-client-1.0.4# make cd libnessus && make make[1]: Entering directory `/root/openvas-client-1.0.4/libnessus' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/root/openvas-client-1.0.4/libnessus' cd nessus && make make[1]: Entering directory `/root/openvas-client-1.0.4/nessus' gcc -g -O2 -Wall `sh ./cflags` -c auth.c In file included from comm.h:39, from auth.c:35: context.h:29:18: error: glib.h: No such file or directory make[1]: *** [auth.o] Error 1 make[1]: Leaving directory `/root/openvas-client-1.0.4/nessus' make: *** [client] Error 2 I also ran this command to make sure my glib exists: osva:~/openvas-client-1.0.4# pkg-config --cflags glib-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include Seems awfully reproducible in Debian Etch, but something is certainly not right. Any ideas? Once I get this working, I'll make a new .torrent, or just post the download on my web server. On Wed, Aug 27, 2008 at 10:30 PM, Patrick Hornung wrote: > Although this isn't my finished project, I've built a VMware-based > debian install that includes OpenVAS preinstalled. It should help for > beginners or new developers that don't want to go through the hassle > of building their own server for testing. The download (via torrent) > is just under 100MB and is zipped using 7-zip. > > OpenVAS vulnerability scanner > http://www.openvas.org > > Root password=osva > > OpenVAS user=osva password=osva > > This VMware server appliance is built from a minimal Debian > installation and contains the following packages installed from > source: > > openvas-libraries 1.02 > openvas-libnasl 1.01 > openvas-server 1.02 > openvas-plugins 1.02 > openvas-client 1.04 > > Instructions: > Unzip the virtual machine and open it with either vmware-server or > vmware-player. > When asked to create or keep identifiers, choose keep. > Run the command: export LD_LIBRARY_PATH=/usr/local/lib > Run the command: openvasd -D > Now you can connect using either the local client or a client on your > desktop. > > If you'd like to download and use the virtual machine, you can > download the .torrent from here: > > http://torrents.thepiratebay.org/4366032/OpenVAS_Server_on_Debian_Etch.4366032.TPB.torrent > > Hope this helps those who want to try things out, but are having > install problems! > > -Patrick > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080830/51fa7080/attachment.htm From jan-oliver.wagner at intevation.de Sun Aug 31 21:01:08 2008 From: jan-oliver.wagner at intevation.de (Jan-Oliver Wagner) Date: Sun, 31 Aug 2008 21:01:08 +0200 Subject: [Openvas-discuss] OpenVAS VMware appliance - very basic version In-Reply-To: <9587e64c0808302008q18255937nc9b07cbe5a095eb9@mail.gmail.com> References: <9587e64c0808271930v4b2f195dt3aac6e4472660c58@mail.gmail.com> <9587e64c0808302008q18255937nc9b07cbe5a095eb9@mail.gmail.com> Message-ID: <200808312101.11710.jan-oliver.wagner@intevation.de> On Sunday 31 August 2008 05:08, Patrick Hornung wrote: > osva:~/openvas-client-1.0.4# pkg-config --cflags glib-2.0 > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > > Seems awfully reproducible in Debian Etch, but something is certainly not > right. ?Any ideas? is glib.h in one of the above directories? Next, config.log created during configure of OpenVAS-Client might contain some helpful information. 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 From phornung at gmail.com Sun Aug 31 21:37:39 2008 From: phornung at gmail.com (Patrick Hornung) Date: Sun, 31 Aug 2008 15:37:39 -0400 Subject: [Openvas-discuss] OpenVAS VMware appliance - very basic version In-Reply-To: <200808312101.11710.jan-oliver.wagner@intevation.de> References: <9587e64c0808271930v4b2f195dt3aac6e4472660c58@mail.gmail.com> <9587e64c0808302008q18255937nc9b07cbe5a095eb9@mail.gmail.com> <200808312101.11710.jan-oliver.wagner@intevation.de> Message-ID: <9587e64c0808311237n74bd5207h6f96b4c3f41a6d40@mail.gmail.com> Thanks for the reply. The OS is Debian Etch, if I haven't already mentioned it. It is reproducible using the virtual machine I created earlier. Here's a direct link to download the virtual machine (since I believe Comcast is currently blocking my bittorrent): http://michpc.com/osva.7z Indeed, glib.h exists here: /usr/include/glib-2.0/glib.h And here is the contents of config.log: ______________________________________________________________ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:576: checking host system type configure:607: checking for gcc configure:720: checking whether the C compiler (gcc ) works configure:736: gcc -o conftest conftest.c 1>&5 configure:762: checking whether the C compiler (gcc ) is a cross-compiler configure:767: checking whether we are using GNU C configure:795: checking whether gcc accepts -g configure:827: checking whether make sets ${MAKE} configure:865: checking for a BSD compatible install configure:977: checking for pkg-config configure:1021: checking for glib-2.0 >= 2.2.0 configure:1028: checking GLIB_CFLAGS configure:1033: checking GLIB_LIBS configure:1066: checking how to run the C preprocessor configure:1146: checking for ANSI C header files configure:1250: checking for sys/wait.h that is POSIX.1 compatible configure:1292: checking whether time.h and sys/time.h may both be included configure:1331: checking for dirent.h that defines DIR configure:1369: checking for opendir in -ldir configure:1455: checking for unistd.h configure:1455: checking for string.h configure:1455: checking for strings.h configure:1455: checking for sys/sockio.h configure:1455: checking for sys/socketio.h configure:1495: checking for sys/param.h configure:1495: checking for netinet/tcpip.h configure:1495: checking for netinet/in_systm.h configure:1535: checking for netinet/ip_udp.h configure:1535: checking for netinet/protocols.h configure:1535: checking for sys/ioctl.h configure:1535: checking for netinet/ip_icmp.h configure:1575: checking for rpc/rpc.h configure:1575: checking for netinet/udp.h configure:1575: checking for dlfcn.h configure:1575: checking for sys/un.h configure:1575: checking for memory.h configure:1575: checking for ctype.h configure:1575: checking for errno.h configure:1615: checking for sys/types.h configure:1615: checking for stdlib.h configure:1615: checking for stdio.h configure:1615: checking for sys/filio.h configure:1615: checking for pwd.h configure:1655: checking for assert.h configure:1655: checking for netdb.h configure:1655: checking for netinet/in.h configure:1655: checking for arpa/inet.h configure:1695: checking for poll.h configure:1695: checking for sys/poll.h configure:1695: checking for netinet/ip_tcp.h configure:1695: checking for fcntl.h configure:1695: checking for signal.h configure:1695: checking for limits.h configure:1735: checking for sys/stat.h configure:1735: checking for stat.h configure:1735: checking for net/if.h configure:1735: checking for sys/mman.h configure:1735: checking for sys/resource.h configure:1735: checking for dl.h configure:1775: checking for pty.h configure:1775: checking for termio.h configure:1775: checking for termios.h configure:1775: checking for sgtty.h configure:1775: checking for libutil.h configure:1775: checking for setjmp.h configure:1775: checking for values.h configure:1815: checking for locale.h configure:1873: checking for sys/socket.h configure:1873: checking for netinet/ip.h configure:1873: checking for netinet/tcp.h configure:1916: checking for working alloca.h configure:1949: checking for alloca configure:2148: checking for wait3 that fills in rusage configure:2212: checking for waitpid configure:2212: checking for wait4 configure:2212: checking for mmap configure:2212: checking for atexit configure:2267: checking for lstat configure:2267: checking for memmove configure:2267: checking for gettimeofday configure:2267: checking for gethrtime configure:2267: checking for getrusage configure:2267: checking for rand configure:2322: checking for strchr configure:2322: checking for memcpy configure:2322: checking for select configure:2322: checking for poll configure:2375: checking for vsnprintf configure:2428: checking for bzero configure:2428: checking for bcopy configure:2428: checking for setsid configure:2428: checking for rint configure:2428: checking for mkstemp configure:2483: checking for addr2ascii configure:2483: checking for inet_neta configure:2483: checking for setproctitle configure:2483: checking for _exit configure:2537: checking size of unsigned int configure:2577: checking size of unsigned long configure:2617: checking whether byte ordering is bigendian configure:2707: checking for time_t configure:2740: checking for pid_t configure:2773: checking for size_t configure:2806: checking for uid_t in sys/types.h configure:2883: checking for dlopen in -ldl configure:2974: checking for struct timeval configure:2992: gcc -c -g -O2 conftest.c 1>&5 configure:3012: checking whether gettimeofday can't accept two arguments configure:3036: gcc -o conftest -g -O2 conftest.c 1>&5 configure:3066: checking for a working regexp implementation configure:3101: gcc -o conftest -g -O2 conftest.c 1>&5 configure: In function 'main': configure:3089: warning: incompatible implicit declaration of built-in function 'strlen' configure:3120: checking GNU gettext available configure:3136: gcc -c -g -O2 conftest.c 1>&5 configure:3157: checking for X configure:3988: checking for long file names configure:4036: checking for -lsocket configure:4069: checking for -lnsl configure:4102: checking for -lresolv configure:4138: checking for inet_aton in -lc configure:4181: checking for inet_aton in -lresolv configure:4224: checking for compress in -lz configure:4273: checking for dlopen in -ldl configure:4318: checking for snprintf configure:4380: checking if sockaddr{} has sa_len member configure:4574: checking whether struct sigaction has sa_restorer configure:4589: gcc -c -g -O2 conftest.c 1>&5 configure:4725: checking for ar ______________________________________________________________ On Sun, Aug 31, 2008 at 3:01 PM, Jan-Oliver Wagner < jan-oliver.wagner at intevation.de> wrote: > On Sunday 31 August 2008 05:08, Patrick Hornung wrote: > > osva:~/openvas-client-1.0.4# pkg-config --cflags glib-2.0 > > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > > > > Seems awfully reproducible in Debian Etch, but something is certainly not > > right. Any ideas? > > is glib.h in one of the above directories? > > Next, config.log created during configure of OpenVAS-Client might > contain some helpful information. > > 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-discuss mailing list > Openvas-discuss at wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080831/bbc0112f/attachment.html From gurpreet.singh at teradact.com Fri Aug 29 01:17:21 2008 From: gurpreet.singh at teradact.com (Singh, Gurpreet) Date: Thu, 28 Aug 2008 19:17:21 -0400 Subject: [Openvas-discuss] OpenVAS-Client returns segmentation Fault Message-ID: Hi I am using OpenVAS-Client 1.0.3 under Fedora 8 and I get 'Segmentation fault' when I try to execute it on the terminal under batch mode. Is anyone facing this problem? Please help. Thanks in advance. Gurpreet Singh -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20080828/f0b08dc9/attachment.htm