-
Notifications
You must be signed in to change notification settings - Fork 795
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
ldap and dnsrecon error #48
Comments
I am aware of the dbsrecon error, and I'll work on fixing it. Thanks for bringing up the ldap issue, perhaps there's an issue with regex, so I'll work on fixing it as well. |
I face another issues with sslscan, it only work on port 443, if another port is running on ssl, it won't specify the port thus making the scan failed. |
It should detect regardless of the port number. |
Ok so this seems like an issue with the dnsrecon command. Thanks for reporting it, and I'll fix the command in the next commit. The second one can be easily fixed. Are you somehow using a proxy? |
Is it possible to add in option to disable ffuf/gobuster or nikto when the sV scan return Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)? |
dnsrecon is not running due to the missing -d switch
It is running ldap search when 3389 is open even port 389 is not
The text was updated successfully, but these errors were encountered: