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

PHP's .ini mini guide


Tightening PHP revolves largely around its configuration file, php.ini.

Locating your configuration options

Even with some shared hosts there's quite a lot you can do to tighten up your PHP installation. In cPanel, for example, you can investigate your options by choosing the main menu's php.ini QuickConfig icon and selecting Enable QuickConfig.

Note

WordPress 3.2 drops support for PHP versions below 5.2, so nag your web host.

For unmanaged types, open your php.ini file with a terminal. The path may vary, but can be located with sudo find / -name php.ini -print or, if there's more than one file, add a temporary page with <?php phpinfo();?> inside, browse there, and look for this:

That done, delete the file before someone else looks too. And open the .ini:

sudo nano /etc/php5/apache2/php.ini

Making .ini a meany

Here are the key security variables. Some defaults are the same as the recommended setting but check, they may have been changed. Variable's proceeded by ;semi-colons...