Great Circle Associates Firewalls
(January 1995)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Router filtering not enough! (Was: Re: CERT advisory )
From: Rens Troost <rens @ imsi . com>
Date: Tue, 24 Jan 1995 15:21:25 -0500
To: ddrew @ mci . net, firewalls @ greatcircle . com, bugtraq @ fc . net, z056716 @ uprc . com
Cc: rens @ lorax . imsi . com
In-reply-to: Your message of "Tue, 24 Jan 1995 11:17:48 EST." <9501241617 . AA07921 @ lorax . imsi . com>
Reply-to: rens @ imsi . com

>>>>> "Rens" == Rens Troost <rens @
 imsi .
 com> writes:

  Rens> This can be done with a routing redirect attack anywhere on
  Rens> the path between the telnet client and the skey login machine
  Rens> (firewall), and does not require IP spoofing.

What I meant was, does not require that it spoofing that can be
detected by router filters. It does require spoofing that the packets
are coming from the machine that originated the valid connection; let
my fingers get ahead of me. 

-Rens



References:
Indexed By Date Previous: Re: CERT advisory
From: Christian Wettergren <cwe @ it . kth . se>
Next: Re: Router filtering not enough! (Was: Re: CERT advisory )
From: Christian Wettergren <cwe @ it . kth . se>
Indexed By Thread Previous: Router filtering not enough! (Was: Re: CERT advisory )
From: Rens Troost <rens @ imsi . com>
Next: Re: Router filtering not enough! (Was: Re: CERT advisory )
From: Christian Wettergren <cwe @ it . kth . se>

Google
 
Search Internet Search www.greatcircle.com