Re: [Openvas-discuss] Autogenerate credential - SOLVED

[Helms , Michael - WVI GmbH]

> -Ursprüngliche Nachricht-
> 
> I wasn't aware that you need rpm and alien for windows stuff. The posted
> documentation by Michael also says that you just need nsis?

Yes, you need nsis. Without nsis all downloaded exe have 0 Byte.

Michael

--
Michael Helms, m.he...@wvigmbh.de
WVI Prof. Dr. Wermuth Verkehrsforschung und Infrastrukturplanung GmbH
Nordstr. 11, 38106 Braunschweig
Sitz Braunschweig, Amtsgericht Braunschweig HRB 2805
Geschäftsführer: Dr.-Ing. Tobias Wermuth
www.wvigmbh.de
___

OpenVAS 8, Kali 2.0



___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

[Openvas-discuss] Problem with Win 7 and remote registry service - second trail

[Helms , Michael - WVI GmbH]

Hello,

I have ask this a few days ago, but the problem still exist. In short:
I scanned an Win7 machine, remote registry service = manual. Scan with domain 
admin, login ok.
The scan don't start the remote registry service, and so the scanresults are 
poor.

Can someone verify or falsify this behavior.

The documentation 
http://docs.greenbone.net/GSM-Manual/gos-3.1/en/scanning.html#requirements-on-target-systems-with-windows
said: "... you could configure manual start up. In that case the service will 
be started while
the system is scanned by GSM and afterwards it will be disabled again... "

Michael

--
Michael Helms, m.he...@wvigmbh.de
WVI Prof. Dr. Wermuth Verkehrsforschung und Infrastrukturplanung GmbH
Nordstr. 11, 38106 Braunschweig
Sitz Braunschweig, Amtsgericht Braunschweig HRB 2805
Geschäftsführer: Dr.-Ing. Tobias Wermuth
www.wvigmbh.de
___

OpenVAS 8, Kali 2.0



___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

[Openvas-discuss] Scanner loading: 43450 / 45616 nvts

[SaiKrishna Katta]

Hi All,

Since from a week and half, I am trying to search internet on fixing below 
error.

I installed openvas on Kali Linux and noticed that scans are getting hanged.
For that I tried

#openvas-setup

 And NVT is getting updated and hangs here. Not sure what is happening.



mdotp-Message: Scanner loading: 42600 / 45616 nvts.

   /mdotp-Message: Scanner loading: 
43450 / 45616 nvts.

   \mdotp-Message: Scanner loading: 
44200 / 45616 nvts.

   /mdotp-Message: Scanner loading: 
44800 / 45616 nvts.

   \mdotp-Message: Scanner loading: 
45400 / 45616 nvts.


tried removing /var/lib/openvas /var/lib/cache and executed openvas-setup and 
still it hangs near 45000 nvts.

when I check openvas-check -setup am getting below error.

root@kali01:~# openvas-check-setup
openvas-check-setup 2.3.0
  Test completeness and readiness of OpenVAS-8
  (add '--v6' or '--v7' or '--9'
   if you want to check for another OpenVAS version)

  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 5.0.1.
OK: OpenVAS Scanner CA Certificate is present as 
/var/lib/openvas/CA/cacert.pem.
OK: OpenVAS Scanner server certificate is valid and present as 
/var/lib/openvas/CA/servercert.pem.
OK: NVT collection in /var/lib/openvas/plugins contains 45546 NVTs.
WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
SUGGEST: Enable signature checking (see 
http://www.openvas.org/trusted-nvts.html).
OK: The NVT cache in /var/cache/openvas contains 45546 files for 45546 
NVTs.
OK: redis-server is present in version v=2.8.17.
OK: scanner (kb_location setting) is configured properly using the 
redis-server socket: /var/lib/redis/redis.sock
OK: redis-server is running and listening on socket: 
/var/lib/redis/redis.sock.
OK: redis-server configuration is OK and redis-server is running.
Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 6.0.1.
OK: OpenVAS Manager client certificate is valid and present as 
/var/lib/openvas/CA/clientcert.pem.
OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
OK: Access rights for the OpenVAS Manager database are correct.
md   main:WARNING:21198:2016-02-09 14h21.07 utc: database must be initialised 
from scanner (with --update or --rebuild)
ERROR: No users found. You need to create at least one user to log in.
It is recommended to have at least one user with role Admin.
FIX: create a user by running 'openvasmd --create-user= 
--role=Admin && openvasmd --user= --new-password='

 ERROR: Your OpenVAS-8 installation is not yet complete!

Please follow the instructions marked with FIX above and run this
script again.

If you think this result is wrong, please report your observation
and help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze 
the problem.



Can some one help me on this please ?

-Regards,
Katta.


___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

[Openvas-discuss] openvas-check-setup

[Hanel Rahman]

Please help to find solution
openvas-check-setup 2.3.3
  Mode:  desktop
  Date:  Tue, 09 Feb 2016 10:17:41 +0530

Checking for old OpenVAS Scanner <= 2.0 ...
/usr/bin/openvas-check-setup: 177: /usr/bin/openvas-check-setup: openvasd: not found

Checking presence of OpenVAS Scanner ...
OpenVAS Scanner 5.0.4
Most new code since 2005: (C) 2015 Greenbone Networks GmbH
Nessus origin: (C) 2004 Renaud Deraison 
License GPLv2: GNU GPL version 2
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.


Checking OpenVAS Scanner version ...

OK: OpenVAS Scanner is present in version 5.0.4.
plugins_folder = /var/lib/openvas/plugins
cache_folder = /var/cache/openvas
include_folders = /var/lib/openvas/plugins
max_hosts = 30
max_checks = 10
be_nice = no
logfile = /var/log/openvas/openvassd.messages
log_whole_attack = no
log_plugins_name_at_load = no
dumpfile = /var/log/openvas/openvassd.dump
cgi_path = /cgi-bin:/scripts
optimize_test = yes
checks_read_timeout = 5
network_scan = no
non_simult_ports = 139, 445
plugins_timeout = 320
safe_checks = yes
auto_enable_dependencies = yes
use_mac_addr = no
nasl_no_signature_check = yes
drop_privileges = no
unscanned_closed = yes
unscanned_closed_udp = yes
vhosts = 
vhosts_ip = 
report_host_details = yes
cert_file = /var/lib/openvas/CA/servercert.pem
key_file = /var/lib/openvas/private/CA/serverkey.pem
ca_file = /var/lib/openvas/CA/cacert.pem
kb_location = /var/lib/redis/redis.sock
config_file = /etc/openvas/openvassd.conf
Checking OpenVAS Scanner CA cert ...

OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem.
Checking OpenVAS Manager server certificate ...
OK: OpenVAS Scanner server certificate is valid and present as /var/lib/openvas/CA/servercert.pem.

Checking presence of redis ...
OK: redis-server is present in version v=3.0.6.

Checking if redis-server is configured properly to run with openVAS ...
OK: scanner (kb_location setting) is configured properly using the redis-server socket: /var/lib/redis/redis.sock
Checking if redis-server is running ...
OK: redis-server is running and listening on socket: /var/lib/redis/redis.sock.
OK: redis-server configuration is OK and redis-server is running.

Checking NVT collection ...

OK: NVT collection in /var/lib/openvas/plugins contains 45546 NVTs.
Checking status of signature checking in OpenVAS Scanner ...
WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
SUGGEST: Enable signature checking (see http://www.openvas.org/trusted-nvts.html).

OK: The NVT cache in /var/cache/openvas contains 45546 files for 45546 NVTs.

Checking presence of OpenVAS Manager ...
OpenVAS Manager 6.0.5
Manager DB revision 146
Copyright (C) 2010-2015 Greenbone Networks GmbH
License GPLv2+: GNU GPL version 2 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.



OK: OpenVAS Manager is present in version 6.0.5.
Checking OpenVAS Manager client certificate ...
OK: OpenVAS Manager client certificate is valid and present as /var/lib/openvas/CA/clientcert.pem.

OK: OpenVAS Manager client certificate is present as /var/lib/openvas/CA/clientcert.pem.
Checking OpenVAS Manager database ...

OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
Checking access rights of OpenVAS Manager database ...

OK: Access rights for the OpenVAS Manager database are correct.
Checking sqlite3 presence ...
OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.

Checking OpenVAS Manager database revision ...
OK: OpenVAS Manager database is at revision 146.
Checking database revision expected by OpenVAS Manager ...
OK: OpenVAS Manager expects database at revision 146.
OK: Database schema is up to date.
Checking OpenVAS Manager database (NVT data) ...
OK: OpenVAS Manager database contains information about 45546 NVTs.
Checking if users exist ...
OK: At least one user exists.

Checking OpenVAS SCAP database ...

OK: OpenVAS SCAP database found in /var/lib/openvas/scap-data/scap.db.
Checking OpenVAS CERT database ...

OK: OpenVAS CERT database found in /var/lib/openvas/cert-data/cert.db.
Checking xsltproc presence ...
OK: xsltproc found.

Checking status of password policy ...
WARNING: Your password policy is empty.
SUGGEST: Edit the /etc/openvas/pwpolicy.conf file to set a password policy.

Checking presence of Greenbone Security Assistant ...
Greenbone Security Assistant 6.0.5
Copyright (C) 2010-2015 Greenbone Networks GmbH
License GPLv2+: GNU GPL version 2 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.



OK: Greenbone Security Assistant 

[Openvas-discuss] Scanner loading: 43450 / 45616 nvts

[SaiKrishna Katta]

Hi All,

Since from a week and half, I am trying to search internet on fixing below 
error.

I installed openvas on Kali Linux and noticed that scans are getting hanged.
For that I tried

#openvas-setup

 And NVT is getting updated and hangs here. Not sure what is happening.



mdotp-Message: Scanner loading: 42600 / 45616 nvts.

   /mdotp-Message: Scanner loading: 
43450 / 45616 nvts.

   \mdotp-Message: Scanner loading: 
44200 / 45616 nvts.

   /mdotp-Message: Scanner loading: 
44800 / 45616 nvts.

   \mdotp-Message: Scanner loading: 
45400 / 45616 nvts.


tried removing /var/lib/openvas /var/lib/cache and executed openvas-setup and 
still it hangs near 45000 nvts.

when I check openvas-check -setup am getting below error.

root@kali01:~# openvas-check-setup
openvas-check-setup 2.3.0
  Test completeness and readiness of OpenVAS-8
  (add '--v6' or '--v7' or '--9'
   if you want to check for another OpenVAS version)

  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 5.0.1.
OK: OpenVAS Scanner CA Certificate is present as 
/var/lib/openvas/CA/cacert.pem.
OK: OpenVAS Scanner server certificate is valid and present as 
/var/lib/openvas/CA/servercert.pem.
OK: NVT collection in /var/lib/openvas/plugins contains 45546 NVTs.
WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
SUGGEST: Enable signature checking (see 
http://www.openvas.org/trusted-nvts.html).
OK: The NVT cache in /var/cache/openvas contains 45546 files for 45546 
NVTs.
OK: redis-server is present in version v=2.8.17.
OK: scanner (kb_location setting) is configured properly using the 
redis-server socket: /var/lib/redis/redis.sock
OK: redis-server is running and listening on socket: 
/var/lib/redis/redis.sock.
OK: redis-server configuration is OK and redis-server is running.
Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 6.0.1.
OK: OpenVAS Manager client certificate is valid and present as 
/var/lib/openvas/CA/clientcert.pem.
OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
OK: Access rights for the OpenVAS Manager database are correct.
md   main:WARNING:21198:2016-02-09 14h21.07 utc: database must be initialised 
from scanner (with --update or --rebuild)
ERROR: No users found. You need to create at least one user to log in.
It is recommended to have at least one user with role Admin.
FIX: create a user by running 'openvasmd --create-user= 
--role=Admin && openvasmd --user= --new-password='

 ERROR: Your OpenVAS-8 installation is not yet complete!

Please follow the instructions marked with FIX above and run this
script again.

If you think this result is wrong, please report your observation
and help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze 
the problem.



Can some one help me on this please ?

-Regards,
Katta.


___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

[Openvas-discuss] Can't get OpenVAS server to listen on a specific IP Address

[Lyndon P. Nelson]

I have been trying everything I can find online, and still OpenVAS will only
listen on 127.0.0.1. I have installed Debian Linux (Jessie), and used apt to
install OpenVAS. The install appeared to go well, and openvas-check-setup
seems happy overall. 

 

I have attached the openvas-check-setup.log file, as well as the
configuration files from /etc/default and /etc/init.d  . I have added the
directory name where the file is located to the front of the file name -
they are not really named this in the directory. 

 

Thanks for the help.  

 

Lyndon P. Nelson

 



etc_init.d_openvas-manager
Description: Binary data


etc_init.d_openvas-scanner
Description: Binary data


etc_init.d_greenbone-security-assistant
Description: Binary data


etc_default-openvas-manager
Description: Binary data


etc_default-openvas-scanner
Description: Binary data


etc_default-greenbone-security-assistant
Description: Binary data


openvas-check-setup.log
Description: Binary data
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] openvas-check-setup

[Antu Sanadi]

Hi,

Looks like openvas manager is not started start it.
To start run command  openvasmd

cross verify manager is started or not by running command netstat -antp
following response you should gett

tcp6   0  0 :::9390 :::*LISTEN  
15857/openvasmd


Thanks,
Antu

On Tuesday 09 February 2016 10:29 AM, Hanel Rahman wrote:

Please help to find solution


___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss



--
Saner Personal
A free vulnerability mitigation
software. Build strong defense.
http://www.secpod.com/saner-personal.html

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Scanner loading: 43450 / 45616 nvts

[Antu Sanadi]

Hi,

You need create an administrator user with the --create-user option of
"openvasmd":

$ openvasmd --create-user=myuser

The new user's password is printed on success.

An administrator user can later create further users or
administrators via clients like the Greenbone Security Assistant (GSA).

Also, the new user can change her password via GSA.

For more please  refer the INSTALL file from openvas-manager-6.0.7.

Thanks,
Antu

On Tuesday 09 February 2016 10:18 PM, SaiKrishna Katta wrote:


Hi All,

Since from a week and half, I am trying to search internet on fixing 
below error.


I installed openvas on Kali Linux and noticed that scans are getting 
hanged.

For that I tried

#openvas-setup

 And NVT is getting updated and hangs here. Not sure what is happening.



mdotp-Message: Scanner loading: 42600 / 45616 nvts.
   /md   
 otp-Message: Scanner loading: 43450 / 45616 nvts.
   \md   
 otp-Message: Scanner loading: 44200 / 45616 nvts.
   /md   
 otp-Message: Scanner loading: 44800 / 45616 nvts.
   \md   
 otp-Message: Scanner loading: 45400 / 45616 nvts.



tried removing /var/lib/openvas /var/lib/cache and executed 
openvas-setup and still it hangs near 45000 nvts.


when I check openvas-check -setup am getting below error.

root@kali01:~# openvas-check-setup
openvas-check-setup 2.3.0
  Test completeness and readiness of OpenVAS-8
  (add '--v6' or '--v7' or '--9'
   if you want to check for another OpenVAS version)

  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 5.0.1.
OK: OpenVAS Scanner CA Certificate is present as 
/var/lib/openvas/CA/cacert.pem.
OK: OpenVAS Scanner server certificate is valid and present as 
/var/lib/openvas/CA/servercert.pem.
OK: NVT collection in /var/lib/openvas/plugins contains 45546 
NVTs.
WARNING: Signature checking of NVTs is not enabled in OpenVAS 
Scanner.
SUGGEST: Enable signature checking (see 
http://www.openvas.org/trusted-nvts.html).
OK: The NVT cache in /var/cache/openvas contains 45546 files 
for 45546 NVTs.

OK: redis-server is present in version v=2.8.17.
OK: scanner (kb_location setting) is configured properly using 
the redis-server socket: /var/lib/redis/redis.sock
OK: redis-server is running and listening on socket: 
/var/lib/redis/redis.sock.

OK: redis-server configuration is OK and redis-server is running.
Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 6.0.1.
OK: OpenVAS Manager client certificate is valid and present as 
/var/lib/openvas/CA/clientcert.pem.
OK: OpenVAS Manager database found in 
/var/lib/openvas/mgr/tasks.db.

OK: Access rights for the OpenVAS Manager database are correct.
md   main:WARNING:21198:2016-02-09 14h21.07 utc: database must be 
initialised from scanner (with --update or --rebuild)
ERROR: No users found. You need to create at least one user to 
log in.

It is recommended to have at least one user with role Admin.
FIX: create a user by running 'openvasmd --create-user= 
--role=Admin && openvasmd --user= --new-password='


 ERROR: Your OpenVAS-8 installation is not yet complete!

Please follow the instructions marked with FIX above and run this
script again.

If you think this result is wrong, please report your observation
and help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Please attach the log-file (/tmp/openvas-check-setup.log) to help us 
analyze the problem.




Can some one help me on this please ?

-Regards,
Katta.




___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss



--
Saner Personal
A free vulnerability mitigation
software. Build strong defense.
http://www.secpod.com/saner-personal.html

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[blackndoor]

Thank you Rene Behring.
I followed your advise to upgrade to version 9. I removed openvas8 first and 
then installed the version openvas9
Then, I did the following:

sudo openvas-nvt-sync
sudo openvas-scapdata-sync
sudo openvas-certdata-sync
sudo service openvas-manager stop 
sudo service openvas-scanner stop 
sudo openvassd
sudo openvasmd --migrate
(output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
sql_open: db open, max retry sleep time is 0)
sudo openvasmd --progress --rebuild
(output => Rebuilding NVT cache... failed.)

The rebuilding of the NVT cache failed..
I checked the installation with the openvas-check-setup --v9

Step 2: Checking OpenVAS Manager ... 
OK: OpenVAS Manager is present in version 6.1+beta2.
OK: OpenVAS Manager client certificate is present as 
/var/lib/openvas/CA/clientcert.pem.
OK: OpenVAS Manager database found in /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.
Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to open 
database file
ERROR: Could not determine database revision, database corrupt or in 
invalid format.
FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild it.

So I deleted the file requested and retried the following :

sudo openvassd
sudo openvasmd --migrate
(output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
sql_open: db open, max retry sleep time is 0)
sudo openvasmd --progress --rebuild
(output => Rebuilding NVT cache... failed.)
It is worse now with version 9..


___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[blackndoor]

I understand how to fix. Change the ‘SECURE’ by ‘NORMAL’ in a .c file. Sorry 
for my stupid question..
I have compiled the source. Copied the certificate at the right place.
I’m currently running the scap data sync which takes time…


> Le 11 févr. 2016 à 14:24, Rene Behring  a écrit :
> 
> Well i thought, that the ppa has it already fixed, maybe not for version 9. 
> You can fix it yourself but then you have to compile it.
> 
> Heres something about that problem:
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009171.html
>  
> 
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009256.html
>  
> 
> 
>> Am 11.02.2016 um 14:14 schrieb blackndoor > >:
>> 
>> Yes, I tried other scans before with no success.
>> Here is the content of openvasmd.log :
>> 
>> md main:MESSAGE:2016-02-11 12h46.03 utc:19584: OpenVAS Manager version 
>> 6.1+beta2 (DB revision 155)
>> lib serv:WARNING:2016-02-11 12h46.03 utc:19585: Failed to shake hands with 
>> peer: The signature algorithm is not supported.
>> 
>>> Le 11 févr. 2016 à 13:50, René Behring >> > a écrit :
>>> 
>>> Well that sucks, sorry for that! Have you tried other scans before?
>>> 
>>> What is the openvasmd.log saying? (I had the Same issues because of the 
>>> certificates...)
>>> 
>>> Am 11.02.2016 13:37 schrieb "blackndoor" >> >:
>>> Thank you Rene Behring.
>>> I followed your advise to upgrade to version 9. I removed openvas8 first 
>>> and then installed the version openvas9
>>> Then, I did the following:
>>> 
>>> sudo openvas-nvt-sync
>>> sudo openvas-scapdata-sync
>>> sudo openvas-certdata-sync
>>> sudo service openvas-manager stop 
>>> sudo service openvas-scanner stop 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> 
>>> The rebuilding of the NVT cache failed..
>>> I checked the installation with the openvas-check-setup --v9
>>> 
>>> Step 2: Checking OpenVAS Manager ... 
>>> OK: OpenVAS Manager is present in version 6.1+beta2.
>>> OK: OpenVAS Manager client certificate is present as 
>>> /var/lib/openvas/CA/clientcert.pem.
>>> OK: OpenVAS Manager database found in /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.
>>> Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to 
>>> open database file
>>> ERROR: Could not determine database revision, database corrupt or 
>>> in invalid format.
>>> FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild 
>>> it.
>>> 
>>> So I deleted the file requested and retried the following :
>>> 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> It is worse now with version 9..
>>> 
>>> 
>>> 
>>> ___
>>> Openvas-discuss mailing list
>>> Openvas-discuss@wald.intevation.org 
>>> 
>>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss 
>>> 
>> 
>> ___
>> Openvas-discuss mailing list
>> Openvas-discuss@wald.intevation.org 
>> 
>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
> 

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[blackndoor]

Your post made me doubt. I thought I had use the same settings but it seems 
that not.
I made a new test and results are the same.

I still have to solve the gsa crashes

Thanks

> Le 11 févr. 2016 à 14:24, Rene Behring  a écrit :
> 
> Well i thought, that the ppa has it already fixed, maybe not for version 9. 
> You can fix it yourself but then you have to compile it.
> 
> Heres something about that problem:
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009171.html
>  
> 
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009256.html
>  
> 
> 
>> Am 11.02.2016 um 14:14 schrieb blackndoor > >:
>> 
>> Yes, I tried other scans before with no success.
>> Here is the content of openvasmd.log :
>> 
>> md main:MESSAGE:2016-02-11 12h46.03 utc:19584: OpenVAS Manager version 
>> 6.1+beta2 (DB revision 155)
>> lib serv:WARNING:2016-02-11 12h46.03 utc:19585: Failed to shake hands with 
>> peer: The signature algorithm is not supported.
>> 
>>> Le 11 févr. 2016 à 13:50, René Behring >> > a écrit :
>>> 
>>> Well that sucks, sorry for that! Have you tried other scans before?
>>> 
>>> What is the openvasmd.log saying? (I had the Same issues because of the 
>>> certificates...)
>>> 
>>> Am 11.02.2016 13:37 schrieb "blackndoor" >> >:
>>> Thank you Rene Behring.
>>> I followed your advise to upgrade to version 9. I removed openvas8 first 
>>> and then installed the version openvas9
>>> Then, I did the following:
>>> 
>>> sudo openvas-nvt-sync
>>> sudo openvas-scapdata-sync
>>> sudo openvas-certdata-sync
>>> sudo service openvas-manager stop 
>>> sudo service openvas-scanner stop 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> 
>>> The rebuilding of the NVT cache failed..
>>> I checked the installation with the openvas-check-setup --v9
>>> 
>>> Step 2: Checking OpenVAS Manager ... 
>>> OK: OpenVAS Manager is present in version 6.1+beta2.
>>> OK: OpenVAS Manager client certificate is present as 
>>> /var/lib/openvas/CA/clientcert.pem.
>>> OK: OpenVAS Manager database found in /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.
>>> Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to 
>>> open database file
>>> ERROR: Could not determine database revision, database corrupt or 
>>> in invalid format.
>>> FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild 
>>> it.
>>> 
>>> So I deleted the file requested and retried the following :
>>> 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> It is worse now with version 9..
>>> 
>>> 
>>> 
>>> ___
>>> Openvas-discuss mailing list
>>> Openvas-discuss@wald.intevation.org 
>>> 
>>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss 
>>> 
>> 
>> ___
>> Openvas-discuss mailing list
>> Openvas-discuss@wald.intevation.org 
>> 
>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
> 

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[blackndoor]

I use openvas9 on ubuntu and openvas8 on Kali.
On both OS, I don’t have any firewall neither packet filter.

The only message I have in gsa.log is:
gsad main:WARNING:2016-02-11 18h39.58 UTC:6175: MHD: Error: received handshake 
message out of context


> Le 11 févr. 2016 à 14:24, Rene Behring  a écrit :
> 
> Well i thought, that the ppa has it already fixed, maybe not for version 9. 
> You can fix it yourself but then you have to compile it.
> 
> Heres something about that problem:
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009171.html
>  
> 
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009256.html
>  
> 
> 
>> Am 11.02.2016 um 14:14 schrieb blackndoor > >:
>> 
>> Yes, I tried other scans before with no success.
>> Here is the content of openvasmd.log :
>> 
>> md main:MESSAGE:2016-02-11 12h46.03 utc:19584: OpenVAS Manager version 
>> 6.1+beta2 (DB revision 155)
>> lib serv:WARNING:2016-02-11 12h46.03 utc:19585: Failed to shake hands with 
>> peer: The signature algorithm is not supported.
>> 
>>> Le 11 févr. 2016 à 13:50, René Behring >> > a écrit :
>>> 
>>> Well that sucks, sorry for that! Have you tried other scans before?
>>> 
>>> What is the openvasmd.log saying? (I had the Same issues because of the 
>>> certificates...)
>>> 
>>> Am 11.02.2016 13:37 schrieb "blackndoor" >> >:
>>> Thank you Rene Behring.
>>> I followed your advise to upgrade to version 9. I removed openvas8 first 
>>> and then installed the version openvas9
>>> Then, I did the following:
>>> 
>>> sudo openvas-nvt-sync
>>> sudo openvas-scapdata-sync
>>> sudo openvas-certdata-sync
>>> sudo service openvas-manager stop 
>>> sudo service openvas-scanner stop 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> 
>>> The rebuilding of the NVT cache failed..
>>> I checked the installation with the openvas-check-setup --v9
>>> 
>>> Step 2: Checking OpenVAS Manager ... 
>>> OK: OpenVAS Manager is present in version 6.1+beta2.
>>> OK: OpenVAS Manager client certificate is present as 
>>> /var/lib/openvas/CA/clientcert.pem.
>>> OK: OpenVAS Manager database found in /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.
>>> Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to 
>>> open database file
>>> ERROR: Could not determine database revision, database corrupt or 
>>> in invalid format.
>>> FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild 
>>> it.
>>> 
>>> So I deleted the file requested and retried the following :
>>> 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> It is worse now with version 9..
>>> 
>>> 
>>> 
>>> ___
>>> Openvas-discuss mailing list
>>> Openvas-discuss@wald.intevation.org 
>>> 
>>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss 
>>> 
>> 
>> ___
>> Openvas-discuss mailing list
>> Openvas-discuss@wald.intevation.org 
>> 
>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
> 

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[Rene Behring]

> Your post made me doubt. I thought I had use the same settings but it seems 
> that not.
> I made a new test and results are the same.
> 
> I still have to solve the gsa crashes

So you use OpenVAS 8 on Ubuntu oder Kali? Is there any kind of Firewall/Package 
Filter?
And what does the gsad log is saying?

René
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Autogenerate credential - SOLVED

[Helms , Michael - WVI GmbH]

> 
> Mhhh, i thought you have solved that by installing alien/rpm as
> previously posted?

Before the initial post I had already nsis. Because of your question I removed 
nsis,
checked Win download and then reinstalled nsis.

Indeed I solved the problem by installing alien (that brings rpm with it).

Michael

--
Michael Helms, m.he...@wvigmbh.de
WVI Prof. Dr. Wermuth Verkehrsforschung und Infrastrukturplanung GmbH
Nordstr. 11, 38106 Braunschweig
Sitz Braunschweig, Amtsgericht Braunschweig HRB 2805
Geschäftsführer: Dr.-Ing. Tobias Wermuth
www.wvigmbh.de
___

OpenVAS 8, Kali 2.0




___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] still Master - Slave Problems

[Rene Behring]

>>> As i remember correctly, we started 3 tasks with 1 target each. After every
>>> task was DONE (so we had no trouble) all the data remains on the slave. So
>>> not only the Portlists, the task, the scanconfig and the target (i think
>>> even the credentials).
>> 
>> Can you douoble-check that indeed the remains are from a happy "Done" task?
>> 
>> Anything special in your situation that is owrth to mention?
>> 
>> Anyone else here observed this with latest OpenVAS-8?

I have tried to recreate the behavior without success. So everything is fine. I 
will watch if it happens again with scheduled scans.

René
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[Chris]

Hi,

> Opensvas doesn’t mark the system as dead, but I only have the following logs :
> 
> - OS fingerprinting
> - ICMP Timestamp Detection
> - Traceroute
> - CPE Inventory

that are too few log entries. You should have at least:

> - Checks for open tcp ports

containing the detected open ports and stuff like:

> - SSH Server type and version

if there is an SSH server running there.
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[blackndoor]

Thank you Chris.

I used the port list 'All tcp' + full’n’fast scan.
The system is alive as I’m able to ping it or to scan it with nmap.

Opensvas doesn’t mark the system as dead, but I only have the following logs :

- OS fingerprinting
- ICMP Timestamp Detection
- Traceroute
- CPE Inventory

I executed Wireshark during a scan of Openvas and I think that it doesn’t scan 
all the tcp port. I see more information in Wireshark than in Openvas.
For exemple, I find the ssh version of metasploitable2 in wireshark, Openvas 
didn't give anything about that info.

Is there a test to check to functionality of the Openvas scanner ?

Thanks
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[Rene Behring]

Sounds all good to me. Have you scanned an other host? (maybe localhost)

You could also try the openvas 9 beta from the ppa...

> Am 11.02.2016 um 12:18 schrieb blackndoor :
> 
> Thank you Chris.
> 
> I used the port list 'All tcp' + full’n’fast scan.
> The system is alive as I’m able to ping it or to scan it with nmap.
> 
> Opensvas doesn’t mark the system as dead, but I only have the following logs :
> 
> - OS fingerprinting
> - ICMP Timestamp Detection
> - Traceroute
> - CPE Inventory
> 
> I executed Wireshark during a scan of Openvas and I think that it doesn’t 
> scan all the tcp port. I see more information in Wireshark than in Openvas.
> For exemple, I find the ssh version of metasploitable2 in wireshark, Openvas 
> didn't give anything about that info.
> 
> Is there a test to check to functionality of the Openvas scanner ?
> 
> Thanks
> ___
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[blackndoor]

Yes, I tried other scans before with no success.
Here is the content of openvasmd.log :

md main:MESSAGE:2016-02-11 12h46.03 utc:19584: OpenVAS Manager version 
6.1+beta2 (DB revision 155)
lib serv:WARNING:2016-02-11 12h46.03 utc:19585: Failed to shake hands with 
peer: The signature algorithm is not supported.

> Le 11 févr. 2016 à 13:50, René Behring  a écrit :
> 
> Well that sucks, sorry for that! Have you tried other scans before?
> 
> What is the openvasmd.log saying? (I had the Same issues because of the 
> certificates...)
> 
> Am 11.02.2016 13:37 schrieb "blackndoor"  >:
> Thank you Rene Behring.
> I followed your advise to upgrade to version 9. I removed openvas8 first and 
> then installed the version openvas9
> Then, I did the following:
> 
> sudo openvas-nvt-sync
> sudo openvas-scapdata-sync
> sudo openvas-certdata-sync
> sudo service openvas-manager stop 
> sudo service openvas-scanner stop 
> sudo openvassd
> sudo openvasmd --migrate
>   (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
> sql_open: db open, max retry sleep time is 0)
> sudo openvasmd --progress --rebuild
>   (output => Rebuilding NVT cache... failed.)
> 
> The rebuilding of the NVT cache failed..
> I checked the installation with the openvas-check-setup --v9
> 
> Step 2: Checking OpenVAS Manager ... 
> OK: OpenVAS Manager is present in version 6.1+beta2.
> OK: OpenVAS Manager client certificate is present as 
> /var/lib/openvas/CA/clientcert.pem.
> OK: OpenVAS Manager database found in /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.
> Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to 
> open database file
> ERROR: Could not determine database revision, database corrupt or in 
> invalid format.
> FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild it.
> 
> So I deleted the file requested and retried the following :
> 
> sudo openvassd
> sudo openvasmd --migrate
>   (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
> sql_open: db open, max retry sleep time is 0)
> sudo openvasmd --progress --rebuild
>   (output => Rebuilding NVT cache... failed.)
> It is worse now with version 9..
> 
> 
> 
> ___
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org 
> 
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss 
> 

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[Rene Behring]

Well i thought, that the ppa has it already fixed, maybe not for version 9. You 
can fix it yourself but then you have to compile it.

Heres something about that problem:
https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009171.html
 

https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009256.html
 


> Am 11.02.2016 um 14:14 schrieb blackndoor :
> 
> Yes, I tried other scans before with no success.
> Here is the content of openvasmd.log :
> 
> md main:MESSAGE:2016-02-11 12h46.03 utc:19584: OpenVAS Manager version 
> 6.1+beta2 (DB revision 155)
> lib serv:WARNING:2016-02-11 12h46.03 utc:19585: Failed to shake hands with 
> peer: The signature algorithm is not supported.
> 
>> Le 11 févr. 2016 à 13:50, René Behring > > a écrit :
>> 
>> Well that sucks, sorry for that! Have you tried other scans before?
>> 
>> What is the openvasmd.log saying? (I had the Same issues because of the 
>> certificates...)
>> 
>> Am 11.02.2016 13:37 schrieb "blackndoor" > >:
>> Thank you Rene Behring.
>> I followed your advise to upgrade to version 9. I removed openvas8 first and 
>> then installed the version openvas9
>> Then, I did the following:
>> 
>> sudo openvas-nvt-sync
>> sudo openvas-scapdata-sync
>> sudo openvas-certdata-sync
>> sudo service openvas-manager stop 
>> sudo service openvas-scanner stop 
>> sudo openvassd
>> sudo openvasmd --migrate
>>  (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>> sql_open: db open, max retry sleep time is 0)
>> sudo openvasmd --progress --rebuild
>>  (output => Rebuilding NVT cache... failed.)
>> 
>> The rebuilding of the NVT cache failed..
>> I checked the installation with the openvas-check-setup --v9
>> 
>> Step 2: Checking OpenVAS Manager ... 
>> OK: OpenVAS Manager is present in version 6.1+beta2.
>> OK: OpenVAS Manager client certificate is present as 
>> /var/lib/openvas/CA/clientcert.pem.
>> OK: OpenVAS Manager database found in /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.
>> Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to 
>> open database file
>> ERROR: Could not determine database revision, database corrupt or in 
>> invalid format.
>> FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild it.
>> 
>> So I deleted the file requested and retried the following :
>> 
>> sudo openvassd
>> sudo openvasmd --migrate
>>  (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>> sql_open: db open, max retry sleep time is 0)
>> sudo openvasmd --progress --rebuild
>>  (output => Rebuilding NVT cache... failed.)
>> It is worse now with version 9..
>> 
>> 
>> 
>> ___
>> Openvas-discuss mailing list
>> Openvas-discuss@wald.intevation.org 
>> 
>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss 
>> 
> 
> ___
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[blackndoor]

The patch is the attachment.bin file ?
If I understand, I have to uninstall openvas9 and download the official source 
of openvas9,
Sorry for my stupid question but what I have to do with the patch file ? place 
it somewhere in the source before compiling (after compiling)?

Thanks

> Le 11 févr. 2016 à 14:24, Rene Behring  a écrit :
> 
> Well i thought, that the ppa has it already fixed, maybe not for version 9. 
> You can fix it yourself but then you have to compile it.
> 
> Heres something about that problem:
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009171.html
>  
> 
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009256.html
>  
> 
> 
>> Am 11.02.2016 um 14:14 schrieb blackndoor > >:
>> 
>> Yes, I tried other scans before with no success.
>> Here is the content of openvasmd.log :
>> 
>> md main:MESSAGE:2016-02-11 12h46.03 utc:19584: OpenVAS Manager version 
>> 6.1+beta2 (DB revision 155)
>> lib serv:WARNING:2016-02-11 12h46.03 utc:19585: Failed to shake hands with 
>> peer: The signature algorithm is not supported.
>> 
>>> Le 11 févr. 2016 à 13:50, René Behring >> > a écrit :
>>> 
>>> Well that sucks, sorry for that! Have you tried other scans before?
>>> 
>>> What is the openvasmd.log saying? (I had the Same issues because of the 
>>> certificates...)
>>> 
>>> Am 11.02.2016 13:37 schrieb "blackndoor" >> >:
>>> Thank you Rene Behring.
>>> I followed your advise to upgrade to version 9. I removed openvas8 first 
>>> and then installed the version openvas9
>>> Then, I did the following:
>>> 
>>> sudo openvas-nvt-sync
>>> sudo openvas-scapdata-sync
>>> sudo openvas-certdata-sync
>>> sudo service openvas-manager stop 
>>> sudo service openvas-scanner stop 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> 
>>> The rebuilding of the NVT cache failed..
>>> I checked the installation with the openvas-check-setup --v9
>>> 
>>> Step 2: Checking OpenVAS Manager ... 
>>> OK: OpenVAS Manager is present in version 6.1+beta2.
>>> OK: OpenVAS Manager client certificate is present as 
>>> /var/lib/openvas/CA/clientcert.pem.
>>> OK: OpenVAS Manager database found in /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.
>>> Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to 
>>> open database file
>>> ERROR: Could not determine database revision, database corrupt or 
>>> in invalid format.
>>> FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild 
>>> it.
>>> 
>>> So I deleted the file requested and retried the following :
>>> 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> It is worse now with version 9..
>>> 
>>> 
>>> 
>>> ___
>>> Openvas-discuss mailing list
>>> Openvas-discuss@wald.intevation.org 
>>> 
>>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss 
>>> 
>> 
>> ___
>> Openvas-discuss mailing list
>> Openvas-discuss@wald.intevation.org 
>> 
>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
> 

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[Chris]

Hi,

> The patch is the attachment.bin file ?
> If I understand, I have to uninstall openvas9 and download the official 
> source of openvas9,
> Sorry for my stupid question but what I have to do with the patch file ? 
> place it somewhere in the source before compiling (after compiling)?
 
based on this question i think its better if you completely uninstall/purge the 
OpenVAS9 installation and stay with the pre-compiled/packages OpenVAS8 
installation from that ppa. This already includes the fix.
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[blackndoor]

Alright… It seems to work now but not completely…
In fact, I scan the same metasploitable with my ubuntu and with Kali linux 2. 
The version of openvas is not the same on both but the feed version of NVT, 
SCAP and CERT are the same.
the result is different..

On Ubuntu :
- 1 hight
- 7 medium
- 1 low
- 55 logs

On kali the scan takes longer than on ubuntu. I stopped it at 96%:
- 15 hight
- 35 medium
- 7 low
- 88 logs

I don’t know where could come from this huge difference..
I also have gsa which crashes sometimes with the message :
O j: ... this is a bug (sexp.c:1340:vsexp_sscan)


> Le 11 févr. 2016 à 14:24, Rene Behring  a écrit :
> 
> Well i thought, that the ppa has it already fixed, maybe not for version 9. 
> You can fix it yourself but then you have to compile it.
> 
> Heres something about that problem:
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009171.html
>  
> 
> https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-January/009256.html
>  
> 
> 
>> Am 11.02.2016 um 14:14 schrieb blackndoor > >:
>> 
>> Yes, I tried other scans before with no success.
>> Here is the content of openvasmd.log :
>> 
>> md main:MESSAGE:2016-02-11 12h46.03 utc:19584: OpenVAS Manager version 
>> 6.1+beta2 (DB revision 155)
>> lib serv:WARNING:2016-02-11 12h46.03 utc:19585: Failed to shake hands with 
>> peer: The signature algorithm is not supported.
>> 
>>> Le 11 févr. 2016 à 13:50, René Behring >> > a écrit :
>>> 
>>> Well that sucks, sorry for that! Have you tried other scans before?
>>> 
>>> What is the openvasmd.log saying? (I had the Same issues because of the 
>>> certificates...)
>>> 
>>> Am 11.02.2016 13:37 schrieb "blackndoor" >> >:
>>> Thank you Rene Behring.
>>> I followed your advise to upgrade to version 9. I removed openvas8 first 
>>> and then installed the version openvas9
>>> Then, I did the following:
>>> 
>>> sudo openvas-nvt-sync
>>> sudo openvas-scapdata-sync
>>> sudo openvas-certdata-sync
>>> sudo service openvas-manager stop 
>>> sudo service openvas-scanner stop 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> 
>>> The rebuilding of the NVT cache failed..
>>> I checked the installation with the openvas-check-setup --v9
>>> 
>>> Step 2: Checking OpenVAS Manager ... 
>>> OK: OpenVAS Manager is present in version 6.1+beta2.
>>> OK: OpenVAS Manager client certificate is present as 
>>> /var/lib/openvas/CA/clientcert.pem.
>>> OK: OpenVAS Manager database found in /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.
>>> Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to 
>>> open database file
>>> ERROR: Could not determine database revision, database corrupt or 
>>> in invalid format.
>>> FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild 
>>> it.
>>> 
>>> So I deleted the file requested and retried the following :
>>> 
>>> sudo openvassd
>>> sudo openvasmd --migrate
>>> (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
>>> sql_open: db open, max retry sleep time is 0)
>>> sudo openvasmd --progress --rebuild
>>> (output => Rebuilding NVT cache... failed.)
>>> It is worse now with version 9..
>>> 
>>> 
>>> 
>>> ___
>>> Openvas-discuss mailing list
>>> Openvas-discuss@wald.intevation.org 
>>> 
>>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss 
>>> 
>> 
>> ___
>> Openvas-discuss mailing list
>> Openvas-discuss@wald.intevation.org 
>> 
>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
> 

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[Winfried Neessen]

Hi,

> On Ubuntu :
> - 1 hight
> - 7 medium
> - 1 low
> - 55 logs
>
> On kali the scan takes longer than on ubuntu. I stopped it at 96%:
> - 15 hight
> - 35 medium
> - 7 low
> - 88 logs
> 

You might want to compare the port scan settings, enabled NVTs and
scan options on for each task on each machine.


Winni
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Autogenerate credential - SOLVED

[Chris]

> > I wasn't aware that you need rpm and alien for windows stuff. The posted
> > documentation by Michael also says that you just need nsis?
> 
> Yes, you need nsis. Without nsis all downloaded exe have 0 Byte.

Mhhh, i thought you have solved that by installing alien/rpm as previously 
posted?
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] OpenVAS v8 on ubuntu 14.04.03 LTS

[René Behring]

Well that sucks, sorry for that! Have you tried other scans before?

What is the openvasmd.log saying? (I had the Same issues because of the
certificates...)
Am 11.02.2016 13:37 schrieb "blackndoor" :

> Thank you Rene Behring.
>
> I followed your advise to upgrade to version 9. I removed openvas8 first and 
> then installed the version openvas9
> Then, I did the following:
>
> sudo openvas-nvt-sync
> sudo openvas-scapdata-sync
> sudo openvas-certdata-sync
> sudo service openvas-manager stop
> sudo service openvas-scanner stop
> sudo openvassd
> sudo openvasmd --migrate
>   (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
> sql_open: db open, max retry sleep time is 0)
> sudo openvasmd --progress --rebuild
>   (output => Rebuilding NVT cache... failed.)
>
> The rebuilding of the NVT cache failed..
> I checked the installation with the openvas-check-setup --v9
>
> Step 2: Checking OpenVAS Manager ...
> OK: OpenVAS Manager is present in version 6.1+beta2.
> OK: OpenVAS Manager client certificate is present as 
> /var/lib/openvas/CA/clientcert.pem.
> OK: OpenVAS Manager database found in /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.
> Error: unable to open database "/var/lib/openvas/mgr/tasks.db": unable to 
> open database file
> ERROR: Could not determine database revision, database corrupt or in 
> invalid format.
> FIX: Delete database at /var/lib/openvas/mgr/tasks.db and rebuild it.
>
> So I deleted the file requested and retried the following :
>
> sudo openvassd
> sudo openvasmd --migrate
>   (output => md   main:  DEBUG:19215:2016-02-11 13h21.01 CET:
> sql_open: db open, max retry sleep time is 0)
> sudo openvasmd --progress --rebuild
>   (output => Rebuilding NVT cache... failed.)
>
> It is worse now with version 9..
>
>
>
> ___
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss