Skip to content
This repository has been archived by the owner on Jan 24, 2022. It is now read-only.

Add support for IPv4 fallback when IPv6 cannot be established #74

Closed
claudijd opened this issue Aug 15, 2016 · 3 comments
Closed

Add support for IPv4 fallback when IPv6 cannot be established #74

claudijd opened this issue Aug 15, 2016 · 3 comments

Comments

@claudijd
Copy link
Contributor

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.

@jinankjain
Copy link
Collaborator

@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?

@claudijd
Copy link
Contributor Author

@jinankjain yeah, that could work

@jinankjain
Copy link
Collaborator

@claudijd then I would implement that after fixing #112 #104

jinankjain added a commit to jinankjain/ssh_scan that referenced this issue Aug 29, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants