I think it depends... I know for sure that ettercap (on linux) can
hijack a tcp connection and inject whatever data the intruder wants
(it's child's play for instance to hijack a telnet to a router and send
back to the operator fake answers from the router)...
But in order to do that it has to
Yes,
google TCP session hijacking.
The possibilities are limited by your access to the network path between the endpoints.
If you have share a LAN with one of the endpoints you can poison the ARP cache of the
endpoint and insert a MAC-layer proxy, if you can tap the ONLY link between routers,
Gene LeDuc wrote:
Sorry to be blunt, but someone who doesn't understand the difference between
UDP and TCP should not even consider setting firewall rules. You need to
buy a decent beginners level book on networking that covers tcp/ip
fundamentals.
-Original Message-
From: Roberto
i believe you are asking if it is possible to hijack a TCP session. is
this correct? absolutely it is possible, it is just a matter of spoofing
the mechanics for maintaining the session, the syn/ack numbers.
rant
let it be a lesson to you. using a non security feature to provide you
with
Dear list:
It's possible that a intruder could take active part of a TCP
connection after this was established?
In UPD I know this is true because is a connectionless
protocol. But I have doubts about TCP.
Depending on the location of the attacker this would indeed be possible.
He/She's
In-Reply-To: [EMAIL PROTECTED]
Hi,
It depends totally on the application you are using. Both TCP and UDP are
IP protocol types, and there are others like IP proto 47 (used by PPTP)
etc. which you would need to open in case the application needs it. As
always, do not open any additional
-Original Message-
From: Roberto Ramsis [mailto:robertoramsis;hotmail.com]
Sent: Monday, November 11, 2002 5:59 PM
To: [EMAIL PROTECTED]
Subject: RE: TCP vs UDP
hello
thanks for everyone who replied to my msg.
but as for that part:
Sorry to be blunt, but someone who doesn't understand
Sorry to be blunt, but someone who doesn't understand the difference between
UDP and TCP should not even consider setting firewall rules. You need to
buy a decent beginners level book on networking that covers tcp/ip
fundamentals.
-Original Message-
From: Roberto Ramsis
hello
thanks for everyone who replied to my msg.
but as for that part:
Sorry to be blunt, but someone who doesn't understand the difference
between
UDP and TCP should not even consider setting firewall rules. You need to
buy a decent beginners level book on networking that covers tcp/ip
Although i'm not an expert i would say it depends on the port... Say for
example that we're talking about a DNS server... surely you'll leave
open the UDP port 53 so that i will answer to clients but you won't open
TCP 53 as well unless you want to allow everybody to perform zone
transfers...
10 matches
Mail list logo
