[prev in list] [next in list] [prev in thread] [next in thread]
List: openvas-discuss
Subject: Re: [Openvas-discuss] Help please - my openvas scan did not work ...
From: Alfredo França <alfredo_franca () hotmail ! com>
Date: 2012-03-21 16:27:58
Message-ID: BLU158-W528A5F2BFEDE4DC769EFBFE400 () phx ! gbl
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Can anyone help me with this situation?
Tanx in advance
From: alfredo_franca@hotmail.com
To: openvas-discuss@wald.intevation.org
Date: Wed, 21 Mar 2012 11:43:44 +0000
Subject: [Openvas-discuss] Help please - my openvas scan did not work ...
Hello,
I need your urgent help, I can not put the openvas software working :( .
I have the following test scenario, I have a VirtualBox with a windows 7 has a \
host,then I have two machines, one with backtrack 5 r2, other with windows server \
2003,there are connetivity, when i use the nmap result agaisnt the windows server \
machine i get severl services up, my test is using openvas in backtrack against \
windows server 2003, but the openvas finish the scan without results, I use the scan \
full and fast, and without credencial, i aslo try the others types of scan with the \
same result.
This server do not have any updates so the ideia is seeing many results appearing in \
openvas scanning...
Another situation, is that after I start a scan, the status change to requested and \
stays there some time without change...
In attach I also send the openvassd.conf.
I put here de result of the last log in the following openvas file,
openvassd.messages:
Wed Mar 21 03:02:27 2012][1865] user om starts a new scan. Target(s) : 10.120.59.200, \
with max_hosts = 20 and max_checks = 4 Wed Mar 21 03:02:28 2012][1865] user om : \
testing 10.120.59.200 (::ffff:10.120.59.200) [1887] Wed Mar 21 03:02:39 2012][1887] \
user om : new KB will be saved as \
/usr/local/var/lib/openvas/users/om/kbs/10.120.59.200 Wed Mar 21 03:06:53 2012][1887] \
Finished testing 10.120.59.200. Time : 265.44 secs [Wed Mar 21 03:06:53 2012][1865] \
user om : test complete Wed Mar 21 03:06:54 2012][1865] Total time to scan all hosts \
: 267 seconds Wed Mar 21 03:06:54 2012][1865] user om : Kept alive connection
Wed Mar 21 03:06:54 2012][1865] Communication closed by client
The Installation of openvas seems working, the results of checkup utility is :
root@bt:~# /root/Desktop/openvas-check-setup
openvas-check-setup 2.1.5
Test completeness and readiness of OpenVAS-4
(add '--v5' if you want to check for OpenVAS-5)
Please report us any non-detected problems and
help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Send us the log-file (/tmp/openvas-check-setup.log)
to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner ...
OK: OpenVAS Scanner is present in version 3.2.5.
OK: OpenVAS Scanner CA Certificate is present as \
/usr/local/var/lib/openvas/CA/cacert.pem.
OK: NVT collection in /usr/local/var/lib/openvas/plugins contains 24766 NVTs.
OK: Signature checking of NVTs is enabled in OpenVAS Scanner.
Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 2.0.4.
OK: OpenVAS Manager client certificate is present as \
/usr/local/var/lib/openvas/CA/clientcert.pem.
OK: OpenVAS Manager database found in /usr/local/var/lib/openvas/mgr/tasks.db.
OK: Access rights for the OpenVAS Manager database are correct.
OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
OK: OpenVAS Manager database is at revision 41.
OK: OpenVAS Manager expects database at revision 41.
OK: Database schema is up to date.
OK: OpenVAS Manager database contains information about 24766 NVTs.
OK: xsltproc found.
Step 3: Checking OpenVAS Administrator ...
OK: OpenVAS Administrator is present in version 1.1.2.
OK: At least one user exists.
OK: At least one admin user exists.
Step 4: Checking Greenbone Security Assistant (GSA) ...
OK: Greenbone Security Assistant is present in version 2.0.1.
Step 5: Checking OpenVAS CLI ...
OK: OpenVAS CLI version 1.1.4.SVN.r.
Step 6: Checking Greenbone Security Desktop (GSD) ...
OK: Greenbone Security Desktop is present in Version 1.2.1.
Step 7: Checking if OpenVAS services are up and running ...
OK: netstat found, extended checks of the OpenVAS services enabled.
OK: OpenVAS Scanner is running and listening on all interfaces.
OK: OpenVAS Scanner is listening on port 9391, which is the default port.
WARNING: OpenVAS Manager is running and listening only on the local interface. This \
means that you will not be able to access the OpenVAS Manager from the outside using \
GSD or OpenVAS CLI.
SUGGEST: Ensure that OpenVAS Manager listens on all interfaces.
OK: OpenVAS Manager is listening on port 9390, which is the default port.
OK: OpenVAS Administrator is running and listening only on the local interface.
OK: OpenVAS Administrator is listening on port 9393, which is the default port.
WARNING: Greenbone Security Assistant is running and listening only on the local \
interface. This means that you will not be able to access the Greenbone Security \
Assistant from the outside using a web browser.
SUGGEST: Ensure that Greenbone Security Assistant listens on all interfaces.
OK: Greenbone Security Assistant is listening on port 9392, which is the default \
port. Step 8: Checking nmap installation ...
WARNING: Your version of nmap is not fully supported: 5.61TEST4
SUGGEST: You should install nmap 5.51.
Step 9: Checking presence of optional tools ...
OK: pdflatex found.
WARNING: PDF generation failed, most likely due to missing LaTeX packages. The PDF \
report format will not work.
SUGGEST: Install required LaTeX packages.
OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely \
to work.
WARNING: Could not find rpm binary, LSC credential package generation for RPM and \
DEB based targets will not work.
SUGGEST: Install rpm.
OK: nsis found, LSC credential package generation for Microsoft Windows targets \
is likely to work.
It seems like your OpenVAS-4 installation is OK.
Thanks in advance,
Best regards,
Alfredo
_______________________________________________ Openvas-discuss mailing list \
Openvas-discuss@wald.intevation.org \
http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
[Attachment #5 (text/html)]
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Can anyone help me with this situation?<BR>
<BR>
Tanx in advance<BR>
<BR> <BR>
<DIV>
<DIV id=SkyDrivePlaceholder></DIV>
<HR id=stopSpelling>
From: alfredo_franca@hotmail.com<BR>To: openvas-discuss@wald.intevation.org<BR>Date: \
Wed, 21 Mar 2012 11:43:44 +0000<BR>Subject: [Openvas-discuss] Help please - my \
openvas scan did not work ...<BR><BR> <META name=Generator content="Microsoft \
SafeHTML"> <STYLE>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
<DIV dir=ltr>Hello,<BR> <BR>I need your urgent help, I can not put the openvas \
software working :( . <BR> <BR>I have the following test scenario, I have a \
VirtualBox with a windows 7 has a host,then I have two machines, one with backtrack 5 \
r2, other with windows server 2003,there are connetivity, when i use the \
nmap result agaisnt the windows server machine i get severl services up, my test \
is using openvas in backtrack against windows server 2003, but the openvas finish \
the scan without results, I use the scan full and fast, and without credencial, \
i aslo try the others types of scan with the same result. <BR><BR>This server do not \
have any updates so the ideia is seeing many results appearing in openvas \
scanning...<BR> <BR>Another situation, is that after I start a scan, the status \
change to requested and stays there some time without change...<BR> <BR>In \
attach I also send the openvassd.conf.<BR><BR> <DIV>
<DIV dir=ltr>
<DIV>
<DIV dir=ltr>
<DIV>
<DIV dir=ltr>
<DIV>
<DIV dir=ltr><BR>I put here de result of the last log in the following openvas \
file,<BR> openvassd.messages:<BR></DIV> <BLOCKQUOTE style="MARGIN-RIGHT: 0px" \
dir=ltr>Wed Mar 21 03:02:27 2012][1865] user om starts a new scan. Target(s) : \
10.120.59.200, with max_hosts = 20 and max_checks = 4 <BR>Wed Mar 21 03:02:28 \
2012][1865] user om : testing 10.120.59.200 (::ffff:10.120.59.200) [1887] <BR>Wed Mar \
21 03:02:39 2012][1887] user om : new KB will be saved as \
/usr/local/var/lib/openvas/users/om/kbs/10.120.59.200<BR>Wed Mar 21 03:06:53 \
2012][1887] Finished testing 10.120.59.200. Time : 265.44 secs <BR>[Wed Mar 21 \
03:06:53 2012][1865] user om : test complete<BR>Wed Mar 21 03:06:54 2012][1865] Total \
time to scan all hosts : 267 seconds <BR>Wed Mar 21 03:06:54 2012][1865] user om : \
Kept alive connection<BR>Wed Mar 21 03:06:54 2012][1865] Communication closed by \
client<BR></BLOCKQUOTE> <DIV dir=ltr><BR>The Installation of openvas seems \
working, the results of checkup utility is :<BR> <BR><A \
href="mailto:root@bt">root@bt</A>:~# \
/root/Desktop/openvas-check-setup<BR>openvas-check-setup 2.1.5<BR> Test \
completeness and readiness of OpenVAS-4<BR> (add '--v5' if you want to check \
for OpenVAS-5)<BR> Please report us any non-detected problems and<BR> \
help us to improve this check routine:<BR> <A \
href="http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss" \
target=_blank>http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss</A><BR> \
Send us the log-file (/tmp/openvas-check-setup.log)<BR> to help analyze the \
problem.<BR> Use the parameter --server to skip checks for client \
tools<BR> like GSD and OpenVAS-CLI.<BR><BR>Step 1: Checking OpenVAS Scanner ... \
<BR> <BR>OK: OpenVAS Scanner is present in \
version 3.2.5.<BR> <BR>OK: OpenVAS Scanner \
CA Certificate is present as \
/usr/local/var/lib/openvas/CA/cacert.pem.<BR> \
<BR>OK: NVT collection in /usr/local/var/lib/openvas/plugins contains 24766 \
NVTs.<BR> <BR>OK: Signature checking of \
NVTs is enabled in OpenVAS Scanner.<BR>Step 2: Checking OpenVAS Manager ... \
<BR> <BR>OK: OpenVAS Manager is present in \
version 2.0.4.<BR> <BR>OK: OpenVAS Manager \
client certificate is present as \
/usr/local/var/lib/openvas/CA/clientcert.pem.<BR> \
<BR>OK: OpenVAS Manager database found in \
/usr/local/var/lib/openvas/mgr/tasks.db.<BR> \
<BR>OK: Access rights for the OpenVAS Manager database are \
correct.<BR> <BR>OK: sqlite3 found, \
extended checks of the OpenVAS Manager installation \
enabled.<BR> <BR>OK: OpenVAS Manager \
database is at revision 41.<BR> <BR>OK: \
OpenVAS Manager expects database at revision \
41.<BR> <BR>OK: Database schema is up to \
date.<BR> <BR>OK: OpenVAS Manager database \
contains information about 24766 NVTs.<BR> \
<BR>OK: xsltproc found.<BR>Step 3: Checking OpenVAS Administrator ... \
<BR> <BR>OK: OpenVAS Administrator is \
present in version 1.1.2.<BR> <BR>OK: At \
least one user exists.<BR> <BR>OK: At least \
one admin user exists.<BR>Step 4: Checking Greenbone Security Assistant (GSA) ... \
<BR> <BR>OK: Greenbone Security Assistant \
is present in version 2.0.1.<BR>Step 5: Checking OpenVAS CLI ... \
<BR> <BR>OK: OpenVAS CLI version \
1.1.4.SVN.r.<BR>Step 6: Checking Greenbone Security Desktop (GSD) ... \
<BR> <BR>OK: Greenbone Security Desktop is \
present in Version 1.2.1.<BR>Step 7: Checking if OpenVAS services are up and running \
... <BR> <BR>OK: netstat found, extended \
checks of the OpenVAS services enabled.<BR> \
<BR>OK: OpenVAS Scanner is running and listening on all \
interfaces.<BR> <BR>OK: OpenVAS Scanner is \
listening on port 9391, which is the default \
port.<BR> <BR>WARNING: OpenVAS Manager is \
running and listening only on the local interface. This means that you will not be \
able to access the OpenVAS Manager from the outside using GSD or OpenVAS \
CLI.<BR> <BR>SUGGEST: Ensure that OpenVAS \
Manager listens on all interfaces.<BR> \
<BR> OK: OpenVAS Manager is listening on port 9390, which is the default \
port.<BR> <BR>OK: OpenVAS Administrator is \
running and listening only on the local \
interface.<BR> <BR> OK: OpenVAS \
Administrator is listening on port 9393, which is the default \
port.<BR> <BR> WARNING: Greenbone Security \
Assistant is running and listening only on the local interface. This means that you \
will not be able to access the Greenbone Security Assistant from the outside using a \
web browser.<BR> <BR>SUGGEST: Ensure that \
Greenbone Security Assistant listens on all \
interfaces.<BR> <BR>OK: Greenbone Security \
Assistant is listening on port 9392, which is the default port.<BR>Step 8: Checking \
nmap installation ...<BR> <BR>WARNING: Your \
version of nmap is not fully supported: \
5.61TEST4<BR> <BR> SUGGEST: You should \
install nmap 5.51.<BR>Step 9: Checking presence of optional tools \
...<BR> <BR> OK: pdflatex \
found.<BR> <BR> WARNING: PDF generation failed, most \
likely due to missing LaTeX packages. The PDF report format will not \
work.<BR> <BR>SUGGEST: Install required \
LaTeX packages.<BR> <BR> OK: ssh-keygen found, \
LSC credential generation for GNU/Linux targets is likely to \
work.<BR> <BR> WARNING: Could not find rpm \
binary, LSC credential package generation for RPM and DEB based targets will not \
work.<BR> <BR> SUGGEST: Install \
rpm.<BR> <BR> OK: nsis found, LSC credential \
package generation for Microsoft Windows targets is likely to work.<BR> <BR>It \
seems like your OpenVAS-4 installation is OK.<BR> <BR> <BR>Thanks in \
advance,</DIV> <DIV dir=ltr>Best \
regards,<BR>Alfredo<BR> <BR> <BR></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV><BR>_______________________________________________ \
Openvas-discuss mailing list Openvas-discuss@wald.intevation.org \
http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss</DIV> \
</div></body> </html>
_______________________________________________
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic