Article View: comp.dcom.sys.cisco
Article #2260Re: IOS exploit: please disclose vehicle, not mechanism
From: Walter Roberson
Date: Fri, 25 Jul 2003 04:36
Date: Fri, 25 Jul 2003 04:36
33 lines
2891 bytes
2891 bytes
In article <Xns93C2CB80F3AF9wdjohnstoncomcastnet@206.127.4.25>, Bill Johnston <wdj-netconsult@consultant.com> wrote: :My ignorance on the meaning of the number in router ACLs :could stem from the fact that I spent more time diddling :my clients' PIX boxes, on which port blocking and port :redirection (PAT) is a major concern. To be sure, this :use of port numbers typically occurs in the "conduit" :command lines, but those are ones that often get the :most work and rework as a new firewall is set up. I would interpret that paragraph as indicating that you do not do any IPSec work, and that you are working primarily on old PIX boxes -- probably PIX 4.2 boxes that haven't been upgraded much past 5.2. If you were working with IPSec, then you would very likely have run into issues of getting IPSec working through a filter or firewall, which would have led you to references to AH, ESP, or GRE, and you would likely have encountered the numeric protocol specification syntax. If you were working with newer PIXes from scratch or PIXes that were being kept up to date into the 6.x era, you would be using ACLs instead of conduits. Also, 6.x especially tends to work with port names instead of port numbers [but accepts numbers still]. My inference would be that your PIX skills are not really up to date. If you can afford it, I would suggest that you invest in a PIX 501 for learning purposes. [Someone suggested recently that the 501E will be out soon; I don't know anything about that.] -- Look out, there are llamas!
Technical Details
Message-ID:
<bfqc44$60n$1@canopus.cc.umanitoba.ca>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!torn!canopus.cc.umanitoba.ca!not-for-mailReferences:
<Xns93C1BACF3C55Awdjohnstoncomcastnet@206.127.4.25> <Xns93C294B29ED49wdjohnstoncomcastnet@206.127.4.25> <vi0eseqe4p8sc3@corp.supernews.com> <Xns93C2CB80F3AF9wdjohnstoncomcastnet@206.127.4.25>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f922c,536b22101f44acbf X-Google-Attributes: gidf922c,public X-Google-Thread: 114395,536b22101f44acbf X-Google-Attributes: gid114395,public X-Google-Thread: 102702,536b22101f44acbf X-Google-Attributes: gid102702,public X-Google-ArrivalTime: 2003-07-24 21:36:20 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!torn!canopus.cc.umanitoba.ca!not-for-mail From: roberson@ibd.nrc-cnrc.gc.ca (Walter Roberson) Newsgroups: comp.dcom.sys.cisco,ios.general,comp.security.firewalls Subject: Re: IOS exploit: please disclose vehicle, not mechanism Date: 25 Jul 2003 04:36:20 GMT Organization: National Research Council Canada - Conseil national de rechereches Canada Lines: 33 Message-ID: <bfqc44$60n$1@canopus.cc.umanitoba.ca> References: <Xns93C1BACF3C55Awdjohnstoncomcastnet@206.127.4.25> <Xns93C294B29ED49wdjohnstoncomcastnet@206.127.4.25> <vi0eseqe4p8sc3@corp.supernews.com> <Xns93C2CB80F3AF9wdjohnstoncomcastnet@206.127.4.25> NNTP-Posting-Host: zeno.ibd.nrc-cnrc.gc.ca X-Trace: canopus.cc.umanitoba.ca 1059107780 6167 192.70.172.132 (25 Jul 2003 04:36:20 GMT) X-Complaints-To: Postmaster@cc.umanitoba.ca NNTP-Posting-Date: 25 Jul 2003 04:36:20 GMT Originator: roberson@ibd.nrc-cnrc.gc.ca (Walter Roberson)