I wanted to try and update the look and feel of the site to something more modern and try using some CSS3 techniques. HTML 5 canvas was planned but I never got round to using it.

I’m sure there will be some bugs so do not hesitate to contact me or leave a comment if you find one.

Related posts:

1. WordPress 2.3.3 Upgrade
2. Header Image 14
3. WordPress 2.2.1 Theme Breaker

When deleting an account such as the admin one, WordPress can re-assign all the post under that account to the any account including the new administrators account.

The only thing I had to do was use a different email address when creating the new user and then change it back to the original once the admin user was deleted.

Take 5 Minutes to Make WordPress 10 Times More Secure

Related posts:

1. WordPress Avatar
2. WordPress 3.0
3. WordPress and Postfix

Related posts:

1. WordPress 2.3 Release Date
2. WordPress Upload File IO Error
3. Firefox 1.5 Growing Pains

SSL is used to encrypt data between the client e.g a user viewing a website to the web server which hosts the site. SSL uses certificates which are signed and verify the validity of a website. Like any vendor based system the certificate is as secure as the issuer. This means anyone can generate an SSL certificate but only “certified vendors” are considered safe.

Pre-requisites

This post assumes Apache 2 is installed on Ubuntu 10.04 (other versions may apply) with no issues. The default virtual host will be used as the example.

Install SSL

1. Ensure the SSL mod is installed so Apache can handle SSL requests sudo apt-get install ssl-cert
2. Enable the SSL module sudo a2enmod ssl
3. Before restarting the service, edit /etc/apache2/ports.conf and make sure there is a Listen 443 in the file. Alternatively add it in and if the entry is invalid apache won’t start.
4. Create a directory to store the SSL certificates sudo mkdir /etc/apache2/ssl
5. Restart apache service sudo service apache2 restart

Generate SSL Certificate

Only run steps in this section if the certificate to be used is not going to be issued by a vendor.

1. Create the certificate in the Apache SSL directory sudo make-ssl-cert /usr/share/ssl-cert/ssleay.cnf /etc/apache2/ssl/www.dannytsang.com.crt

Once complete go to Configure Apache 2

Applying For SSL

The steps may vary but this is what I had to go through to obtain an SSL certificate:

1. Install OpenSSL sudo apt-get install openssl
2. Generate a RSA private key. Enter a password when prompted openssl genrsa -des3 -out www.dannytsang.com.key 2048
3. Create the CSR openssl req -new -key www.dannytsang.com.key -out www.dannytsang.com.csr Example information:
   • Country Name (2 letter code) [AU]:GB
   • State or Province Name (full name) [Some-State]:Hertfordshire
   • Locality Name (eg, city) []:Stevenage
   • Organization Name (eg, company) [GX Networks Ltd]:Danny Tsang
   • Organizational Unit Name (eg, section) []:
   • Common Name (eg, YOUR name) []:www.dannytsang.com
   • Leave the rest blank
4. Ensure the CSR details are correct openssl req -noout -text -in www.dannytsang.com.csr If not go through the steps above again to re-generate the CSR
5. Submit the CSR to the vendor.
6. The vendor will verify details submitted before issuing the SSL certificate. Once that is complete continue to the next stage.

Depending on the level of the SSL certificate applied there is always at least 2 certificates that have to be included in Apache. One is the Vendor who signs the SSL and the SSL certificate itself.

7. Copy the vendor certificate to sudo mkdir /etc/apache2/ssl. For example sudo vi /etc/apache2/ssl/CaCert.pem
8. Copy the site / domain SSL certificate sudo vi /etc/apache2/ssl/www.dannytsang.com.crt

Configure Apache 2

There are various ways to enable HTTPS on a website. The options described below are the ones discussed in this article:

• Site Wide – The whole site uses HTTPS so that all the traffic is encrypted. This is the most secure method. Some limitations with this include any “resources” displayed on the site not from a HTTPS site will show a warning to the user. Website traffic will still be encrypted but not for non HTTPS parts e.g Ads
• Login / Accounts only – From user log in and onwards will be encrypted. Other parts are not.

For Login / Accounts only part, WordPress will be used as the example.

