New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature: IPv6 compatibility #3

Closed

BernhardGruen opened this issue Dec 20, 2023 · 3 comments · Fixed by #6

BernhardGruen commented Dec 20, 2023

If I try to scan an IPv6 address I get the following error message:

panic: dial tcp: address xxxx:xxxx:xxxx:xxxx::2: too many colons in address

The following command lines were tried:

terrapin-scanner -connect 'xxxx:xxxx:xxxx:xxxx::2'
terrapin-scanner -connect xxxx:xxxx:xxxx:xxxx::2

My workaround for the moment:
I use jtesta/ssh-audit for these cases. Joe Testa luckily implemented the scan for terrapin into his software.

The text was updated successfully, but these errors were encountered:

Contributor

TrueSkrillor commented Dec 20, 2023

Thanks for the report. This is to be expected given that the socket is always tcp, not tcp6. I try to add support for IPv6 today.

TrueSkrillor mentioned this issue

feat: Add support for scanning IPv6 targets #6

Merged

TrueSkrillor closed this as completed in #6

Contributor

TrueSkrillor commented Dec 20, 2023 •

edited

Loading

v1.1.0 is now available, adding support for IPv6. Note that literal IPv6 addresses must be enclosed by square brackets. This was also one of the problems that you encountered. Happy to hear if the latest release works for you.

Author

BernhardGruen commented Dec 21, 2023

Hey @TrueSkrillor,

Thank you for your fast fix and sorry for the late response.
I can confirm that it works as expected using the following command line:
terrapin-scanner -connect [xxxx:xxxx:xxxx:xxxx::2]:22 (Port is optional)

TrueSkrillor pushed a commit that referenced this issue


          Merge pull request #3 from RUB-NDS/main

b4d1757

Sync with upstream

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment