Skip to content

Fix ssl.SSLEOFError on HTTP targets when using --full or --sslinfo #77

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

thesw0rd
Copy link

This PR addresses an issue where FinalRecon attempts to run SSL certificate enumeration on HTTP targets, which leads to an ssl.SSLEOFError. This commonly occurs when using --sslinfo or --full against URLs without HTTPS support or when SSL is not available on the specified port.
Changes:

  • Skips the SSL info module (cert()) if the target URL starts with http://.
  • Adds a visible warning message when SSL info is requested for non-HTTPS targets.
  • Logs a note when skipping SSL enumeration for unsupported protocols.

@thewhiteh4t
Copy link
Owner

@thesw0rd what is your test case where you are getting SSLEOFError ?

for example :

image

@thesw0rd
Copy link
Author

There is also ssl Timeout error with some targets

Screenshot_2025-07-13_07-52-14 Screenshot_2025-07-13_07-55-23

@thewhiteh4t
Copy link
Owner

@thesw0rd I tested one of the targets and I am not getting that error :

image

the second one looks like HTB academy, if you can share the module name and assessment name, I can test that as well

@thewhiteh4t
Copy link
Owner

@thesw0rd please share output of :

cd FinalRecon
git rev-parse HEAD

@thesw0rd
Copy link
Author

Second target is from "Information Gathering - Web Edition" module assessment.

hash: ac4681c

@thewhiteh4t
Copy link
Owner

@thesw0rd tested on HTB academy :

image

@thewhiteh4t
Copy link
Owner

@thesw0rd check output of pip show cryptography

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants