User commands and logs
All these logs and commands are a lot to learn. Fortunately, much of the information they offer is easy to read and understand.
In many cases, too, you only need one or two of these information sources in any given context. For example, if you suspect that an account password has been compromised, probably all you need to do is examine
lastlog for login attempts at a time when the legitimate user was away from the keyboard. Similarly, a corporate administrator might want to use
w to see whether the processes a user is running during office hours include PySol and Battle of Wesnoth.
In other words, it's all about choosing the right tool for the job at hand. Familiarize yourself with these logs and tools in a general way, and you will generally be able to know which tool you should use in any particular circumstance.
Buy this article as PDF
Xen project announces a privilege escalation problem for Qemu host systems
Attackers can compromise an Android phone just by sending a text message
PC vendor will pre-install Ubuntu on portables in India.
More embarrassment for Adobe's embattled multimedia tool
Mozilla’s script blocker add-on could be putting malware sites on the whitelist.
The Internet community officially banishes the notoriously unsafe Secure Sockets Layer protocol.
Popular desktop environment continues the Gnome 2 legacy – with new support for the Gnome 3 toolkit.
The Obama White House has issued a memorandum telling all US government agencies they must use HTTPS for all websites and web communication.
New program will dial up security for the Firefox browser.
Red Hat's community distro embraces the cloud.