You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
TestSSL boefje and normalizer complete successfully, although the actual output indicates failure.
To Reproduce
Run TestSSL in a way that it produces failure (e.g. unreachable IP), see what happens in KAT.
Expected behavior
It is fine if KAT is aware that its internal workings (boefje/normalizer) are OK, however, as an end user I would expect some kind of indicator something has gone wrong.
Screenshots
Example output:
[
{
"id" : "scanProblem",
"ip" : "$IPv4/$IPv4",
"port" : "53",
"severity" : "FATAL",
"finding" : "Can't connect to '$IPv4' Make sure a firewall is not between you and your scanning target!"
}
, {
"id" : "scanTime",
"ip" : "$IPv4/$IPv4",
"port" : "53",
"severity" : "WARN",
"finding" : "Scan interrupted"
}
]
Describe the bug
TestSSL boefje and normalizer complete successfully, although the actual output indicates failure.
To Reproduce
Run TestSSL in a way that it produces failure (e.g. unreachable IP), see what happens in KAT.
Expected behavior
It is fine if KAT is aware that its internal workings (boefje/normalizer) are OK, however, as an end user I would expect some kind of indicator something has gone wrong.
Screenshots
Example output:
OpenKAT version
main 20 nov 24
Related
#1828
#1440
The text was updated successfully, but these errors were encountered: