Here are some ways to debug Bluval.
Blucon.sh
Blucon.sh builds and runs a Docker container that runs the Bluval tests. This uses the Docker builder pattern, in which it creates a container inside a container. The container sometimes has DNS problems which can be tested simply by running a Ubuntu container and testing that it can access the outside world.
The root cause for this may be found from iptables.
ssh access
The tests can fail if there is no ssh access to the system under test, so one has to check what is the reason for the failure. Bluval uses the Robot Framework SSH Client library which in turn uses the Python paramiko library. Paramiko has sometimes problems with the configured keys. The following can be tried:
- Create new keys with ssh-keygen
- Check if ssh-agent is running, it can confuse paramiko
- Check what is in ~/.ssh/config. It could define what are allowable algorithms which could then confuse paramiko
- Turn on debugging in Vuls. In Robot this is " Set Default Configuration loglevel=DEBUG"