We’ve renewed the SSL certificate on our mail servers (because it was due to expire soon).
Almost all customers shouldn’t notice any change, but if you read e-mail using a secure connection with an unusual mail program that doesn’t handle SSL connections properly, you might be asked to “accept” the new certificate.
The PHP developers recently released versions 5.4.39, 5.5.23 and 5.6.7 that fix several bugs. We’ve upgraded PHP 5.4, 5.5 and 5.6 on our servers as a result.
These changes should not be noticeable, but in the unlikely event you experience any trouble, don’t hesitate to contact us.
A couple of customers have asked if our servers are vulnerable to the FREAK attack SSL security bug.
The answer is no: we don’t use the weak “export grade ciphers suites” that are affected by the bug, so no site hosted on our servers is vulnerable. You can verify this with the FREAK attack server check tool.
For a long time, our mail system has blocked obviously malicious filenames like “443645787823424455.scr”, “Invoice.pdf.exe”, and so on, even if they aren’t actually flagged by the antivirus software we use (which can happen if they’re new viruses that don’t yet have matching patterns).
Recently, we’ve seen a dramatic increase in simpler names where the virus author doesn’t even try to hide the fact that it’s a program: things as simple as “Invoice.exe” in a zip file. We’ve received a couple of reports that people unzipped these, ran them, and clicked past the Windows warning saying that programs from the Internet can harm your computer — perhaps assuming that if it wasn’t flagged by either our virus scanner or the virus scanner on their own computer, it must be okay.
We want to make sure our customers never fall victim to anything like this, so we’ve expanded our blocked filename patterns to include simple “.exe” files (and other additions). This may very occasionally reject legitimate messages with an error asking the sender to rename the file and resend it, but it will solve far more problems than it causes.
We’re using the same list of filename extensions that Gmail uses — if we block it, Gmail would block it, too. You can find more information on our support page about virus scanning.
We’ve added experimental support for the new PHP 5.6 series, although the default for new accounts remains PHP version 5.5 for now.
Adventurous customers can choose PHP 5.6 as a new option in our My Account control panel. Keep in mind that some scripts are not yet compatible with PHP 5.6, and there may be unexpected problems because it’s new and relatively untested.
If you try it and have any trouble, contact us and we’ll do our best to help.
The PHP developers recently released versions 5.4.38 and 5.5.22 that fix several bugs. We’re upgrading PHP 5.4 and 5.5 on our servers as a result. This will be complete on all servers within 24 hours.
These changes should not be noticeable, but in the unlikely event you experience any trouble, don’t hesitate to contact us.
The PHP developers recently released versions 5.4.37 and 5.5.21 that fix several bugs. We’re upgrading PHP 5.4 and 5.5 on our servers as a result. This will be complete on all servers within 24 hours.
These changes should not be noticeable, but in the unlikely event you experience any trouble, don’t hesitate to contact us.
The researchers at Sucuri yesterday announced that they’ve discovered a critical security bug in the widely used Pagelines/Platform WordPress themes. If you use one of these themes or their many derivatives, “hackers” can easily take over your site unless you update the theme.
Since many of our customers use these themes, so we’ve added security rules to block attacks even if you haven’t updated. And we’re glad we did: our logs show that a large Chinese botnet started attacking every WordPress site we host last night, in alphabetical order (they’re currently up to domain names starting with “e”), testing whether each site is vulnerable to the bugs.
We’re again surprised to see how many customers are using versions of these themes that haven’t been updated in years. I know we sound like a broken record, but when WordPress offers to update something you’ve installed, you must update it if you want your site to stay secure.
Although we haven’t offered the long-obsolete PHP 5.2 series to new customers for some time, some who signed up long ago are still using it.
(New customers have defaulted to using PHP 5.5 for the last few months, and PHP 5.3 was the default for several years before that. We’ve also previously nagged everyone still using PHP 5.2 by e-mail, asking them to upgrade to at least PHP 5.3.)
For those customers still using PHP 5.2 despite the nagging, this is just a quick note that we’ve “rebuilt” PHP 5.2.17 for technical reasons to allow it to keep running on our systems. It now uses slightly newer versions of various libraries, including libxml, FreeType, ImageMagick, MySQL, and OpenSSL. The rebuilt version will be deployed on all our servers within the next few hours.
These changes should not be noticeable. In the unlikely event you experience any trouble, don’t hesitate to contact us.
The PHP developers recently released versions 5.4.36 and 5.5.20 that fix several bugs. We’re upgrading PHP 5.4 and 5.5 on our servers as a result. This will be complete on all servers by 5 PM Pacific time on Monday (January 6).
In addition, PHP 5.3.29 has been upgraded to use ionCube Loader 4.7.3.
These changes should not be noticeable, but in the unlikely event you experience any trouble, don’t hesitate to contact us.
