Book Image

WordPress 3 Ultimate Security

Book Image

WordPress 3 Ultimate Security

Overview of this book

Most likely – today – some hacker tried to crack your WordPress site, its data and content – maybe once but, with automated tools, very likely dozens or hundreds of times. There's no silver bullet but if you want to cut the odds of a successful attack from practically inevitable to practically zero, read this book. WordPress 3 Ultimate Security shows you how to hack your site before someone else does. You'll uncover its weaknesses before sealing them off, securing your content and your day-to-day local-to-remote editorial process. This is more than some "10 Tips ..." guide. It's ultimate protection – because that's what you need. Survey your network, using the insight from this book to scan for and seal the holes before galvanizing the network with a rack of cool tools. Solid! The WordPress platform is only as safe as the weakest network link, administrator discipline, and your security knowledge. We'll cover the bases, underpinning your working process from any location, containing content, locking down the platform, your web files, the database, and the server. With that done, your ongoing security is infinitely more manageable. Covering deep-set security yet enjoyable to read, WordPress 3 Ultimate Security will multiply your understanding and fortify your site.
Table of Contents (23 chapters)
WordPress 3 Ultimate Security
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Hardening wp-content and wp-includes


Again using htaccess, we'd best restrict access to content from the remaining core WordPress directories, wp-content and wp-includes.

Create an htaccess file in each folder, pasting this rule within:

Order Allow,Deny
Deny from all
<Files ~ "\.(gif|jpe?g|png|css|js|xml)$">
Allow from all
</Files>

That allows access to images, javascripts, stylesheets, and XML, denying everything else. Sometimes, though, this is too restrictive so let's consider some workarounds.

Extra rules for wp-include's htaccess

Let's say you use the Dashboard's flash uploader. You would need also to accept swf files, adding that extension to the <Files etc> directive like this:

<Files ~ "\.(gif|jpe?g|png|css|js|xml|swf)$">

Or if you have issues with an included plugin, say the Tiny WYSIWYG editor, add a further rule to the file:

<Files ~ "js/tinymce/*.$">
Allow from all
</Files>

Extra rules for wp-content's htaccess

In this file, you can counter any problems...