Ok, so as it appears _all_ of the OpenVAS default scanner configs use
a default scan mode of TCP Connect (connect()). I see that what I need
to do for my fast scans that are firewalled, is to
clone an existing
scan config, alter the clone, change the TCP Scanning Technique" to SYN
then use that
Hello,
Still tinkering with my ongoing slow scan issues. Basically
I'm on a Kali 2 box with OpenVAS 8, NMAP 7.31. When I'm port scanning
firewalls the scans take forever, 2 hours or more.
I've had some
recommendations to change firewall rules to REJECT instead of DROP. I've
done this and it has
Hello,
Trying to edit any of the included port lists and can't. I
have two users, admin and another one. I have deleted all reports,
tasks, etc, and changed targets to not point to the port list I want to
to edit.
None of my port lists show the wrench as either my admin or
other user. If I
Hello,
As I'm running scans, I get a lot of results in my reports
stating a kernel vulnerability because the scanner is scanning old
kernels that are installed on the system, but not otherwise in use. I
don't want to uninstall the older kernels as there may be a stability
issue requiring me to
Hello,
I'm seeing an issue that I do not quite understand. I have two
OpenVAS users (for the we interface):
1. The Default Admin User.
2.
Another user that I created and assigned to the admin role to.
For Each
User I have created:
1. The same credentials for logging in to target
machines
2. The
As turns out, it was a firewall issue on the target box. Although I
could SSH to the target from a terminal commandline, after reviewing the
firewall rules I can see why OpenVAS could not. In our default iptables
config we specify a hit count (which is not be a problem for manual
logins), and
Thanks for Christians earlier reply and request for more information.
In regards to the issue I'm having where OpenVAS does not appear to
SSH into a target machine using the credentials created. I followed
previous advice and added ssh debugging on the target box,
log_whole_attack etc, and
Hello,
I'm having trouble understanding why the same scan task/target
can take so long sometimes but not other times.
When I run a scan on
one host using the default OpenVAS port list and the Fast and Full scan
type, it can take as much as several hours or more to complete.
I can
see that the
Hello,
Just trying out OpenVAS and having a couple issues. I'll
create a second post for the other one as I do not believe the two are
related.
The first issue I have is that I cannot get credentials in my
targets to work. I've tried both key credentials as well as
user/password credentials and
