Re: NAT is not a mechanism for securing a network.. but.. HELP!
From: Leythos (void_at_nowhere.lan)
Date: 08/26/05
- Next message: Doug Fox: "Firewalk 5.0"
- Previous message: Doug Fox: "Re: hping and firewall testing"
- In reply to:(deleted message) CyberDroog: "Re: NAT is not a mechanism for securing a network.. but.. HELP!"
- Next in thread: CyberDroog: "Re: NAT is not a mechanism for securing a network.. but.. HELP!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 26 Aug 2005 20:52:54 GMT
In article <cssug1tg85b854jg9uv74undtnl56df7cg@news.easynews.com>,
CyberDroog@ClockworkOrange.com says...
> What is the difference if the S&M types (heh) get away with it? As far as
> the home user in concerned, a NAT router is *their* firewall. It restricts
> access somewhat.
>
> By your, and Duane's, strict definition of a firewall, a home user is
> rarely going to have one.
And why is that a bad thing - the only reason they call them Firewalls
is to that ignorant people will purchase them. In the days when they
first came out they called them CABLE/DSL ROUTERS, then, without any
change in the firmware or functions, about 6 months later, they started
packaging them as "Firewalls".... See the history here.... Poeple will
buy it if you sell it as some BUZZ word they think they need.
Don't get me wrong, I recommend NAT Routers to ALL home users with DSL
or Cable, and I was installing "LAN MODEMS" long before there ever was
DSL or CABLE service - LAN Modems are single unit boxes with a NAT
router and a modem and a 1 or more port HUB - 3COM use to make them and
they did great to protect Dial-Up users from inbound (as do the
Cable/DSL routers), but they were not and are not firewalls.
> Note, I do see your point and understand why you want a strict definition.
> So now maybe you see my point in not thinking it's all that important. For
> the good of the net, at least many home users are using *something*.
You seem to think I want a "stricter" definition when in reality, until
those lamers started calling NAT devices firewalls, it was always
understood that NAT does not make a device a firewall. It's those
supporters of NAT being a firewall that are "watering down" the
definition of what a Firewall is.
The real problem is that people think these devices ARE firewalls and
that they are getting the same protection that their company firewall
give them - even though they have no idea what kind of protection that
is.
If you don't object to a Yugo being called a Space Shuttle I can see why
you don't object to a NAT Router being called a Firewall.
-- spam999free@rrohio.com remove 999 in order to email me
- Next message: Doug Fox: "Firewalk 5.0"
- Previous message: Doug Fox: "Re: hping and firewall testing"
- In reply to:(deleted message) CyberDroog: "Re: NAT is not a mechanism for securing a network.. but.. HELP!"
- Next in thread: CyberDroog: "Re: NAT is not a mechanism for securing a network.. but.. HELP!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|