Why not just disable the TCP/IP stack when it's not in use? As long as the computer doesn't need to be seen over IP while a user isn't at it, that could be done. MacOS up to 9.2 default to TCP/IP enabled when required rather than all of the time. That effectively keeps them hidden on the network when a user isn't using their computer.
Greg on 10/30/01 12:22 PM, John Oliver at [EMAIL PROTECTED] wrote: > A thought just occurred to me... desktop systems (and even some servers) > could be almost completely secure if there was a way to dynamically > allocate and de-allocate routes. If your system has no default route, > it ought to be safe from any TCP-based attack. If routes to remote > networks could be dynamically added as needed, and then removed, it > seems that it would be virtually impossible for an outsider to even see > that the host exists, let alone be able to root it. > > Ideas? Am I just way off the deep end here? :-) -- Greg Francis Sr. System Administrator Gonzaga University [EMAIL PROTECTED] 509-323-6896
