The demise of 32 bit distros is nigh!
Some distros are dropping or reducing support for 32 bit versions. e.g. only providing 64 bit ISO downloads.
Some software makers are no longer putting out 32 bit versions of their software. e.g. Since version 9 Oracle have only released a 64 bit version of Java.
In most cases you will be fine to remain on 32 bit distros until you need some software application that is 64 bit only (e.g. Java 9 or Java 10). If you have a lot of memory and are not limited by the 32 bit application 4GB per process limit then running a 64 bit kernel on a 32 bit distro can be a good option.
If you are able to easily reinstall your server then using a 64 bit distro for your next reinstall is a straight forward option.
If you do not have the luxury of a reinstall then you may want to consider a cross grade. Where you convert a 32 bit distro to a 64 bit one.
We have been adding 32 to 64 bit cross grade support to our distrorejuve tool. At the moment the script is in alpha. We recommend you make a full server snapshot prior to starting the process.
You can run the distrorejuve 32 to 64 bit crossgrade as:
RimuHosting has now been providing VM servers for over 15 years.
Back in the day the state of the art distros we setup for customers included 32-bit Debian 3- and Ubuntu 6-based servers.
Things have moved on. By default all new orders are setup with 64-bit distros. And Debian is up to version 9, while Ubuntu 18.04 is about to be released.
The newer distros are almost exclusively the ones you will want. They will have the latest libraries and applications.
Our team is working on the best approach to secure our customers' systems against the recently reported Spectre and Meltdown vulnerabilities. Our first step is to understand the problem and its mitigations. This post provides a roundup of discussions and work on the topic with a focus on mitigation for the Xen hypervisor.
Spectre (aka “Branch target injection”) includes:
SP1) speculative execution to perform bounds-check bypass (CVE-2017-5753)
SP2) utilizing branch target injection (CVE-2017-5715) to cause kernel code at an address under attacker control to execute speculatively
SP3) third variant (CVE-2017-5754) rogue data cache load. Relies on the fact that, on impacted microprocessors, during speculative execution of instruction permission faults, exception generation triggered by a faulting access is suppressed until the retirement of the whole instruction block. Subsequent memory accesses may cause an allocation into the L1 data cache even when they reference otherwise inaccessible memory locations. As a result, an unprivileged local attacker could read privileged (kernel space) memory (including arbitrary physical memory locations on a host) by conducting targeted cache side-channel attacks.
We have added the latest 4.14 kernel to our list of stable kernels for 64bit VPS servers.
The 4.14 kernel includes a large number of performance enhancements, including ...
- filesystem io
- block_mq scheduler improvements
- new selectable scheduler options for disk io
- improved cryptographic performance
- cgroup2 support merged
SSL is good, you should use it everywhere!
Letsencrypt it is a project that allows you to obtain signed certificates for free (you should consider donating though) to secure your website. Big efforts have been done to make this accessible to anyone.
In order to issue SSL certificates Certificate Authorities will check that you can control the domain, by either 1) sending validation emails to specific addresses within domain, 2) requesting special files in the website for the domain or 3) setup special DNS records that are checked during the certificate issue, Letsencrypt specially likes to do the latter two. These special files or DNS records are normally called challenges, and if you host DNS zones with Rimuhosting or Zonomi name servers now there is an easy way for you to issue Letsencrypt certificates.
(Photo by Steven Lilley )
We have found some virtualmin installs will change the format of new virtualhosts from ip:80 to *:80 sometimes which breaks virtualhosts as the *:80 overrides the ip:80.
This can result in websites showing another website content, and usually shows up right after you add a new domain in virtualmin.￼
Recently there have been two sets of Xen vulnerabilities. One being disclosed in September, the other earlier today. Historically we have had to organize host updates which required downtime to reboot VMs.
For these last sets of vulnerabilities we have been able to use a recently introduced live patching feature in Xen to mitigate the vulnerabilities for most of our hosts. The live patching swaps out an exploitable function, with a patched function. It can do this without restarting the host or the VM.
Live patching will work for most (but not all) vulnerabilities. Resulting in fewer VM restarts, and less client disruption. Taking a little more hassle out of your hosting.
We have added a couple of features to the 25mail.st service.
First, we now support DKIM email signing. This lets our email servers sign outgoing messages so that recipients can verify that the email was sent from an authorized server. You will need to add a DNS entry for each email domain wishing to have their emails signed. Adding a 25mail.st DKIM key will not affect other email servers you may be using. To get it setup see: https://25mail.st/faq.jsp?is_require_login=Y#dns
We have also added subaddressing. So you can invent subaddresses on the fly (e.g. email@example.com or firstname.lastname@example.org) and by default they will all arrive to that user's mailbox. For more details see https://25mail.st/faq.jsp?is_require_login=Y#subaddressing
Photo credit: cayusa
Fail2ban is a great "dynamic" firewall for servers that is installed by default on many of our VPSs, and we can install it on your VPSs at your request. It protects against brute-force attacks, where an attacker is trying to guess a password or exploit certain classes of vulnerabilities on servers.
One potential problem with fail2ban and similar tools is the false positive problem, that is, banning yourself from your own VPS, particularly if you don't always get your password right. In this post, I'll explain how to fix that problem using fail2ban's whitelist feature.
Virtualmin now supports Let Encrypt, this means you can easily get multiple SSL certificates easily and free if needed.
Here is how you can set that up.
Step 1: Login to your virtualmin, select the domain from the drop down in the top left.
Step 2: Click 'Edit Virtual Server' , under the 'Enabled Features' you will see 'SSL Website Enabled'. check the checkbox and save
Step 3: Expand the left menu under Server Configuration click on Manage SSL certificate. The top Far right should have a tab named 'Let's Encrypt' which you can click on.
Step 4: Change the 'Months between automatic renewal' from Manual to every 2 months or similar and save.
Step 5: Test the domain works with https and you are done.
Notes: You will need apache 2.4 to allow multiple SSL certificates on a single IP,