There seem to be two kinds of people in the world: those who think computer
security is fun and exciting, and those who think it is arcane and scary.
Professional system administrators who read their logs will tell you computer
security is actually long periods of boredom punctuated by intervals of
sleeplessness, panic, and frantic activity.
For months, you read logs that basically consist of the same sequence of
messages. Then one morning, you see a different message. Your first thought
tends to be "I've been hit!" You want to determine whether the attack was
successful. You comb through logs and examine files on your systems, looking
for signs of abnormal behavior. There are none; maybe the attack has failed.
But perhaps the attacker was smarter than you. For days or weeks you remain
unsure if your system's defenses were penetrated. Eventually, you forget
about it... (more)
Because Linux is a deep operating system, we often use a miniscule portion of
a tool's features. I, for one, use awk primarily to isolate columns that cut
can't find, though in fact awk is a full-fledged text-processing language.
There's nothing wrong with that approach -- in fact, it's unavoidable -- but
it benefits us to delve more deeply into the advantages a single program can
offer.
Presumably you have already installed SSH and use it to securely log in to
remote systems. (If you don't please read Jay Beale's article "Stupid, Stupid
Protocols: Telnet, FTP, rsh/rcp/rlogin" to... (more)