Some people add the parameter "–scanner-type=OSP-Sensor " but what’s the difference? I tested both and both worked fine. The only difference I could found was the appearance in the web interface.
The type “Greenbone Sensor” references a remote sensor, that is another system running a GVM installation, via the OSP protocol. This makes it possible to run another OpenVAS scanner instance in a different network segment.
my tests show me some other results. No matter of the configuration, the scanns are running on my remote system. The only difference I found is the appearance in GSA.
With --scanner-type=OSP-Sensor the scanner is shown under the Default Scanner from the Main System.
With --scanner-type=OpenVAS the scanner is shown as separat scanner.
If I dont specify the scanner type, like showen in my firtst post, it automaticly sets it to OpenVAS.
Here you see two remote scanner setup with the different type:
But the question is, are there also technical differences in the backround? Does it use the OSP protocol in both cases? Do I need the VTs on the remote system in both cases?
Using “OpenVAS Scanner” remotely is not a supported use case to my knowledge. It may even be an oversight or bug. I don’t have any more information about why and how this could work.
Do I need the VTs on the remote system in both cases?
For the “Greenbone Sensor” case the VTs must be present on the remote system as well, yes.