Re: Q: How do stealth ports manage to accept a connection?
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.security.firewalls archive

Re: Q: How do stealth ports manage to accept a connection?

From: Volker Birk <bumens@dingens.org>
Date: Tue Jan 31 2006 - 15:40:40 CET

Entropy1024 <Entropy1024@gmail.com> wrote:
> Can you explain your "Stealth port" is just advertizing nonsense
> comment more please.

Please read RFC 792. "Stealth ports" are just misunderstanding protocols.
If there is no machine behind a router, you're getting a message - ICMP
host unreachable or ICMP network unreachable. If there is a host, you're
getting a message, too - ICMP port unreachable or TCP RST. If you're
getting no message, then there is a host with a b0rken "Personal Firewall"
and "stealthing" nonsense, or a b0rken network provider.

> Is my explenation of the three way handshake incorrect?

As an approximation. If you want to know, how a TCP handshake works
exactly, and what the different possibilities for that are, you could
read RFC 793.

Yours,
VB.

-- 
Netzwerkgrundlagen anhand Windows lernen zu wollen ist doch wie seine
ersten sexuellen Erfahrungen mit einer Prostituierten zu sammlen: Die
Leidenschaft fehlt, das wirklich Wichtige lernt man dabei nicht, und die
Chance sich einen Schädling einzufangen ist hoch. (Lukas Graf in d.c.s.m)
Received on Tue Feb 7 20:58:29 2006