Skip to content
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.

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

Fallback mechanism for SNI value to use in case of IP input #125

Open
ehsandeep opened this issue Nov 29, 2022 · 0 comments
Open

Fallback mechanism for SNI value to use in case of IP input #125

ehsandeep opened this issue Nov 29, 2022 · 0 comments
Labels
Investigation Something to Investigate Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@ehsandeep
Copy link
Member

tlsx version:

dev/main

Please describe your feature request:

Different server behaves differently depending on requirement when it comes to SNI value to use with tls connection when connecting to IP directly.

echo 45.60.13.153 | go run  . -json -tps | jq . # requires empty SNI
echo 142.251.42.110 | go run  . -json -tps | jq . # requires random SNI

As of #123, empty SNI is used when connecting to IP and random SNI can be passed using -random-sni option following the default behavior of curl when it comes to TLS connection with IP input.

As the purpose of tlsx to connect all possible hosts as possible, we need to implement a fallback mechanism to use appreciated SNI value which requires further research to collect all the possible errors to implement the fallback mechanism effectively.

@ehsandeep ehsandeep added Type: Enhancement Most issues will probably ask for additions or changes. Investigation Something to Investigate labels Nov 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Investigation Something to Investigate Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

No branches or pull requests

1 participant