Monday, August 25, 2008

Maximum Linux Security (2nd Edition)

Maximum Linux Security: A Hacker’s Guide to Protecting Your Linux Server and Workstation is designed for system administrators, managers, or Linux users who wish to protect their Linux servers and workstations from unauthorized intrusions and other external threats to their systems’ integrity. Written by an experienced hacker–someone who knows which systems are vulnerable and how crackers get into them–this unique guide to Linux security identifies existing and potential security holes and faults, and then describes how to go about fixing them.

As we’ve all become well aware lately, every complex system has flaws. When the complex system is a computer operating system, such as Linux, or a piece of software running under it, those flaws can provide black-hat hackers with the access they need to steal your data, damage your system, or use your computing resources as a base for attacking other computers. Maximum Linux Security reveals securitybook and break into unsecured Linux machines in a variety of ways. The newest edition of this book includes newer information about Linux security exploits and updated links to information and tools. holes in Linux and does so explicitly. You can follow instructions in this

The anonymous author of this book has done a fine job of recognizing that his readers, despite the fact that they’re probably pretty accomplished power users just because they’re messing around with Linux–David Wall, aren’t really experienced with Linux or with computer security. He’s careful to explain his subjects precisely. For example, he goes to considerable effort to explain how to set up user accounts properly (with emphasis on preventing obvious security holes), in addition to documenting offensive and defensive weapons like SAINT and Crack. Most entries on software include URL references to the latest versions, as well as cross-references to related programs.

Topics covered: Good Linux security practice, as well as specific malicious software packages and ways to defend against them.

Print this post

No comments: