Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-25 Thread Thijs Stuurman
n Van: Louis Bohm [mailto:lo...@systemgeek.net] Verzonden: vrijdag 23 februari 2018 16:05 Aan: Thijs Stuurman CC: openvas-discuss@wald.intevation.org Onderwerp: Re: [Openvas-discuss] Scanner Master Slave setup I got it working but not sure why. So if I use a username/password and set the credent

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-25 Thread Louis Bohm
] > Verzonden: vrijdag 23 februari 2018 16:05 > Aan: Thijs Stuurman <mailto:thijs.stuur...@internedservices.nl>> > CC: openvas-discuss@wald.intevation.org > <mailto:openvas-discuss@wald.intevation.org> > Onderwerp: Re: [Openvas-discuss] Scanner Master Slave se

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-23 Thread Thijs Stuurman
thijsstuurman Van: Openvas-discuss [mailto:openvas-discuss-boun...@wald.intevation.org] Namens Thijs Stuurman Verzonden: vrijdag 23 februari 2018 16:58 Aan: Louis Bohm CC: openvas-discuss@wald.intevation.org Onderwerp: Re: [Openvas-discuss] Scanner Master Slave setup gvmd is the new name of op

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-23 Thread Thijs Stuurman
n.org Onderwerp: Re: [Openvas-discuss] Scanner Master Slave setup The url says to add a listen=0.0.0.0 port=9393 for openvasmd on the slave. The master will then use just the scanner on the slave not the entire OpenVAS stack of the slave (even though you need to install all of it). The Allow Insec

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-23 Thread Louis Bohm
7D4B 6E02 8BE5 6D46 8007 16AD C048 >> >> W: https://www.internedservices.nl <https://www.internedservices.nl/> | L: >> https://nl.linkedin.com/in/thijsstuurman >> <https://nl.linkedin.com/in/thijsstuurman> >> >> Van: Louis Bohm [mailto:lo...@system

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-23 Thread Thijs Stuurman
rijdag 23 februari 2018 16:00 Aan: Thijs Stuurman CC: openvas-discuss@wald.intevation.org Onderwerp: Re: [Openvas-discuss] Scanner Master Slave setup That yelled me this on the client but still the scan has not progressed from Requested. Client: lib serv: DEBUG:2018-02-23 14h37.52 utc:25578:

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-23 Thread Louis Bohm
2018 13:18 > Aan: Thijs Stuurman > CC: openvas-discuss@wald.intevation.org > Onderwerp: Re: [Openvas-discuss] Scanner Master Slave setup > > According to the doc it says to use: > ${CMAKE_INSTALL_PREFIX}"/var/lib/openvas/CA/servercert.pem. > On CentOS 7 that turns out to b

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-23 Thread Thijs Stuurman
Verzonden: vrijdag 23 februari 2018 13:18 Aan: Thijs Stuurman CC: openvas-discuss@wald.intevation.org Onderwerp: Re: [Openvas-discuss] Scanner Master Slave setup According to the doc it says to use: ${CMAKE_INSTALL_PREFIX}"/var/lib/openvas/CA/servercert.pem. On CentOS 7 that turns out to

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-23 Thread Louis Bohm
According to the doc it says to use: ${CMAKE_INSTALL_PREFIX}"/var/lib/openvas/CA/servercert.pem. On CentOS 7 that turns out to be: /var/lib/openvas/CA/servercert.pem according to openvas-manage-certs -V [root@pci-sec02 ~]# openvas-manage-certs -V OK: Directory for keys (/var/lib/openvas/private/C

Re: [Openvas-discuss] Scanner Master Slave setup

2018-02-23 Thread Thijs Stuurman
My best guess is that you didn’t load in the right CA certificate from your slave at step: CA Certificate: The certificate you gathered from the slave Thijs Stuurman Security Operations Center | KPN Internedservices B.V. thijs.stuur...@internedservices.nl