Great Circle Associates Firewalls
(October 1997)
 

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

Subject: RE: sex, lies, and firewall code
From: Ryan Russell/SYBASE <Ryan . Russell @ sybase . com>
Date: 20 Oct 97 8:16:43 EDT
To: Rick Murphy <rick @ paimail . com>
Cc: "Craig S. Wright" <craig . wright @ asx . com . au>, "'firewalls @GreatCircle.COM'" <firewalls @ GreatCircle . COM>

I think he may have been talking about the plug-gw,
which (from the descriptions I've heard) is a packet
filter (i.e. allow based on port numbers.)

    Ryan





rick @
 paimail .
 com (Rick Murphy) on 10/19/97 05:01:28 PM
To: craig .
 wright @
 asx .
 com .
 au ("Craig S. Wright") @ smtp
cc: firewalls @
 GreatCircle .
 COM ("'firewalls @
 GreatCircle .
 COM'") @ smtp (bcc: Ryan 
Russell/SYBASE)
Subject: RE: sex, lies, and firewall code

At 12:44 PM 10/19/97 +1000, Craig S. Wright wrote:
> The issues should not be based on proxy vs filter gateways, rather the
> two need to be deployed together (note that TIS uses a packet filter too,
so >both FW-1 and TIS are hybrids).
Gauntlet uses a packet *screen* for enforcing anti-spoofing rules and for
support of transparency. This is not a packet filter. (I'm not arguing
semantics here - a packet FILTER allows packets to forward across the
firewall. The Gauntlet packet SCREEN only denies packets or permits them
to go to proxies.)
 -Rick






Follow-Ups:
Indexed By Date Previous: Re: firewall and virus
From: David Lang <dlang @ diginsite . com>
Next: Re: sex, lies, and firewall code
From: Peter da Silva <peter @ baileynm . com>
Indexed By Thread Previous: Re: sex, lies, and firewall code
From: Bernd Eckenfels <lists @ lina . inka . de>
Next: Re: sex, lies, and firewall code
From: Joe Judge <joej @ ultranet . com>

Google
 
Search Internet Search www.greatcircle.com