Being Prepared for Intrusion
By Dan Farmer and Wietse Venema
, April 01, 2001
As every good programmer knows, software will eventually fail—no matter how well it is written. The same applies to systems, networks, and security mechanisms; and a system that is prepared for failure has safety nets in various places.
Apr01: Being Prepared for Intrusion
telnet> open research.att.com
Trying...
Connected to research.att.com.
Escape character is '^]'.
RISC/os (inet)
login: 123
Last login: Sun Feb 3 15:27:19 from research.att.com
RISC/os (UMIPS) 4.0 inet
Copyright 1986, MIPS Computer Systems
All Rights Reserved
This is inet. Authorized use only.
Recent disk problems have caused some file corruption and we
have reloaded a number of files. This seems to have solved
the problem.
We are still recovering stuff, so let us know if something is
missing.
$ w
w: check_kernel_id; mismatch between kernel file and memory; error= 2
$ who
who: not found
Figure 3: First entrance by "Berferd" into the Bell Labs firewall, as recorded at Stanford University.