For both options there should be 2 virtual hosts configured in Apache. One for non encrypted and the other for encrypted. If the desired effect is for the user to explicitly type https into the browser then only the secure virtual host is need. Otherwise a redirect will be created so that users entering http://www.dannytsang.com will automatically go to https://www.dannytsang.com. The following will assume the virtual host file have already been created and working. The virtual host file will be called dannytsang.

1. Make a copy of the virtual host which will be used for the SSL part of the site sudo cp /etc/apache2/sites-available/dannytsang /etc/apache2/sites-available/dannytsangssl
2. Edit the secure virtual host file and make the following changes:
   • Change the port to 443, the default port for HTTPS traffic e.g <VirtualHost *:443>
   • ServerName – Ensure this directive is set to the same as the SSL certificate e.g ServerName www.dannytsang.com
   • SSLEngine – Turn SSL on e.g SSLEngine On
   • SSLCACertificateFile – Path to the vendor or “Certificate Authority” signing certificate. This may be optional and not required if it was not mentioned by the issuer e.g SSLCACertificateFile /etc/apache2/ssl/CaCert.pem
   • SSLCertificateChainFile – Intermediate CA. Same as above e.g SSLCertificateChainFile /etc/apache2/ssl/ICaCert.pem
   • SSLCertificateFile – Path to site SSL e.g SSLCertificateFile /etc/apache2/ssl/www.dannytsang.com.crt
   • SSLCertificateKeyFile – The file path to the private key used to sign the CSR e.g SSLCertificateKeyFile /etc/apache2/ssl/www.dannytsang.com.key
   • Save and exit the file

Example of the secure virtual host configuration file so far:

<VirtualHost *:443>
ServerName www.dannytsang.com

SSLEngine On
SSLCertificateChainFile /etc/apache2/ssl/ICaCert.pem
SSLCertificateFile /etc/apache2/ssl/www.dannytsang.com.crt
SSLCertificateKeyFile /etc/apache2/ssl/www.dannytsang.com.key

DocumentRoot /var/www/dannytsang

</VirtualHost>

Note that my example does not contain SSLCACertificateFile. For a self generated SSL the only SSLCertificateFile is needed.

Site Wide HTTPS

One of the pit falls of site wide encryption is that all content must reside on the https domain or from other https sources. Below is an example of what Google’s Chrome browser would show if content didn’t come from a secured resource. In my case it was Ads:

1. Edit the non secure virtual host file of the site sudo vi /etc/apache2/sites-available/dannytsang
2. Add the following lines below the SSL related directives:
   
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R]
</IfModule>

3. Save and exit the virtual host file.
4. Enable the new secure virtual host sudo a2ensite dannytsangssl
5. Restart Apache sudo service apache2 restart

Login HTTPS For WordPress

1. Edit the non secure virtual host file sudo vi /etc/apache2/sites-available/dannytsang
2. Add the following inside the <Directory /var/www/dannytsang>:
   
<Directory /var/www/dannytsang>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^wp-(admin|login|register)(.*) https://%{SERVER_NAME}/wp-$1$2 [L]
</IfModule>
</Directory>

   The RewriteRule is the rule for when it would change the URL to https. In this case it looks for any of the following combinations after the domain wp-admin, wp-login, wp-register e.g www.dannytsang.com/wp-login.php. Multiple rules may be added to match all sorts of sub directories.
3. Save and exit the virtual host file.
4. Add the following line to the non secure site so that going from a login / admin page to the normal part of the site e.g logging out and going back to the front page will change it to non https
   vi /etc/apache2/sites-available/dannytsang

<Directory /var/www/dannytsang>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule !^wp-(admin|login|register)(.*) - [C]
RewriteRule ^(.*)$ http://%{SERVER_NAME}/$1 [L]
</IfModule>
</Directory>

5. Save and exit the virtual host file.
6. Enable mod_rewrite in Apache sudo a2enmod rewrite
7. Enable the new secure virtual host sudo a2ensite dannytsangssl
8. Restart Apache sudo service apache2 restart
9. Edit the WordPress config file (wp-config.php) and add the following line to the bottom of the file define('FORCE_SSL_ADMIN', true);

Debugging Tools & Methods

