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

Restrict OS detection in more cases with --osscan-limit #1735

Open
dmiller-nmap opened this issue Sep 10, 2019 · 0 comments

Comments

@dmiller-nmap
Copy link

commented Sep 10, 2019

The --osscan-limit option causes OS detection to be skipped if the target does not have at least 1 open and 1 closed TCP port available for testing. There are other cases where a scan could return unreliable results, so we should consider abandoning the scan in those cases as well if the user chooses --osscan-limit.

The one case I am mostly concerned with is when there is no response to any of the SEQ tests (see code surrounding warning message "is this port really open?" in osscan2.cc). There could be other cases that I am not thinking of, though.

Related: #223

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.