Hi folks
I got the following error on a 2 out of 3 servers im running after
leaving scan /24's. I have to flush redis, restart services and rebuild
openvas to fix it. Can someone point me in the right direction for
discovering what maybe causing it?
openvas-scanner.service - LSB: remote
Hi,
I am installing OpenVAS 9 latest release from sources on Debian Stretch
and having issues executing "make" of "gsa-7.0.3" (see error messages
below).
All other package (Libraries, Scanner, Manager) installations have been
executed without any issues.
Can anyone help me further in these
On Tue, Apr 10, 2018 at 10:16:39PM +0200, Reindl Harald wrote:
>
>
> Am 10.04.2018 um 19:39 schrieb Alex Smirnoff:
> > I dare to say any "external security audit" which considers that being a
> > problem is pefromed by morons that should be replaced ASAP.
>
> you have no idea from the real
Am 11.04.2018 um 15:21 schrieb Alex Smirnoff:
> On Tue, Apr 10, 2018 at 10:16:39PM +0200, Reindl Harald wrote:
>> what the hell are you argue here?
>
> Show. Me. A. Real. Attack. Scenario. Where. It. Matters.
>
> Then I would fix. "Because OpenVAS does not like it" may be good enough
> reason
Hi,
see https://github.com/greenbone/gsa/pull/493 for further info about this
problem. You need to apply
the patch of this PR to your sources.
Regards,
Björn
Am 11.04.2018 um 14:02 schrieb Helmut Koers:
> Hi,
>
> I am installing OpenVAS 9 latest release from sources on Debian Stretch and
>
Well, actually it is a NASL script "bug". I put the word "bug" in quotes
because some people would argue that it is intended behavior, but still:
The proper check should be "if the certificate is self-signed, then weak
hash is either non-issue or low criticality bug depending on your
settings".
Hi,
On 10.04.2018 17:46, Andrew Robinson wrote:
> Yes, _I_ appreciate the humor and irony. But the client didn’t find it even
> slightly humorous, particularly when the nurses in the hospital almost
> triggered the lockdown protocol because they thought they were under an
> active threat. An
