Firewall Folks,
At 05:43 PM 5/23/2001 +0000, Enno Rey was heard to say:
>Date: Wed, 23 May 2001 16:31:10 +0200
>From: "Enno Rey" <[EMAIL PROTECTED]>
>Subject: RE: Differences between Cisco PIX and Nokia / Check Point
>
>Hi,
>
> > IOS". It is an independent OS written specifically for the PIX and
> > security.
>
>You mean, the PIX's OS was designed from the scratch?
Many, many moons ago the PIX OS was developed from the source of an
embedded computer OS. For all intents and purposes it was pretty much from
scratch as the embedded OS no longer exists except in the PIX OS.
>Without any input from
>anything? Then they got pretty good developers at XYZ [the company the PIX
>was originally designed by, before Cisco bought them]...
Yes. They were and continue to be a pretty smart group of folks.
><snip>
>is the PIX's OS based on BSD [that's what I assume... my 2 cents...] or
>based on XYZ [put in OS of your choice] ... or something completely
>different ... or something created by mossad or...
>I'm too lazy to search the archives right now...
No. Having seen the source code I can say that the PIX OS is not based on:
BSD,
any *nix,
any Microsoft OS,
DRDOS,
XYZ, or
anything created by any agency of any international government.
><snip>
>So why do you think there's a move towards IOS style access-lists in newer
>versions of the PIX?
Amazingly, because folks who regularly buy Cisco equipment including PIXen
asked us to do this.
>Cisco would not act economically reasonable if they didn't harmonize
>'classic IOS' and PIX OS.[any comments on this from somebody @ cisco ?]
I don't know about harmonizing. I know I ask the developers to do it cause
customers ask me for it all the time.
Why do people on the list care what OS (or if an OS) is under the PIX? If
you used the PIX, you'd know that if there were something underneath you
don't have access to it?
> > My two cents.
>
>And mine...
With mine we are up to $0.06.
Regards from Shanghai China,
Brian
>Enno Rey
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
