WordPress - Revision history

Johnno: /* Cache all the things */

2021-10-11T21:53:19Z

Cache all the things

Johnno: /* Use a content security policy */

2021-10-11T20:41:35Z

Use a content security policy

Johnno: /* Use SSL everywhere */

2021-10-11T20:40:30Z

Use SSL everywhere

Johnno at 20:39, 11 October 2021

2021-10-11T20:39:42Z

Johnno: /* Use SSL */

2021-10-11T20:01:51Z

Use SSL

Johnno: /* Cache all the things */

2021-10-11T19:56:17Z

Cache all the things

Johnno: /* Optimise PHP */

2021-10-11T19:32:53Z

Optimise PHP

Johnno at 09:01, 20 August 2021

2021-08-20T09:01:03Z

Johnno at 05:21, 20 August 2021

2021-08-20T05:21:03Z

Johnno: /* Allow user-installed plugin and themes */

2021-08-20T05:06:48Z

Allow user-installed plugin and themes

← Older revision		Revision as of 21:53, 11 October 2021
Line 12:		Line 12:

	Second, install a Redis server, and get the [https://wordpress.org/plugins/wp-redis/#installation WP-Redis] plugin and follow its installation instructions. This hugely reduces load times by caching PHP object data and reducing calls to the database.		Second, install a Redis server, and get the [https://wordpress.org/plugins/wp-redis/#installation WP-Redis] plugin and follow its installation instructions. This hugely reduces load times by caching PHP object data and reducing calls to the database.
		+	apt get install redis-server

	Also, configure Apache to gzip all the static assets and use a long cache expiry time.		Also, configure Apache to gzip all the static assets and use a long cache expiry time.

@@ Line 50: / Line 50: @@
 Use a content security policy to reduce or even eliminate several methods of attack. There is a plugin for managing one from within WordPress, but it is straightforward to cobble one and add it to the headers. Here's an example content security policy that allows JavaScript, images and CSS from only certain origins, and denies everything else:
   Header always set Content-Security-Policy <nowiki>"base-uri 'self';
       default-src 'none'; media-src 'self';

@@ Line 44: / Line 44: @@
 === Use SSL everywhere ===
-Use [[Letsencrypt]] to get free SSL certificates, and enforce it everywhere using HTTP redirection to HTTPS. This is probably the most important thing you can do to increase the attack difficulty of your site. Use dehydrated to automatically renew the SSL certificate, and grab the latest [[https://ssl-config.mozilla.org/ Mozilla SSL Guideline] to set up strong SSL.
+Use [[Letsencrypt]] to get free SSL certificates, and enforce it everywhere using HTTP redirection to HTTPS. This is probably the most important thing you can do to increase the attack difficulty of your site. Use dehydrated to automatically renew the SSL certificate, and grab the latest [https://ssl-config.mozilla.org/ Mozilla SSL Guideline] to set up strong SSL.
 === Use a content security policy ===

@@ Line 26: / Line 26: @@
 It is however useful as a temporary measure when starting out, and once the website is nearing a stable production-ready state, you can audit it all, and switch back to maintaining the selection of themes and plugins separately (e.g. in git, using submodules, or using wp-cli on the server) and disallowing user installs.
-== WP CLI ==
+== Command line tool ==
 Use [https://wp-cli.org wp-cli], a really useful tool for managing WordPress sites from the command line. Once downloaded you can keep it updated with:
@@ Line 32: / Line 32: @@
   wp cli update
-== Use SSL ==
+Manage users, pages, posts and so on. Plugins and themes can be installed, enabled or disabled, removed, and kept up to date:
-Use [[Letsencrypt]] to enforce HTTPS everywhere and reduce the attack surface of your site. Use dehydrated to maintain the SSL certificate, and the latest [[https://ssl-config.mozilla.org/ Mozilla SSL Guideline] to set up strong SSL.
+ wp plugin install wp-super-cache wp-redis
-== Content security ==
+== Security hardening ==
-Use a content security policy. There is a plugin for managing one from within WordPress, but it is straightforward to cobble one and add it to the headers. Here's an example content security policy that allows JavaScript, images and CSS from only certain origins, and denies everything else:
+Treat the internet like it is: an invading horde of zombie bots, script kiddies, crypto miners and identity thieves swarming outside relentlessly trying to break into your site.
   Header always set Content-Security-Policy <nowiki>"base-uri 'self';
@@ Line 59: / Line 69: @@
       style-src 'self' 'unsafe-inline' https://*.wp.com https://ajax.googleapis.com
           https://fonts.googleapis.com;"</nowiki>
 Other headers can be used to further enforce some secure behaviour:
@@ Line 67: / Line 79: @@
   Header always set Access-Control-Allow-Origin "*"
-== Some more security hardening ==
+=== Mandate strong user passwords ===
-There's a lot of written material out there. but for a start, as suggested by [https://wpscan.com/wordpress-security-scanner WPScan], prevent DDoS attacks on web-accessible cron and XMLRPC endpoints, but allow CLI invocation, and prevent execution of uploaded PHP content:
+Consider installing a password policy plugin, such as [https://wordpress.org/plugins/password-policy-manager/ this one] from [https://www.miniorange.com/ Mini Orange].
   <Files "xmlrpc.php">
       Require ip 127
   </Files>
   <Files "wp-cron.php">
       Require ip 127
   </Files>
   RedirectMatch 404 "/readme\.html"
 == Do you need an online shop? ==

@@ Line 34: / Line 34: @@
 == Use SSL ==
-Use [[Letsencrypt]] to enforce HTTPS everywhere and dehydrated to maintain the SSL certificate, and use the latest Mozilla SSL Guideline from their [https://ssl-config.mozilla.org/ configurator] to set up strong SSL.
+Use [[Letsencrypt]] to enforce HTTPS everywhere and reduce the attack surface of your site. Use dehydrated to maintain the SSL certificate, and the latest [[https://ssl-config.mozilla.org/ Mozilla SSL Guideline] to set up strong SSL.
 == Content security ==

@@ Line 7: / Line 7: @@
 == Cache all the things ==
-WordPress is slow. Install and configure [https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] to make it go much faster. Also, configure Apache to gzip all the static assets and use a long cache expiry time.
+WordPress is slow. Fortunately, there are things we can do to make it behave more like a static site, which for 99% of the time, it may as well be.
 == Allow user-installed plugins and themes ==

@@ Line 3: / Line 3: @@
 == Optimise PHP ==
-See the [[PHP]] page.
+Use PHP-FPM and use the Opcache. See the [[PHP]] page.
 == Cache all the things ==

← Older revision		Revision as of 09:01, 20 August 2021
Line 1:		Line 1:
	WordPress is popular, feature-rich and useful, despite the awful spaghetti state of its PHP code. It is also slow, without a bunch of extra help. Luckily we can speed it up and lock it all down pretty well as follows.		WordPress is popular, feature-rich and useful, despite the awful spaghetti state of its PHP code. It is also slow, without a bunch of extra help. Luckily we can speed it up and lock it all down pretty well as follows.
		+
		+	== Optimise PHP ==
		+
		+	See the [[PHP]] page.

	== Cache all the things ==		== Cache all the things ==

← Older revision		Revision as of 05:21, 20 August 2021
Line 86:		Line 86:
	I have certainly found it sufficiently useful for a small non-profit selling merchandise, a community orchestra selling tickets, or a home business flogging chilli sauce.		I have certainly found it sufficiently useful for a small non-profit selling merchandise, a community orchestra selling tickets, or a home business flogging chilli sauce.

−	If your phone has a NFC chip, then the Stripe app will also let you use your phone as a mobile EFTPOS machine that accepts credit cards for when you're out and about, and there is also a handy WooCommerce app that lets you track orders and sales from the website.	+	If your phone has a NFC chip, then the Stripe app will also let you use your phone as a mobile EFTPOS machine that accepts credit cards for when you're out and about, and there is also a handy [https://woocommerce.com/mobile/ WooCommerce app] that lets you track orders and sales from the website.

@@ Line 5: / Line 5: @@
 WordPress is slow. Install and configure [https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] to make it go much faster. Also, configure Apache to gzip all the static assets and use a long cache expiry time.
-== Allow user-installed plugin and themes ==
+== Allow user-installed plugins and themes ==
 I do not recommend it, but if you're game you can enable WordPress users with admin access to install their own plugins and themes by allowing write access to wp-content/{plugins,themes} and configuring as follows: