Hi, Ryan Schulze,
Now, I indeed don't konw what to do.
compiling is ok,
scanning is ok,
openvas-nvt-sync is ok, the profile is all tcp and udp, others are all
default.
openvas-scapdata-sync gave an error: HTTP request sent, awaiting
response...404 Not Found 2013-01-05 01:05:34 ERROR 404: Not Found.
ls:cannot access /usr/local/var/lib/openvas/scap-data/nvdcve-2.0-*.xml: No
such file or directory.
you said that "have you tried any of the alternative methods, like
--rsync (either way it shouldn't have any impact on your scan results)?
This is really basic debugging
stuff you should be doing yourself."
I don't update anything, I don't know whether debian and openvas auto
update?
--rsync, how i deal with it? can you give me a detailed example?
How to do the basic debugging stuff? can you give me more detailed
info? I feel the openvas is straner to me now. your mean is that i
should check all the libs version?
About this, I hope that you can give me more detailed info.
Thank you very much.
best regards
2013/1/5 <[email protected]>
> Send Openvas-discuss mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Openvas-discuss digest..."
>
>
> Today's Topics:
>
> 1. Re: questions about building and testing the openvas 5
> released sourcecode (Ryan Schulze)
> 2. Re: about openvas sourcecode compile and run test (Ryan Schulze)
> 3. Openvas 5 against Slackware64... (Ningun Nick)
> 4. viewing the errors when running the openvas bin packages (???)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 04 Jan 2013 08:26:48 -0600
> From: Ryan Schulze <[email protected]>
> To: [email protected]
> Subject: Re: [Openvas-discuss] questions about building and testing
> the openvas 5 released sourcecode
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Are you sure you managed to check out everything correctly? the RNC.xsl
> file missing in your various modules is in SVN. Any firewalls/proxies
> involved that may be making problems with downloading all files? The
> logs look fine btw.
>
>
> On 1/4/2013 1:44 AM, ??? wrote:
> > Hi, /Ryan Schulze,/
> > /Thank you for you told me the followed info, yestoday:/
> > 1, I'm using the latest stable versions from the list on the website
> > http://openvas.org/install-source.html
> >
> > 2, The SVN paths are:
> >
> https://svn.wald.intevation.org/svn/openvas/tags/openvas-libraries-release-5.0.4
> >
> https://svn.wald.intevation.org/svn/openvas/tags/openvas-administrator-release-1.2.1
> >
> https://svn.wald.intevation.org/svn/openvas/tags/openvas-scanner-release-3.3.1
> >
> https://svn.wald.intevation.org/svn/openvas/tags/openvas-manager-release-3.0.5
> >
> https://svn.wald.intevation.org/svn/openvas/tags/openvas-cli-release-1.1.5
> >
> https://svn.wald.intevation.org/svn/openvas/tags/gsa-release-3.0.3
> >
> > Today, I built and test run the openvas, which source code from the
> above links.
> > The openvas scan but the threat is "NONE", detail result info is 8
> logs.
> > During the openvas building and runing, the questions I met with
> are as follows:
> > 1, During building
> > 1) manager module--make doc
> > finalizing index lists...
> > finished...
> > make[3]: *** No rule to make target
> `doc/../src/schema_formats/RNC/RNC.xsl', needed by `doc/omp.rnc'. Stop.
> > make[2]: *** [doc/CMakeFiles/doc.dir/all] Error 2
> > make[1]: *** [doc/CMakeFiles/doc.dir/rule] Error 2
> > make: *** [doc] Error 2
> > 2) manager module--make doc-full
> > finished...
> > make[3]: *** No rule to make target
> `doc/../src/schema_formats/RNC/RNC.xsl', needed by `doc/omp.rnc'. Stop.
> > make[2]: *** [doc/CMakeFiles/doc-full.dir/all] Error 2
> > make[1]: *** [doc/CMakeFiles/doc-full.dir/rule] Error 2
> > make: *** [doc-full] Error 2
> > 3) manager module --make install
> > -- Up-to-date:
> /usr/local/share/openvas/openvasmd/global_schema_formats/787a4a18-dabc-11df-9486-002264764cea/rnc.xsl
> > CMake Error at cmake_install.cmake:105 (FILE):
> > file INSTALL cannot find
> > "/mnt/openvassvn/manager305/src/schema_formats/RNC/RNC.xsl".
> > make: *** [install] Error
> > 4) administrator module --make doc
> > finished... make[3]: *** No rule to make target
> > `doc/../src/schema_formats/RNC/RNC.xsl', needed by `doc/oap.rnc'.
> > Stop. make[2]: *** [doc/CMakeFiles/doc.dir/all] Error 2 make[1]: ***
> > [doc/CMakeFiles/doc.dir/rule] Error 2 make: *** [doc] Error 2
> > 5) administrator module --make install
> > CMake Error at cmake_install.cmake:48 (FILE):
> > file INSTALL cannot find
> > "/mnt/openvassvn/adminitrator121/src/schema_formats/RNC/".
> > make: *** [install] Error 1
> >
> > During testing running,
> > 1)openvasad.log lib auth:WARNING:2013-01-04 01h53.58 EST:15809:
> > Authentication configuration could not be loaded.
> > 2)openvasmd.log event task:MESSAGE:2013-01-04 07h08.42 UTC:15857:
> > Status of task task1 (b9812e33-e1e2-4494-87af-a287cbdc3dfd) has
> > changed to Done event auth:MESSAGE:2013-01-04 07h08.51 utc:16635:
> > Authentication success for user myuser
> > (a6f757f1-ea4c-47c0-ae00-04584115870a) event auth:MESSAGE:2013-01-04
> > 07h09.01 utc:16639: Authentication success for user myuser
> > (a6f757f1-ea4c-47c0-ae00-04584115870a) event auth:MESSAGE:2013-01-04
> > 07h09.12 utc:16642: Authentication success for user myuser
> > (a6f757f1-ea4c-47c0-ae00-04584115870a) event auth:MESSAGE:2013-01-04
> > 07h09.22 utc:16646: Authentication success for user myuser
> > (a6f757f1-ea4c-47c0-ae00-04584115870a) event auth:MESSAGE:2013-01-04
> > 07h09.32 utc:16650: Authentication success for user myuser
> > (a6f757f1-ea4c-47c0-ae00-04584115870a) event auth:MESSAGE:2013-01-04
> > 07h09.43 utc:16653: Authentication success for user myuser
> > (a6f757f1-ea4c-47c0-ae00-04584115870a)
> > 3)openvassd.dump hg_get_name_from_ip: resolved to name localhost
> > SSH-DEBUG: Host 127.0.0.1 <http://127.0.0.1>: no extended credentials
> > configuration.
> > 4)openvassd.messages [Fri Jan 4 06:11:32 2013][11768] openvassd
> > 3.3.1.SVN started [Fri Jan 4 07:06:56 2013][15856] user om starts a
> > new scan. Target(s) : localhost, with max_hosts = 20 and max_checks =
> > 4 [Fri Jan 4 07:06:56 2013][15856] user om : testing 127.0.0.1
> > (::ffff:127.0.0.1) [16087] [Fri Jan 4 07:06:56 2013][16087] user om :
> > new KB will be saved as
> > /usr/local/var/lib/openvas/users/om/kbs/127.0.0.1 <http://127.0.0.1>
> > [Fri Jan 4 07:08:42 2013][16087] Finished testing 127.0.0.1. Time :
> > 105.67 secs [Fri Jan 4 07:08:42 2013][15856] user om : test complete
> > [Fri Jan 4 07:08:42 2013][15856] Total time to scan all hosts : 107
> > seconds [Fri Jan 4 07:08:42 2013][15856] user om : Kept alive
> > connection [Fri Jan 4 07:08:42 2013][15856] Communication closed by
> client
> >
> > How should I deal with these questions?
> > thank you,
> > best regards
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20130104/8a04f21c/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 04 Jan 2013 09:15:32 -0600
> From: Ryan Schulze <[email protected]>
> To: [email protected]
> Subject: Re: [Openvas-discuss] about openvas sourcecode compile and
> run test
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> What is the specific threat you are expecting to show up? A scan should
> at least have a few Log level entries. You seem to be irritated that
> your scans of localhost don't show any threats?
> Which scan profile are you using and did you update your nvt files
> successfully?
>
> In one of your numerous other posts I noticed that you are updating scap
> via wget. according to the output it's throwing a 404, have you tried
> any of the alternative methods, like --rsync (either way it shouldn't
> have any impact on your scan results)? This is really basic debugging
> stuff you should be doing yourself.
>
> On 1/4/2013 4:17 AM, ??? wrote:
> > Hello, everyone,
> > Recently, whether someone compiled and tested the openvas 5 or 6
> > version released sourcecode succeeded and completed on Debian6 and
> > CentOS or other OS?
> > If you compiled and ran succeeded, and scanned the theat is not
> > 'NONE', can you tell me the result? Because I complied and ran the
> > openvas 5 and 6, the threat is 'NONE'.
> > thank you very much.
> > best regards
> >
> >
> >
> > _______________________________________________
> > Openvas-discuss mailing list
> > [email protected]
> >
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20130104/c461e56a/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Fri, 4 Jan 2013 21:23:13 -0200
> From: Ningun Nick <[email protected]>
> To: [email protected]
> Subject: [Openvas-discuss] Openvas 5 against Slackware64...
> Message-ID:
> <
> cah1dnnyqj02tvmw7peyblumnz6nbj02jashw9lwj5+-0wam...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello, when trying to compile the openvas-scan I get the following error:
> http://pastebin.ca/2299112
>
> I already compiled the openvas-libraries after downgrade the gnutls
> version,
>
> OS= Linux Slackware 64 bits.
> Openvas 5.
>
> Thank you in advance
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20130104/fd013ca2/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Sat, 5 Jan 2013 15:08:04 +0800
> From: ??? <[email protected]>
> To: OpenVAS Discussion List <[email protected]>
> Subject: [Openvas-discuss] viewing the errors when running the openvas
> bin packages
> Message-ID:
> <CANqkETp7XkQ+pa8WY6b7_HBGYhTW3v5+1=
> [email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello, everyone,
> I installed the openvas bin packages, when I executed the scanning,
> it viewed the followed info:
> root@localhost:~# Failed to receive data: Connection reset by peer
> Error: received handshake message out of context
> Failed to receive data: A TLS packet with unexpected length was received.
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Error in the push function.
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Error in the push function.
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Error in the push function.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Failed to receive data: A TLS packet with unexpected length was received.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Error in the push function.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Internal application error, closing connection.
> Internal application error, closing connection.
> root@localhost:~# Error: received handshake message out of context
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Internal application error, closing connection.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Broken pipe
> Received malformed line (no colon), closing connection.
> Error 400 (`<html><head><title>Request malformed</title></head><body>Your
> HTTP request was syntactically incorrect.</body></html>') processing
> request, closing connection.
> Failed to send data: Error in the push function.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
> Failed to receive data: A TLS packet with unexpected length was received.
>
> Why it viewed these info?
> thank you very much.
> best regards
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20130105/2d355cbf/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Openvas-discuss mailing list
> [email protected]
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
> ------------------------------
>
> End of Openvas-discuss Digest, Vol 72, Issue 9
> **********************************************
>
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
