User commands and logs
The log with the name
auth.log records authorizations – that is, logons and logoffs on a system since the last time the system was booted (Figure 4). This information can be invaluable in checking patterns of usage and detecting any departures from the norm. Only the root user can view it.
user.log records the logins and logouts for the entire system, as well as any warnings that might indicate potential problems (Figure 5). In other words, this log is often a convenient point for troubleshooting general problems. As you might expect, only root can read this log.
Most commands have two types of options: Unix-like ones that are preceded by a single hyphen and are typically a single letter, and GNU options that are preceded by two hyphens and are usually a complete phrase that describes what they do. You can tell how old many of the user-related commands are by the fact that several of them have no GNU options whatsoever. In other words, when you are administering users, you are really getting down to the foundations of your operating system.
Buy this article as PDF
HP's annual Cyber Risk report offers a bleak look at the state of IT.
But what do the big numbers really mean?
.NET Core execution engine is the basis for cross-platform .NET implementations.
The Xnote trojan hides itself on the target system and will launch a variety of attacks on command.
Spammers go low-volume, and 90% of IE browsers are unpatched.
Adobe scrambles to release patches for vulnerable Flash Player.
Four-inch-long computer on a stick lets you boot a full Linux system from any HDMI display device.
New statute would require companies to report break-ins to consumers.
Weird data transfer technique avoids all standard security measures.
FIDO alliance declares the beginning of the end for old-style login authentication.