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
{{ message }}
This repository has been archived by the owner on Jan 24, 2022. It is now read-only.
Basically, if we have an endpoint that supports both IPv6 and IPv4 on the same hostname (ssh.example.com) and that endpoint has records for both IPv6 and IPv4, but only IPv4 has a listening SSH service we will likely not handle that scenario. This issue is to make sure ssh_scan does have the smarts to handle that gracefully.
The text was updated successfully, but these errors were encountered:
@claudijd One way to handle this we could do first try with IPv6 version if that fails then in the catch block of that we could do for IPv4. Am I correct?
Basically, if we have an endpoint that supports both IPv6 and IPv4 on the same hostname (ssh.example.com) and that endpoint has records for both IPv6 and IPv4, but only IPv4 has a listening SSH service we will likely not handle that scenario. This issue is to make sure ssh_scan does have the smarts to handle that gracefully.
The text was updated successfully, but these errors were encountered: