-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Hang on testing non-TLS HTTP port 80 #2366
Comments
Ok, that means that the problem only appears in some environments, and it is not so easy to reproduce. But why have you closed the issue? In my environment the execution flow goes to testssl.sh#L12129: debugme echo "server hello empty" In your environment it goes to testssl.sh#L12159: echo "no correct server hello" The bifurcation is here: testssl.sh#L12127 if [[ -z "$v2_hello_ascii" ]]; then It remains to figure out how to reliably direct the execution flow to the first branch. |
I used the same docker image. |
Can you use testssl.sh:80 as a target? Not sure why the return code indicates "success" when the SSLv2 ServerHello is empty. There maybe a reason, or not. |
For me it is consistently reproduced with testssl.sh:80. Output
|
Ok, thanks. Not trying to blame your environment but I am curious what your host and docker version is like? |
No problem, here they are.
|
I believe for some reason in Is that possible for you to pull the container and insert |
Here it is: output.txt |
Sorry for the delay. Thanks for the feedback! Status was not as enlightening as I hoped: For some reason the data buffer which is being read is empty -- in your case. On Mac and Linux it is not (Linux also tested w docker). |
Before you open an issue please check which version you are running and whether it is the latest in stable / dev branch
Before you open an issue please whether this is a known problem by searching the issues
Couldn't find anything related by the search phrase
"server hello empty"
.Command line / docker command to reproduce
Expected behavior
No hang. Terminating with the message like
Your system
Official docker image.
Additional context
I haven't experienced such problem if the HTTP port is not standard 80, but e.g. 8080.
The text was updated successfully, but these errors were encountered: