Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Firewalls
[Top] [All Lists]

RE: PIX limitations

Subject: RE: PIX limitations
Date: Mon, 16 Aug 2004 16:28:27 -0700
Thanks Brian, 

Do you know/can you tell when PIX 7.0/FWSM 3.0 are expected to come out? It
was posted on this list that the code trains will be merged at that point. 

Jonathan

-----Original Message-----
From: Brian Ford [mailto:brford@cisco.com] 
Sent: Wednesday, August 11, 2004 9:01 PM
To: jlebowitsch@pacbell.net
Cc: firewalls@securityfocus.com
Subject: Re: PIX limitations

J,

You need to check these details against the PIX OS manual for the version of
code you are using.  FWSM was based on PIX OS v6.0 and details like these
may have diverged between the FWSM and the PIX appliance OS versions.

Liberty for All,

Brian

At 06:18 PM 8/6/2004 +0000, jlebowitsch@pacbell.net wrote:


Hi all,

The manual for Cisco's new FWSM says

"State information for multimedia sessions that require inspection are 
not passed over the state link for stateful failover.

For fragmented IP packets, only the first fragment is inspected.

For segmented TCP packets, if messages are divided between segments, 
the FWSM cannot inspect the packets."

Does anyone knows if this is true also of Cisco PIX? As FWSM is based 
on PIX it seems likely, but i can't find documentation for this.


Brian Ford
Consulting Engineer, Security & Integrity Specialist Office of Strategic
Technology Planning Cisco Systems Inc.
http://www.cisco.com/go/safe/

The opinions expressed in this message are those of the author and not
necessarily those of Cisco Systems, Inc..

This email address is transmitted from San Jose, California, U.S.A..



<Prev in Thread] Current Thread [Next in Thread>