Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
WordPress 3 Ultimate Security

You're reading from   WordPress 3 Ultimate Security WordPress is for everyone and so is this brilliant book on making your site impenetrable to hackers. This jargon-lite guide covers everything from stopping content scrapers to understanding disaster recovery.

Arrow left icon
Product type Paperback
Published in Jun 2011
Publisher Packt
ISBN-13 9781849512107
Length 408 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Toc

Table of Contents (23) Chapters Close

WordPress 3 Ultimate Security
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
So What's the Risk? Hack or Be Hacked FREE CHAPTER Securing the Local Box Surf Safe Login Lock-Down 10 Must-Do WordPress Tasks Galvanizing WordPress Containing Content Serving Up Security Solidifying Unmanaged Defense in Depth Plugins for Paranoia Don't Panic! Disaster Recovery Security Policy Essential Reference Index

Gatekeeping with TCP wrappers


TCP wrappers are a tidy tool helping to secure network services sitting on open ports where just anyone can try to hack in.

What they do is restrict access to localhost, specific hostnames, or IP addresses and are commonly used, for example, for FTP and POP. They're no substitute for a firewall but, instead, secure ports, generally used for administration that, otherwise, are open to all.

Take the example of SSH which we use to tunnel into the server. Ideally you would set up authentication keys to secure the port but, sometimes, that's not practicable.

Adding a simple directive to a couple of files, the TCP wrapper takes immediate effect.

Open up the deny file:

sudo nano /etc/hosts.deny

Add a line:

Open up the allow file:

sudo nano /etc/hosts.allow

Add a line:

Following the colon in the allow file is the IP to be authorized. You can add a series of IPs, comma or space-separated, else use an IP subnet or hostnames.

Before the colon is the name of the daemon for which to...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image