Hi,
On 10.05.2018 16:24, Stelios Barberakis wrote:
> Thank you for your help. I managed to resolve the issue back then,
> cloning and modifying the scan config template.
> Unfortunately after Monday update, I haven't been able to reproduce the
> "printer detection" situation (default scan configs
Hi,
Thank you for your help. I managed to resolve the issue back then, cloning
and modifying the scan config template.
Unfortunately after Monday update, I haven't been able to reproduce the
"printer detection" situation (default scan configs obviously). The issue
seems to have been resolved for m
Hi,
did you had a chance to re-scan your server with the updated feed to see
the extended output?
Regards,
On 30.04.2018 15:33, Stelios Barberakis wrote:
> thanks Christian
>
> On 28 April 2018 at 16:04, Christian Fischer <
> christian.fisc...@greenbone.net> wrote:
>
>> Hi,
>>
>> On 28.04.2018
Hi,
On 28.04.2018 01:30, Stelios Barberakis wrote:
> I apologise if this is a double post, but I think the previous one was
> not delivered.
you can check the delivering status on your own if you browse the
mailing list archives available at:
http://lists.wald.intevation.org/pipermail/openvas-di
Hello all,
I apologise if this is a double post, but I think the previous one was not
delivered.
I am copying from: https://security.stackexchange.com/questions/
184683/change-settings-to-scan-a-printer-with-openvas
I have Openvas 5.1.1 (gui: Greenbone Security Assistant Version 7.0.2), in
Kali
