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

Support connecting to host via proxy #21

Closed
stuarthicks opened this issue Dec 12, 2014 · 5 comments
Closed

Support connecting to host via proxy #21

stuarthicks opened this issue Dec 12, 2014 · 5 comments

Comments

@stuarthicks
Copy link

Attempting to scan a host while being behind a corporate proxy leads to this error:

WARNING: Could not connect (timeout); discarding corresponding tasks.

All usual proxy environment variables are set, and other python scripts on my system work through the proxy, so I'm hoping this isn't too tricky to achieve. Will have a dig through the source later myself and see if I can work out what's required.

@nabla-c0d3
Copy link
Owner

Hi,
I will need more details... it might be that the many connections opened by sslyze killed the proxy.

@stuarthicks
Copy link
Author

Ok, what details would you like? Is there a recommended way to debug sslyze to see exactly what connections are failing?

@nabla-c0d3
Copy link
Owner

Actually SSLyze does not honor environment variables for proxy configuration. You will have to use the --https_tunnel option (see --help for more details).

@nabla-c0d3
Copy link
Owner

Feel free to re-open this if --https_tunnel didn't address your problem.

@stuarthicks
Copy link
Author

Huh. Ok, didn't spot that option, works perfectly when I add --https_tunnel=$https_proxy. Out of curiosity, what's the reason for not using the environment variables?

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

No branches or pull requests

2 participants