Re: [Openvas-discuss] Failed to start LSB: remote network security auditor - scanner.

2018-08-28 Thread Reindl Harald 


Am 28.08.2018 um 17:30 schrieb Leonardo Lanzi:
> On 08/28/2018 05:12 PM, Reindl Harald wrote:
>> Am 28.08.2018 um 16:33 schrieb Studente di Ingegneria:
>>> ● openvas-scanner.service - LSB: remote network security auditor - scanner
>>>
>>>    Loaded: loaded (/etc/init.d/openvas-scanner; generated)
>>>    Active: failed (Result: timeout) since Tue 2018-08-28 14:08:15 UTC;
>> get rid of that damned sysvinit scripts in 2018
> 
> really you think is a sysv problem?
> 
> With Ubuntu??
> 
> In 2018
> 
> Come on!!!
> 
>  and try to increase
>> TimeoutSec

better be quiet when you don't understand the topic!

* Loaded: loaded (/etc/init.d/openvas-scanner; generated)
* Active: failed (Result: timeout)
* come on, set "TimeoutSec" for systemd in your sysv script

my "TimeoutSec=1200" in /etc/systemd/system/openvas-scanner.service
which overrides the distri version (otherwise iot won't be in
/etc/systemd) is the reason for the whole override
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Failed to start LSB: remote network security auditor - scanner.

2018-08-28 Thread Leonardo Lanzi 


On 08/28/2018 05:12 PM, Reindl Harald wrote:
> 
> 
> Am 28.08.2018 um 16:33 schrieb Studente di Ingegneria:
>> I’m having issues with my OpenVAS9 machine running on Ubuntu 18.04.1
>> LTS: the database is preventing the scanner from starting, as you can
>> see below:
>>
>>
>> ● openvas-scanner.service - LSB: remote network security auditor - scanner
>>
>>    Loaded: loaded (/etc/init.d/openvas-scanner; generated)
>>    Active: failed (Result: timeout) since Tue 2018-08-28 14:08:15 UTC;
>> 4min 50s ago
>>    Docs: man:systemd-sysv-generator(8)
>>    Process: 1121 ExecStart=/etc/init.d/openvas-scanner start
>> (code=killed, signal=TERM)
>>    Tasks: 1 (limit: 4915)
>>    CGroup: /system.slice/openvas-scanner.service
>>            └─1345 /usr/sbin/openvassd
> 
> get rid of that damned sysvinit scripts in 2018

really you think is a sysv problem?

With Ubuntu??

In 2018

Come on!!!

 and try to increase
> TimeoutSec
> 
> [root@openvas:~]$ cat /etc/systemd/system/openvas-scanner.service
> [Unit]
> Description=OpenVAS Scanner
> After=network.service
> Before=openvas-manager.service
> 
> [Service]
> Type=forking
> ExecStart=/usr/sbin/openvassd
> 
> Environment="LANG=en_GB.UTF-8"
> Restart=always
> RestartSec=1
> TimeoutSec=1200
> 
> [Install]
> WantedBy=multi-user.target
> ___
> 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] Failed to start LSB: remote network security auditor - scanner.

2018-08-28 Thread Reindl Harald 


Am 28.08.2018 um 16:33 schrieb Studente di Ingegneria:
> I’m having issues with my OpenVAS9 machine running on Ubuntu 18.04.1
> LTS: the database is preventing the scanner from starting, as you can
> see below:
> 
> 
> ● openvas-scanner.service - LSB: remote network security auditor - scanner
> 
>    Loaded: loaded (/etc/init.d/openvas-scanner; generated)
>    Active: failed (Result: timeout) since Tue 2018-08-28 14:08:15 UTC;
> 4min 50s ago
>    Docs: man:systemd-sysv-generator(8)
>    Process: 1121 ExecStart=/etc/init.d/openvas-scanner start
> (code=killed, signal=TERM)
>    Tasks: 1 (limit: 4915)
>    CGroup: /system.slice/openvas-scanner.service
>            └─1345 /usr/sbin/openvassd

get rid of that damned sysvinit scripts in 2018 and try to increase
TimeoutSec

[root@openvas:~]$ cat /etc/systemd/system/openvas-scanner.service
[Unit]
Description=OpenVAS Scanner
After=network.service
Before=openvas-manager.service

[Service]
Type=forking
ExecStart=/usr/sbin/openvassd

Environment="LANG=en_GB.UTF-8"
Restart=always
RestartSec=1
TimeoutSec=1200

[Install]
WantedBy=multi-user.target
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

[Openvas-discuss] Failed to start LSB: remote network security auditor - scanner.

2018-08-28 Thread Studente di Ingegneria 
Hi everybody,

I’m having issues with my OpenVAS9 machine running on Ubuntu 18.04.1 LTS:
the database is preventing the scanner from starting, as you can see below:


● openvas-scanner.service - LSB: remote network security auditor - scanner

   Loaded: loaded (/etc/init.d/openvas-scanner; generated)
   Active: failed (Result: timeout) since Tue 2018-08-28 14:08:15 UTC; 4min
50s ago
   Docs: man:systemd-sysv-generator(8)
   Process: 1121 ExecStart=/etc/init.d/openvas-scanner start (code=killed,
signal=TERM)
   Tasks: 1 (limit: 4915)
   CGroup: /system.slice/openvas-scanner.service
   └─1345 /usr/sbin/openvassd

Aug 28 14:03:15 security-server systemd[1]: Starting LSB: remote network
security auditor - scanner...
Aug 28 14:08:15 security-server systemd[1]: openvas-scanner.service: Start
operation timed out. Terminating
Aug 28 14:08:15 security-server systemd[1]: openvas-scanner.service: Failed
with result 'timeout'.
Aug 28 14:08:15 security-server systemd[1]: Failed to start LSB: remote
network security auditor - scanner.


I've already tried the solutions proposed by Christian Fischer in an
identical situation but it didn't change anything.

-This is probably the known issue where redis is blocking / doesn't
-accept any connections anymore. Make sure that you have commented out all:
-save xyz
-statements in your redis.conf, delete the dump.rdb of redis and then
-restart redis.
-There are quite a lot posts here at the channel or at the mailinglists
-about that where updating redis like explained above helped.
-Regards"


Before this failure the scanner worked well for a couple of months. I'm not
able to bring the 'openvas-scanner' back up at all. Could someone point me
in the right direction to resolving the issue?

Thank you so much

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

[Openvas-discuss] LDAP Integration

2018-08-28 Thread Madden, Joe 
Hi OpenVAS List,

I'm trying to get Greenbone security assistant to accept ldap authentication 
using Mirosoft AD. I can get ldapsearch to look though the directory and pull 
back DN information by using the following:

ldapsearch -x -h 172.19.0.4 -D "joe.mad...@costaina2m2.com" -W -b "ou=AADDC 
Users,dc=costaina2m2,dc=com" -s sub "(cn=Joe Madden)"

With the account password of 
joe.mad...@costaina2m2.com

Trying to get Openvas to accept 
joe.mad...@costaina2m2.com is not possible 
therefore I suspect we need to use something like this in the ldap settings:

userPrincipalName=%s...@costaina2m2.com,ou=AADDC Users,dc=costaina2m2,dc=com

In the log we get:

gsad vali:  DEBUG:2018-08-28 13h09.04 UTC:8933: openvas_validate: matched
gsad vali:  DEBUG:2018-08-28 13h09.04 UTC:8933: openvas_validate: name login 
value Joe.Madden
gsad vali:  DEBUG:2018-08-28 13h09.04 UTC:8933: matching <^[[:alnum:]-_@.]+$> 
against :
gsad vali:  DEBUG:2018-08-28 13h09.04 UTC:8933: openvas_validate: matched
lib  serv:  DEBUG:2018-08-28 13h09.04 UTC:8933:Connected to server 
'127.0.0.1' port 9390.
lib  serv:  DEBUG:2018-08-28 13h09.04 UTC:8933:Shook hands with server 
'127.0.0.1' port 9390.
lib   xml:  DEBUG:2018-08-28 13h09.04 UTC:8933:asking for 1048576
lib   xml:  DEBUG:2018-08-28 13h09.05 UTC:8933: <= 
gsad base:  DEBUG:2018-08-28 13h09.05 UTC:8933: xsl stylesheet: 
[7.0.30Tue
 Aug 28 13:09:05 2018 UTCLogin 
failed.en_US]
gsad base:  DEBUG:2018-08-28 13h09.05 UTC:8933: text to transform: 
[7.0.30Tue
 Aug 28 13:09:05 2018 UTCLogin 
failed.en_US]
gsad xslt:  DEBUG:2018-08-28 13h09.05 UTC:8933: Registering i18n XSLT module
gsad main:WARNING:2018-08-28 13h09.05 UTC:8933: Authentication failure for 
'Joe.Madden' from 127.0.0.1
gsad main:  DEBUG:2018-08-28 13h09.05 UTC:8933: connectiontype=1

I guess there is something incorrect with the AuthDN, Does anyone have any 
suggestions on how to get it to work?

I've tried the documentation but can't really get any further with it.

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