I found Google Chrome to be the best browser to troubleshoot SSL problems. Chrome is the most promient in showing HTTPS problems (see non secure sources screenshot above). The problem with Chrome was that it was more strict on showing the “padlock” HTTPS icon.

Go to the Console in Chrome (Ctrl+Shift+j > Console tab) lists insure content warnings.

Summary

Whilst going through this setup process myself it has been a long and arduous process (even if it doesn’t look it from this write up). I have learnt:

• Check the Certificate Authority – Ensure it is from a reputable organization issuing / signing the SSL. SSL providers are not necessarily the company which signs them. Also cheap SSLs may be signed by an unknown / not recognised as a verified CA. This list of CA vary from browser to browser.
• Non secure SSL – Even if a page or site is encrypted using the HTTPS protocol, the page is not deemed secure if any information on a page comes from a non secure site.
• Check WordPress Plugins – Some plugins are not HTTPS aware for example lightbox2.
• Clear Cookies & Cache – Sometimes browsers cache information and so even restarting the webserver may still result in an unsecure page / site. I found the best practice was to close the browser and start it up again. A quicker way to do it is to clear the cache and cookies associated with the site.

forumserverapache2SSL

Generate a CSR: Apache (Open SSL)

WordPress Administration Over SSL

apache2 – redirect http to https

Intermediate Certificate Authority (CA) & SSL Installation Instructions for Apache

Related posts:

1. Enable SFTP On VSFTPD In Ubuntu
2. Awstats
3. Apache 2 Hardening Tips

Related posts:

1. WordPress 2.9.2
2. WordPress 2.3 Upgrade (Update)
3. WordPress 2.8.3

A work around is to use the browser upload which only allows you to select one file at a time to upload.

To fix the issue, upgrade your browser’s Adobe Flash plugin.

Related posts:

1. PHP File Upload Limit
2. Why Linux Desktop Is Not Ready… Yet
3. Opera Mobile Tested

Related posts:

1. WordPress 2.3.2
2. WP 2.8.5
3. WordPress 2.2.1 Upgrade Again

Related posts:

1. WordPress 3.1 Update.
2. WordPress 2.8.3
3. WordPress 2.3 Upgrade (Update)

Gravatar’s website

Related posts:

1. Remove WordPress Default Admin Account
2. WordPress and Postfix
3. WordPress Built-In Media Library Non Relative Links

I checked all my config settings for both VSFTP and Apache but ended up restarting both services which made it work. I did not see any errors in VSFTP logs and no relevant entries in Apache. One those strange occurrences I guess.

Related posts:

1. WordPress Permalink Change Error
2. WordPress Twitter Tools Shows Blank Page On Connect
3. SPA3102 Username And Password

Related posts:

1. WordPress 2.2.1 Theme Breaker
2. WordPress 2.1
3. WordPress 2.3.1 Installed

Related posts:

1. WordPress 2.6.1 Upgrade
2. Plugin Problem With WordPress 2.3
3. WordPress 3.0

Related posts:

1. WordPress 2.0.7
2. WordPress 2.3.1 Installed
3. WordPress 2.1

Related posts:

1. WordPress 3.0
2. WordPress 2.3.2
3. WordPress 2.6.3 Upgrade

Related posts:

1. WordPress 2.5 Upgrade
2. Hectic
3. WordPress 2.1

Related posts:

1. WordPress 2.9.2
2. WordPress 3.1 Update.
3. WordPress 2.0.7

WordPress 2.8.1 broke my automatic upgrade

Related posts:

1. Automatic WordPress Upgrade To 2.7.1
2. WordPress 2.6.3 Upgrade
3. WordPress 2.3.3 Upgrade

Related posts:

1. TomTom 6.15
2. WordPress 2.9 Released
3. WordPress 2.0.4 > 2.0.5

Related posts:

1. Automatic WordPress Upgrade To 2.7.1
2. WordPress 2.7 – Big UI Changes
3. WordPress and Postfix

I did it because I have to go to work to minutes ago and the the fact that the automatic plugin upgrades have been working out very well. As usual I took the precaution of backing EVERYTHING up but I did not have to use it. Thumbs up to the WordPress people.

Related posts:

1. Plugin Problem With WordPress 2.3
2. WP Upgrade
3. WordPress 2.5 RC2