Vanja Hrustic wrote:
>
> As much as I'm concerned, the answer to "Why not NT?" question is:
>
> In 2 days, I can't find a utility that will tell me who 'owns' the process
> that is keeping port X open. I only got mails from people saying "If you
> find out, let me know!".
>
> And I'm supposed to run firewall on this "thing"!? So, now what I do? Turn
> off everything on the system in order to see if those ports go away? If
> that doesn't work then... reboot? If that still doesn't work - download few
> virus killers to check if maybe some trojan found its way in? And if that's
> not the case - what next?
>
> At least, I know what's on port 80. I hope so...
>
> Vanja
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
This is a really good example of what people have been trying to
explain.
A) We have no easy way to know exactly whats happening in the bowels of
NT. But from all the nasty little bugs of late... I bet its kinda
stinky. (After all, the .htr bug "which was used rarely" expanded pretty
quickly to include other extentions.) If I can't be sure about whats
going on inside my firewall, why should I run it? This topic shouldn't
be "Why Not NT" but "Why NT" Why should I go with a system that is
*more* obscure when I can use one that is *Less* obscure?
B) "With MS you have great support" If this was a BSD or Linux, Vanja
would have had an answer in hours, at worst!
Wake Up!
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
