- Paperback: 544 pages
- Publisher: O'Reilly Media; 2 edition (January 28, 2005)
- Language: English
- ISBN-10: 0596006705
- ISBN-13: 978-0596006709
- Product Dimensions: 7 x 1.1 x 9.2 inches
- Shipping Weight: 1.6 pounds (View shipping rates and policies)
- Average Customer Review: 10 customer reviews
- Amazon Best Sellers Rank: #593,827 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Linux Server Security: Tools & Best Practices for Bastion Hosts 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
About the Author
Michael D. (Mick) Bauer, CISSP, is Network Security Architect for alarge financial services provider. He is also Security Editor forLinux Journal Magazine, and author of its monthly "Paranoid Penguin" security column. Mick's areas of expertise include Linux security and general Unix security, network (TCP/IP) security, security assessment, and the development of security policies and awareness programs.
Browse award-winning titles. See more
Top customer reviews
For instance, for a book that introduces FTP servers, web servers, mail (imap/smtp), dns - they are like separate entities. They do not complete the picture by showing a complete network diagram with IDS / VPN, -- showing an example of all of their advice coming together in a working solution. And Kerberos isn't even mentioned.
They were extremely specific in some areas like talking about rpm example/debian/ make options and specific .conf options ad nauseum - which detracted from the whole picture. Is someone securing bind 4 really reading this book? Also, maybe a mention of apt-get - - but don't tell me how to install each package on every architecture - it just inflates the word count.
I don't think this book was focused enough in the 'big picture' of trying to piece together all of the tiny pieces into a coherant whole, while at the same time it gets cought up in the minute details of certain packages making for a tough read.
Perhaps they could have included an actual example company or two showing possible layouts of ldap in action with:
Anyone for OpenBSD?
First off is the reason I got a copy of this book. (thank god it was used) I am experimenting with options to lock down linux, I wanted to know about, and set up a wide range of technologies to get a good feeling for how much security linux can provide.
I was quite happy to see a section covering how to be a small time CA. (found at the beginning of the stunnel section) This section is so bad, it doesn't even use the right options to say sign a cert from a different server. That is right a book I paid money for didn't even bother to look up the correct options to sign a cert, to be a small time CA? The kerberos section was ok, but it reads like a hobbyist wrote the chapter, and not an experienced admin. I found myself taking notes to follow along, just to redo the instructions to fit my own needs. Lastly ldap. This chapter is simply so awful it inspired me to write this review. I was testing the chapters of this book against the current Debian stable. The only thing this book is good for, is to let you know what other books you should buy instead. I just placed orders for dedicated books, on the chapters from this book I was interested in learning more about.
To recap: The instructions are wrong, the book is inconsistent. I am ashamed o'reilly let this book pass as they have some of the best books.
By Michael D. Bauer
Second Edition January 2005
544 pages, $44.95 US
This book goes along with the moving trend of the normal computer user, securing your data. Servers generally are targeted more often than the average home PC because most are made to be accessible from the outside world. This is where securing that server comes into play. This book covers the tools and techniques to securing your Bastion host.
First I'd like to start out and explain what Bastion host means as according this book so you can understand what this book covers more specifically. Bastion Host is defined as "A system that runs publicly accessible services but is usually not itself a firewall. Bastion hosts are what we put on DMZ (although they can be put anywhere). The term implies that a certain amount of system hardening has been done, but sadly, this is not always the case."
After you understand what a Bastion host is defined as, you should understand that this book mainly covers these server daemons and the systems that run them. But some of the information applies to a Linux desktop system such as a per host iptables firewall, using secure shell, keeping up with your logs, and intrusion detection. Most of these things the average user doesn't care much about but sometimes being paranoid comes in handy.
Someone who would most likely use this book more than the average desktop user would probaly be a system administrator. Securing web, database, ftp, dns, and email servers is what majority of this book contains. Along with covering these server systems, there are guides to securing the Linux system that runs these daemons along with designing the networks around these types of hosts.
One of the sections I'm most fond of is Chapter 2: Designing Perimeter Networks. With this section you can really take a look at the design and layout of the different types of networks and figure out the portions that suit your needs for your own network. The diagrams shown in this chapter help explain what is going on with the traffic and allows you to see exactly what is going on and at what points the systems are protected.
At the end of the book there are 2 well commented iptables firewall scripted that allow you to get a feel for the netfilter iptables system if you're not familiar with it already. With some modification of these scripts you can easily bring them into a working environment depending on your situation, which sometimes these helps with some of the frustration with the iptables syntax. I personally prefer the PF system within OpenBSD for it's clean syntax and have grown away from iptables, but both are powerful firewall systems and should fit the needs of your network.
I'd definitely recommend this book to system admins or anyone who is paranoid about their security. Security is always something that people should be educated about.
Pensacola Linux User's Group
Most recent customer reviews
A lot of people think Linux is bullet proof, but its not.Read more