Yes, this is why, when stealth scanning, you simply send a RST packet. If the port is open, a RST packet is received from the victim. If it is open, SYNACK is received from the victim. If SYNACK is received, it means it is open, but the point isn't to open a connection, so a RST packet is sent back.bad_brain wrote:which connection? there is none until the client replies with an ACK to the SYN-ACK. the RST simply resets the state of the service waiting for the ACK by the client (like "um, nvm"), and only a few port scanners are that friendly.The port scanner has all the information it needs once it gets a SYN-ACK, there's no need to keep the connection after that, so a RST is sent.
There is no point in knowing everything by heart. Trying to do so is a waste of time, as there are so many details that are only useful in certain, very specific situations(Such as the TCP header flags). When you need such things, you will remember enough about them to know you need to check them out, and that's why you have a reference.DNR wrote:To increase the learning potential of this game, try to write from your own knowledge and not from wikipedia please. The scanner host will NOT send a RST packet. Your quote above, is copied from wikipedia - is wrong, because wikipedia was wrong!
Type inference has nothing to do with polymorphism. That might not be what you're trying to say, but that's what it looks like.leetnigga wrote:gogeta70, that was indeed pretty much it. It's important though that this is not the same as weak typing like in PHP. Everything is still completely statically typed, so once variable a is inferred to be an integer, you can't use it again as a string. It's not that the types aren't there, it's that they're implicit Good answer.
Type inference is simply deducting what type a certain variable or literal/constant is, without it being specified explicitly. An example would be the way haskell infers types of functions if you leave out the type signatures.
Anyway, this had been answered, so I'll leave it at that.
