|
Posted by Poutnik on April 6, 2008, 3:41 pm
If you were Registered and logged in, you could reply and use other advanced thread options I do not need to learn what the hardware FWs are
and how they are supposed to work.
According to the fact
Comodo is personal software firewall,
I stayed at this topic.
We can debate, if Pers SW FWs are proper term, but it is commonly used.
And modern PSW are much more then plain packet filters.
PF have no more chance against sofisticated malware.
SW FW can be more easily compromized,
but on the other hand, the have more chances
to detect application hijacking
and suspicious interprocess comunication.
This field is closed to distant HW firewalls.
HW and SW FWs have little different goals, purpose and usage.
There is no use for their users fight each other.
They have common enemy.
>
> >
> >>
> >> And Comodo is worse, since it doesn't even allow proper configuration
> >> even
> >> in the most simple scenarios.
> >
> > As I have said, it is on your hands.
> >
> > My comodo works fine even at complex scenarios.
> > But it can be out of your knowledge scope.
>
> Your first mistake is that some 3rd party personal firewall you're even
> calling a FW. It's not a FW at best it's a machine level packet filter and
> some won't even call it that.
>
> A FW separates two networks. A FW sits at the junction point between two
> networks. A FW protects from the network it's protecting from usually the
> Internet, and it protects the network it's protecting the LAN. A FW must
> have two network interfaces or in the case of a FW running on a secured
> gateway computer, the computer must have two NIC(s). One network interface
> must face the WAN/Internet, and the other one must face the LAN.
>
> Because of the FW ability to segment networks, it reduces the risk of damage
> spreading from one network to another network, like a firewall or firedoor.
>
>
|