You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the socket created for privileged scans checks EVERY packet your computer receives, and returns the one that has a source IP equal to the target (since this should be our target's response). However, when we scan ourselves, the original scan packet matches and is returned, which confuses the scan logic. The simple way to fix this would be to add a check to see if we are scanning ourselves, and if so, return the second packet which matches (the response) instead of the first (the scan).
However, now that I think about this, we should check first if either of the options below makes it so we only get responses back since they would be cleaner.
not setting IP_HDRINCL on the socket (and not crafting the IP header ourselves)
binding our socket to a specific port before we send packets
The text was updated successfully, but these errors were encountered:
Currently, the socket created for privileged scans checks EVERY packet your computer receives, and returns the one that has a source IP equal to the target (since this should be our target's response). However, when we scan ourselves, the original scan packet matches and is returned, which confuses the scan logic. The simple way to fix this would be to add a check to see if we are scanning ourselves, and if so, return the second packet which matches (the response) instead of the first (the scan).
However, now that I think about this, we should check first if either of the options below makes it so we only get responses back since they would be cleaner.
The text was updated successfully, but these errors were encountered: