] "John Wiltshire" <[EMAIL PROTECTED]>
] > From: Paul D. Robertson <[EMAIL PROTECTED]>
] > Second: Baggage/Design. You can't pare that sucker down to essential
] > services and code. Worse yet, most of what you'd worry about isn't
] > documented well enough to help in an attempt. There's also a great deal
] > of non-IP networking baggage, and perhaps some IP networking baggage
] > that
] > doesn't seem to have an off button. In fact, lack of off buttons is a
] > big thing overall. Sometimes the off buttons are undocumented registry
] > settings - what a joy that is to replicate!
]
] Such as? I can pare down my NT machines to exactly the processes and services I
]want running. Why not run the network
] control panel and remove everything you don't want? Look at the services control
]panel and the "Stop" button. Looks
] like a great big off switch to me.
There is a very big difference between turning a service OFF, and removing
the service from the system. Which is the point Paul was making. If the
service can be turned off, then it can be turned on again easily. If it is
removed completely from the system, then it has to be installed (to be [ab]used).
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
