Thank you to all our wonderful customers for your business in 2010. We have had a great time setting up servers and helping out with so many varied and interesting environments. And helping our customers launch some cool websites. A number of our staff are taking a break over Christmas and the New Year to…
Know an open source developer that is looking to launch their application? Help them out by nominating them in our Launchtime VPS twitter competition. Yesterday we launchtimevps.com , the VPS-focused RimuHosting website. http://blog.rimuhosting.com/2010/12/16/introducing-launchtime-ri-mu/ Today we would like to help some open source software developers launch their own website. Competition-style for a bit of fun. Up…
We are uber-happy to announce the 2010 UI RimuHosting website refresh. And it is not all merely fresh fonts, headers, footers and colors. We have a new ordering system to make it quicker and easier to get a new server up and running. Simplified navigation. A new domain. And setup-as-part-of-the-order-process. launchtimevps.com domain: First up there…
Due the severity of the proftp bug, and the mixed systems and versions in the VPSs, we many customers have switched to use vsftp, others just started using sftp, regardless that we have the following notes for customers willing to enable proftpd again: The bug affects versions >= 1.3.2rc3, for more information: http://bugs.proftpd.org/show_bug.cgi?id=3521 Here is…
Introducing http://bakop.com, the offsite FTP backup service We have ‘broken out’ the popular RimuHosting-customer-only backupspace service into a standalone and separately branded service. That anyone can sign up for and use. You get to use however much space you need. No file quotas. The setup continues to use the linux-foo goodness that enables sshfs, sftp,…
A stack overflow bug has been identified in ProFTPd. This bug allows users to gain remote access (usually root) to an attacker. This bug requires immediate attention and potentially a restore to the last backup image of your server. Information on the bug can be found here: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4221 We have been handling the issue per…