<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>The Gradwell Blog</title>
	<atom:link href="http://blog.gradwell.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gradwell.com</link>
	<description>Enabling the internet you don't see...</description>
	<pubDate>Fri, 22 Aug 2008 11:50:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<item>
		<title>Twittex Interviewed By Online Journalism Blog</title>
		<link>http://blog.gradwell.com/2008/08/22/twittex-interviewed-by-online-journalism-blog/</link>
		<comments>http://blog.gradwell.com/2008/08/22/twittex-interviewed-by-online-journalism-blog/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 11:50:24 +0000</pubDate>
		<dc:creator>Stuart Herbert</dc:creator>
		
		<category><![CDATA[News]]></category>

		<category><![CDATA[Twittex]]></category>

		<guid isPermaLink="false">http://blog.gradwell.com/?p=124</guid>
		<description><![CDATA[The Online Journalism Blog has been busy interviewing many of the companies looking to fill the gap left when Twitter pulled out of the SMS updates market last week.  One of those companies is Gradwell dot com, who launched the twittex.com service on Wednesday this week.
You can read the full interview here.
]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://onlinejournalismblog.com">Online Journalism Blog</a> has been busy interviewing many of the companies looking to fill the gap left when Twitter pulled out of the SMS updates market last week.  One of those companies is <a href="http://www.gradwell.com/">Gradwell dot com</a>, who launched the <a href="http://twittex.com">twittex.com</a> service on Wednesday this week.</p>
<p>You can read the full interview <a href="http://onlinejournalismblog.com/2008/08/22/twitter-sms-interview-5-stuart-herbert-of-twittex/">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/08/22/twittex-interviewed-by-online-journalism-blog/feed/</wfw:commentRss>
		</item>
		<item>
		<title>10 Free Messages For First 250 Users Who Sign-Up</title>
		<link>http://blog.gradwell.com/2008/08/20/10-free-messages-for-first-250-users-who-sign-up/</link>
		<comments>http://blog.gradwell.com/2008/08/20/10-free-messages-for-first-250-users-who-sign-up/#comments</comments>
		<pubDate>Wed, 20 Aug 2008 13:39:35 +0000</pubDate>
		<dc:creator>Stuart Herbert</dc:creator>
		
		<category><![CDATA[Twittex]]></category>

		<guid isPermaLink="false">http://blog.gradwell.com/?p=122</guid>
		<description><![CDATA[To celebrate the launch of our new Twitter SMS alerts service, we&#8217;re giving away 10 free messages to the first 250 users who sign up for the service.
Register at twittex.com today!
]]></description>
			<content:encoded><![CDATA[<p>To celebrate the launch of our new Twitter SMS alerts service, we&#8217;re giving away 10 free messages to the first 250 users who sign up for the service.</p>
<p>Register at <a href="http://twittex.com/">twittex.com</a> today!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/08/20/10-free-messages-for-first-250-users-who-sign-up/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Provisioning Engineer</title>
		<link>http://blog.gradwell.com/2008/08/20/provisioning-engineer-2/</link>
		<comments>http://blog.gradwell.com/2008/08/20/provisioning-engineer-2/#comments</comments>
		<pubDate>Wed, 20 Aug 2008 13:32:25 +0000</pubDate>
		<dc:creator>jake</dc:creator>
		
		<category><![CDATA[Available Jobs]]></category>

		<guid isPermaLink="false">http://blog.gradwell.com/?p=119</guid>
		<description><![CDATA[Are you fascinated by new technology? Do you like playing with computers and other electronic devices to find out how they work? Can you solve problems?
If you can, then you should think about working for Gradwell.
Your responsibilities will be processing customer orders, predominantly configuring and dispatching VoIP Telephone hardware, maintaining our stock, processing deliveries and [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Are you fascinated by new technology? Do you like playing with computers and other electronic devices to find out how they work? Can you solve problems?</strong></p>
<p>If you can, then you should think about working for Gradwell.</p>
<p>Your responsibilities will be processing customer orders, predominantly configuring and dispatching VoIP Telephone hardware, maintaining our stock, processing deliveries and assisting the support and operations teams.</p>
<p><span id="more-119"></span></p>
<p>Gradwell dot com Limited is a rapidly growing Internet Services Provider who focuses on VoIP (www.gradwell.com/voip/), email and web service solutions. We are a pioneer in the exciting new world of Internet telephony and this section of our business is growing rapidly.</p>
<p>As a new and fast moving technology, VoIP is a demanding product to provide and our customer support team is regularly faced with evaluating new and different types of network routers, phones, broadband services etc. to make sure it all fits together correctly so our clients can make phone calls.</p>
<p>We have won a number of awards in 2004 and 2005 in various DTI schemes including &#8220;Best use of Broadband&#8221; for our VoIP product and &#8220;Best Teleworking Company&#8221; and &#8220;Best Online Customer Service&#8221; for both of which we were highly commended. 2006 and 2007 have been equally exciting and we are continuing to double every year in terms of customer base, financial turn over and staff. We are a team of 20 with annualised turn over of £2 million.</p>
<p>Prior experience of the Internet, IT and Telecoms Sectors will be highly beneficial as our core business is selling outsourced telecoms, email and web hosting services to IT consultants, designers, media agencies and other small and medium sized technology based businesses.</p>
<h3>About the job</h3>
<p>Your responsibilities will be processing customer orders, predominantly configuring and dispatching VoIP Telephone hardware, maintaining our stock, processing deliveries and assisting the support and operations teams.</p>
<p>You will also be involved in configuring a wide range of linux servers and PCs in a busy TCP/IP network environment.</p>
<p>You will need to have a good familiarity with web, email and computer networks, an understanding of broadband, experience with MS Windows operating systems or linux based systems . Experience with VoIP services will be a plus.</p>
<p>You will be well organised, enthusiastic about new technology, eager to learn, good at asking questions to solve problems and have good written and spoken English with a clear telephone manner.</p>
<p>This position will appeal to those with a keen interest in the latest internet and telecoms technology and who are looking to gain exposure to the world of work and who wish to gain experience prior to a job in customer/it technical support.</p>
<p>Salary is £13,000 per year. We also offer a range of benefits (including free parking in Bath).</p>
<p>This is a full time position (37 hours a week), based at our Bath offices in Cheltenham St, Bath, reporting to our Operations Manager. You will receive 24 days holiday per year.</p>
<h3>Application Details</h3>
<p>For more information, please view our website at http://www.gradwell.com or contact Barrie Millett (barrie.millett@gradwell.net, 01225 800 888).</p>
<p>Please apply via email to <a href="mailto:barrie.millett@gradwell.net">Barrie Millett</a>, or post to: gradwell dot com Limited, 26 Cheltenham St, Bath, BA2 3EX.</p>
<p>Our offices are located on the Lower Bristol Road in Bath, a 10 min walk from the train station, next to the Green Park Tavern.</p>
<p>We are continually expanding our provisioning team, so if you are interested in working with us, please get in contact.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/08/20/provisioning-engineer-2/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Twittex (SMS Service For UK Twitter Users) Launched!</title>
		<link>http://blog.gradwell.com/2008/08/20/twittex-sms-service-for-uk-twitter-users-launched/</link>
		<comments>http://blog.gradwell.com/2008/08/20/twittex-sms-service-for-uk-twitter-users-launched/#comments</comments>
		<pubDate>Wed, 20 Aug 2008 12:22:21 +0000</pubDate>
		<dc:creator>Stuart Herbert</dc:creator>
		
		<category><![CDATA[News]]></category>

		<category><![CDATA[Twittex]]></category>

		<guid isPermaLink="false">http://blog.gradwell.com/?p=115</guid>
		<description><![CDATA[We&#8217;re very pleased to announce the launch of twittex - a simple prepay service that delivers Twitter updates from your friends to your mobile phone via SMS. twittex is currently available on all UK networks. SMS messages are charged at 10p each, including VAT.
Up until 14th August 2008, Twitter provided a free SMS alerts service for its [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;re very pleased to announce the launch of <a title="Twittex.com - Twitter To Your Pocket" href="http://twittex.com/">twittex</a> - a simple prepay service that delivers Twitter updates from your friends to your mobile phone via SMS. twittex is currently available on all UK networks. SMS messages are charged at 10p each, including VAT.</p>
<p>Up until 14th August 2008, Twitter provided a free SMS alerts service for its users in the UK. From inside Twitter, you could register your mobile phone, and decide which of your friends you wanted to follow via SMS. The cost of providing this service for free was one that Twitter couldn&#8217;t continue to carry, and <a href="http://blog.twitter.com/2008/08/changes-for-some-sms-usersgood-and-bad.html">the service was withdrawn</a> as a result.</p>
<p>At Gradwell.com, we&#8217;d recently launched a new service news website so that our customers could be kept informed of alerts and maintenance of our major services (broadband, email, hosting and VoIP). The new service published updates to Twitter, so that our customers could use Twitter&#8217;s SMS alerts for when they were away from their computers. With Twitter no longer sending out SMS alerts, we needed an alternative. So we built twittex!</p>
<p>To get started, create an account at <a href="http://twittex.com/">twittex.com</a>, add your mobile phones and your twitter accounts, and some credit (£1, £5, £10 or £20), and you&#8217;re all set.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/08/20/twittex-sms-service-for-uk-twitter-users-launched/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Visualising our focus</title>
		<link>http://blog.gradwell.com/2008/08/03/gradwells-focus/</link>
		<comments>http://blog.gradwell.com/2008/08/03/gradwells-focus/#comments</comments>
		<pubDate>Sun, 03 Aug 2008 11:51:24 +0000</pubDate>
		<dc:creator>Peter Gradwell</dc:creator>
		
		<category><![CDATA[General Blog]]></category>

		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://blog.gradwell.com/?p=96</guid>
		<description><![CDATA[One of the things we do in Gradwell is write an internal blog. We include three things:

We documents all our system changes, so if something is planned, or has changed, we have any easy reference for it.
We write up internal case studies of our customers, and feedback from our birthday lunches
Weekly, on Friday afternoons, we [...]]]></description>
			<content:encoded><![CDATA[<p>One of the things we do in Gradwell is write an internal blog. We include three things:</p>
<ol>
<li>We documents all our system changes, so if something is planned, or has changed, we have any easy reference for it.</li>
<li>We write up internal case studies of our customers, and feedback from our birthday lunches</li>
<li>Weekly, on Friday afternoons, we do a round up of what all the teams (tech, sales, support, billing) got up to that week.</li>
</ol>
<p>Unfortunately we can&#8217;t make the whole internal blog public, but it is interesting to use a new tool I found, <a href="http://wordle.net/" target="_blank">Wordle</a> to produce a &#8220;word cloud&#8221; for that internal blog. A word cloud is an image made from your blog text which gives greater prominence to words that appear more frequently 		in the text:</p>
<p><img title="Gradwell Office Blog" src="http://peter.gradwell.com/tmp/gradwell-blog.png" alt="Gradwell Office Blog" width="541" height="311" /></p>
<p>We can also compare that to the word cloud that you get from the public Gradwell blog:</p>
<p><img title="Gradwell Office Blog" src="http://peter.gradwell.com/tmp/gradwell-public.png" alt="Gradwell Office Blog" /></p>
<p>It&#8217;s good to see the themes are consistent:</p>
<ul>
<li>Lots of focus on happy customers, through tickets and Birthday Lunches.</li>
<li>Lots of continued work on infrastructure and scaling, particularly email and storage, as well as migrating from legacy servers to our newer platforms.</li>
<li>A huge amount of work being completed and delivered, with many small incremental improvements.</li>
</ul>
<p>We&#8217;d be interested in <em>your feedback</em> as to how we&#8217;re doing, via our <a href="https://www.surveymonkey.com/s.aspx?sm=0WET5kpkqAX_2b5fM_2fhlUoZA_3d_3d" target="_blank">online survey</a>. <strong>Thanks</strong>!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/08/03/gradwells-focus/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Gradwell Not Vulnerable To Latest DNS Attack</title>
		<link>http://blog.gradwell.com/2008/07/25/gradwell-not-vulnerable-to-latest-dns-attack/</link>
		<comments>http://blog.gradwell.com/2008/07/25/gradwell-not-vulnerable-to-latest-dns-attack/#comments</comments>
		<pubDate>Fri, 25 Jul 2008 18:00:57 +0000</pubDate>
		<dc:creator>Stuart Herbert</dc:creator>
		
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://blog.gradwell.com/?p=90</guid>
		<description><![CDATA[By now, on websites like the BBC News, you will probably have read stories about a serious security problem that was recently found in many of the DNS servers commonly used on the Internet.  Some of our customers have contacted our Support phone line asking for more information about Gradwell dot com&#8217;s response to this [...]]]></description>
			<content:encoded><![CDATA[<p>By now, on websites like the BBC News, you will probably have read <a href="http://news.bbc.co.uk/1/hi/technology/7525206.stm">stories about a serious security problem</a> that was recently found in many of the DNS servers commonly used on the Internet.  Some of our customers have contacted our Support phone line asking for more information about Gradwell dot com&#8217;s response to this problem.</p>
<p>Gradwell dot com has been aware of this issue with DNS servers since early July, thanks to<a href="http://www.linux.com/feature/141080"> a story posted on the popular Linux.com website</a>.  We immediately checked our DNS servers, and determined that <strong>our nameservers are not vulnerable to this attack</strong>, using <a href="http://www.doxpara.com/">the testing tools</a> published by the security researcher who discovered this issue.</p>
<p>If you run your own nameserver at all, <a href="http://isc.sans.org/diary.html?storyid=4780">the current advice from security experts</a> is to ensure that you have upgraded it to the very latest version available.  I personally use <a href="http://lwn.net/">Linux Weekly News</a>&#8216; excellent weekly security round-up page to keep track of all the reported security updates for the different Linux distributions; your Linux distribution of choice will also publish regular security advisories.</p>
<p>I hope this clarifies the situation for our customers.  If you do have any concerns that I have not addressed, or at any time believe you&#8217;ve spotted a security problem that we haven&#8217;t addressed, you can raise an incident with our Customer Services team in the usual way, or contact me directly as firstname.lastname@gradwell.net.</p>
<p>Best regards,<br />
Stu<br />
&#8211;<br />
Stuart Herbert, Technical Manager, Gradwell dot com Ltd</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/07/25/gradwell-not-vulnerable-to-latest-dns-attack/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Virgin Media Including Telewest and NTL Portability Now Available</title>
		<link>http://blog.gradwell.com/2008/07/10/virgin-media-including-telewest-and-ntl-portability-now-available/</link>
		<comments>http://blog.gradwell.com/2008/07/10/virgin-media-including-telewest-and-ntl-portability-now-available/#comments</comments>
		<pubDate>Thu, 10 Jul 2008 13:06:53 +0000</pubDate>
		<dc:creator>Peter Gradwell</dc:creator>
		
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://blog.gradwell.net/?p=88</guid>
		<description><![CDATA[We are very pleased to announce that Gradwell can now port Virgin Media (including Telewest and NTL) numbers for use with our VoIP services.
Please visit our porting section or contact our porting team for more information about porting your Virgin Media number to Gradwell!
]]></description>
			<content:encoded><![CDATA[<p>We are very pleased to announce that Gradwell can now port Virgin Media (including Telewest and NTL) numbers for use with our VoIP services.</p>
<p>Please visit our <a href="http://www.gradwell.com/voip/porting/">porting section</a> or contact our <a href="http://www.gradwell.com/contact/">porting team</a> for more information about porting your Virgin Media number to Gradwell!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/07/10/virgin-media-including-telewest-and-ntl-portability-now-available/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Gradwell&#8217;s Busy May and June</title>
		<link>http://blog.gradwell.com/2008/07/06/gradwells-busy-may-and-june/</link>
		<comments>http://blog.gradwell.com/2008/07/06/gradwells-busy-may-and-june/#comments</comments>
		<pubDate>Sun, 06 Jul 2008 10:06:29 +0000</pubDate>
		<dc:creator>Peter Gradwell</dc:creator>
		
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://blog.gradwell.com/?p=87</guid>
		<description><![CDATA[May and June 2008 have been exceptionally busy for Gradwell, with a big focus on talking to customers, improving customer service and increasing service resiliance. Here are some highlights:
Technically:

We&#8217;ve been working on the stability of the email file servers, and had a couple of weeks with no nagios alerts for them (touch wood). We also [...]]]></description>
			<content:encoded><![CDATA[<p>May and June 2008 have been exceptionally busy for Gradwell, with a big focus on talking to customers, improving customer service and increasing service resiliance. Here are some highlights:</p>
<p>Technically:</p>
<ul>
<li>We&#8217;ve been working on the stability of the email file servers, and had a couple of weeks with no nagios alerts for them (touch wood). We also managed to speed up our backups and shorten the time window.</li>
<li>We added a further 7 servers to our VMWare cluster, we have 100 Ghz and 168 Gig of RAM deployed under vmware now, and quite a lot more servers to migrate over.</li>
<li>We&#8217;ve installed £48,000 worth of Cisco Switching gear in our London data centres, as part of a plan to upgrade and improve the redundancy of our core ethernet network, and agreed the purchase of further switch upgrades to our Telecoms network (worth EUR 120,000), to be implemented in July and August.</li>
<li>We&#8217;ve implemented a new security policy, and restructured all our internal web applications to further partition and secure them.</li>
<li>4 Industrial placement students joined our development team (3 will leave this summer) and have completed their inductions.</li>
<li><a href="http://www.stuartherbert.com/" target="_blank">Stuart Herbert</a>, our new Technical Manager, has been with us now for three months and is getting to grips with the wide scope of work we do.</li>
<li>We&#8217;ve done huge amount of other minor fixes and improvements - with over 200 entries logged in our change management system, mainly on email, voip and billing systems.</li>
</ul>
<p>Products:</p>
<ul>
<li>Our broadband product has launched and been well received, with every customer who has switched to resolve a VPN or VoIP quality issue having been statisfied! <strong>Premium Broadband</strong> does <em>make a difference</em>.</li>
<li>We&#8217;ve worked on the implementation and testing of the new Tiscali Annex M service, an enhancement to our broadband range which will give customers a 2.5 Megabit upstream link - due 10th July.</li>
<li>We&#8217;ve completed 999 test calls on our VoIP Platform</li>
<li>We are looking at how we can package our expertise in VoIP, networks and products like Trixbox (and IP PBX) into a managed services offering.</li>
<li>Zimbra testing continues. Zimbra is an email service that provides diary, calendaring and contacts integration, like Microsoft Exchange. <a href="mailto:peter@gradwell.com">Please get in touch</a> if you would like to take part.</li>
<li>We&#8217;ve continued to deploy our <em>newsip</em> VoIP platform for Centrex customers, with good results. This gives more redundancy, scalability, and the ability to view the status of other customers on the phone via <em>Lit Lamps</em>.</li>
<li>We tested integration with <em>SpinVox</em>, a service which converts voicemails to text, and hope to roll this out in July 08.</li>
</ul>
<p><em>Customer Service: </em></p>
<ul>
<li>The support team has been slightly restructured, merging into a broader customer service unit which covers technical support, customer service &amp; billing and product delivery (e.g. number porting).</li>
<li>As part of this, we are starting to assign support incidents to individual members of staff, so they take a more case orientated approach to resolving customer queries.</li>
<li>Our new <a href="https://portal.gradwell.net/" target="_blank">online customer portal </a>now provides a view for support tickets, and will soon track the generic service issues/bugs we know about as well.</li>
<li>We&#8217;ve built the <a href="http://www.gradwellstatus.com/" target="_blank">prototype </a>of the replacement for our Gradnoc status service, and hope to get that released in early July.</li>
<li>The team of 11 continue to handle approximately 600 queries from customers per week, across both technical and billing queries.</li>
</ul>
<p><em>Sales &amp; Marketing:</em></p>
<ul>
<li>Sales have continued very strongly in the summer months, breaking a few of our previous records, which is always excellent news. Phone calls are up 79% since January 2008.</li>
<li>We&#8217;ve telephoned nearly all our resellers this month (some 200) and driven 2936 miles in May talkin to them, bringing them upto date, getting positive fantastic and useful feedback - some times it&#8217;s just good to talk.</li>
<li>We held the first Gradwell lunch in Bristol, meeting 15 customers, from one of the first, to one of the most recent. The experience was very enjoyable and again, customers. <strong><a href="http://blog.gradwell.com/2008/04/29/gradwells-10th-birthday-lunch-series/">Come and see us</a> in Portsmouth in July, or Edinburgh in August.</strong></li>
<li>Emails to promote Unlimted IAX Trunks, Broadband and Customer Lunches were sent out and good a strong response.</li>
</ul>
<p>Hopefully this gives a brief taste of what has happened behind the scenes at Gradwell, and much more is already underway in July!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/07/06/gradwells-busy-may-and-june/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Customer FTP and Website Security</title>
		<link>http://blog.gradwell.com/2008/06/09/customer-ftp-and-website-security/</link>
		<comments>http://blog.gradwell.com/2008/06/09/customer-ftp-and-website-security/#comments</comments>
		<pubDate>Mon, 09 Jun 2008 20:46:41 +0000</pubDate>
		<dc:creator>Peter Gradwell</dc:creator>
		
		<category><![CDATA[General Blog]]></category>

		<guid isPermaLink="false">http://blog.gradwell.com/?p=85</guid>
		<description><![CDATA[Last week, we became aware of a number of customers websites being altered, with the addition of some extra hidden code to customer’s home pages.
No personal data has been compromised (apart from an encrypted version of FTP passwords) and all sites have been restored as far as possible.
We have been investigating this and whilst we [...]]]></description>
			<content:encoded><![CDATA[<p>Last week, we became aware of a number of customers websites being altered, with the addition of some extra hidden code to customer’s home pages.</p>
<p><em>No personal data has been compromised (apart from an encrypted version of FTP passwords) and all sites have been restored as far as possible.</em></p>
<p>We have been investigating this and whilst we first thought that this attack was possible through the exploitation of weak customer passwords, we have now proved that the hacker was manipulating our ftp server username and password database, and adding additional usernames into the system in order to gain access to customer’s websites.</p>
<p>We have been able to successfully monitor this attack in action, which has allowed us to exactly understand what went on, how it happened and most importantly, the full extent of the attack.</p>
<p><strong>The Attack – What happened?</strong><br />
A customer’s website was compromised, probably through some insecure php code, and the attackers uploaded some code which allowed them to browse a mysql database. </p>
<p>Our web servers have access to our management database, so that they can pull down the configuration for customer websites. It seems likely that at some point we inadvertently miss-configured the permissions on the configuration file storing the database access credentials.</p>
<p>From this, the attacker was able to scan the server configuration files and determine a mysql username on our web hosting database. </p>
<p>This user was able to edit the ftp server database table, and they created additional ftp usernames that mirrored customer’s usernames (but with different passwords), which they then used to access the customer&#8217;s website accounts. The extra usernames were then deleted, to hide their trace.</p>
<p><strong>How do we know?</strong><br />
From our FTP server logs we have been able to identify which files were edited, and it is clear that the only change was to alter the index/home page on a website. </p>
<p>We were also able to add monitoring to our database servers and determine which username and password was used, and what changes they made to our database.</p>
<p>From our logging of the network traffic, we can see that no other data was misappropriated, specifically no personal customer data.</p>
<p><strong>What have we done to rectify &#038; prevent future occurrences?</strong></p>
<ul>
<li>We have restored affected customer files as far as possible.</li>
<li>We have improved the firewalling in our network, so that customer web servers do not connect to our management database to get their configuration data.</li>
<li>We have undertaken a further precautionary password changing exercise.</li>
<li>We have planned additional work, to implement automated scanning for future attacks on our ftp servers and web servers.
</li>
<li>We implementing further partitions to our database security, so that web server configuration and ftp access are secured using different users.
</li>
<li>We have fed the lessons learned from this exercise into our web cluster redesign work, to improve the protection we give to customer websites.
</li>
</ul>
<p><strong>Conclusion</strong><br />
We would like to apologise to customers for any inconvenience this episode may have caused. </p>
<p>As you may know from following our blog, we are engaged in a program of evolving our email and web hosting infrastructure and problems like this highlight areas for improvement in our initial systems designs from a several years ago.</p>
<p>Finally, we would also recommend customers reset their FTP passwords, because, whilst they are encrypted in our database, there is the possibility that a 3rd party has a copy of that list, and they could be decrypted and used again.</p>
<p>This can be done online at: <a href="https://hosting.gradwell.net/login/ftpmanage?menu_req=75">https://hosting.gradwell.net/login/ftpmanage?menu_req=75</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/06/09/customer-ftp-and-website-security/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Gradwell Mail Infrastructure Rebuild</title>
		<link>http://blog.gradwell.com/2008/06/02/gradwell-mail-infrastructure-rebuild/</link>
		<comments>http://blog.gradwell.com/2008/06/02/gradwell-mail-infrastructure-rebuild/#comments</comments>
		<pubDate>Mon, 02 Jun 2008 13:02:37 +0000</pubDate>
		<dc:creator>Peter Gradwell</dc:creator>
		
		<category><![CDATA[General Blog]]></category>

		<guid isPermaLink="false">http://www.gradwell.com/company/blog/2008/05/27/gradwell-mail-infrastructure-rebuild/</guid>
		<description><![CDATA[We wanted to update customers on the progress with our email systems migration.
Customers will be aware that we are currently engaged in the process of building a completely new email infrastructure and migrating customers mailboxes from a number of different systems onto a single, consistent platform.
The challenge has been to build a cost effective email [...]]]></description>
			<content:encoded><![CDATA[<p>We wanted to update customers on the progress with our email systems migration.<br />
Customers will be aware that we are currently engaged in the process of building a completely new email infrastructure and migrating customers mailboxes from a number of different systems onto a single, consistent platform.</p>
<p>The challenge has been to build a cost effective email platform which would allow us to offer a high level of uptime and protection against physical server and disk failure, for our low cost email hosting products. We have built a system using multiple storage arrays, on top of a VMWare Server cluster and have nearly completed the migration process.</p>
<p>Our email system consists of front end servers, which handle the connections from customers, using imap, pop3 and the sending of email, using SMTP. We also then have the backend servers, which store customers email files.</p>
<p>To recap:</p>
<ul>
<li>We announced the plan in <a href="http://www.gradwell.com/company/blog/2007/12/21/server-plans-for-2008/">December 2007</a>, where we outlined the proposed developments for the first half of the year.</li>
<li>In February 2008, we completed the deployment of 15 new servers, handling <a href="http://www.gradwell.com/company/blog/2008/02/03/update-on-infrastructure-mail-voip/">pop3, imap and smtp</a>.</li>
<li>One of the hurdles for deploying the new IMAP platform was that customer mailboxes needed to be restructured, so we completed a restructuring project of the 43,000 mailboxes we host, which was completed by 9th May 2008. Customers were largely unaffected by this process, although unfortunately a small percentage of customers had to reconfigure their email programs.</li>
</ul>
<p>This completed the majority of the “front end” work, although we still have a handful of customers whom are logging into the old mail platform and we are going through the process of contacting those manually, to correct their settings.</p>
<p>The second phase of the project has been to migrate the backend of the system – the customers mailbox storage – to a more reliable storage platform.</p>
<ul>
<li>Previously, we put customers mailboxes on individual servers, however, this meant that it would take a long time to recover from a server crash and we were reliant on a single disk array.</li>
<li>Therefore, we adopted a high availability file system from Redhat (GFS), which provided excellent resilience, but at the expense of performance, and it is still reliant on a single disk array.</li>
<li>We have therefore migrated all customers mailboxes to a set of 9 file servers instances on top of our VMWare platform, which allows us to have quick recovery (sub 5 min) in the event of the operating system crashing, and, whilst the files are still stored on top of a single disk array, we can move them from one disk array to another with no down time.</li>
</ul>
<p>During this process, the migration of customers mailboxes has been exacerbated by:</p>
<ul>
<li>Slow performance and unreliability on old servers.</li>
<li>Capacity issues on our new VMware cluster, due to our accelerating the migration process, and licensing delays at VMWare, causing some of the new file servers to crash, particularly early in the morning, when the load has been highest.</li>
<li>The need to migrate over a terabyte of storage in fairly short time windows.</li>
<p>During this migration period in May, customers have experienced short periods of not being able to access their email whilst we adjusted settings and moved mailboxes for which we apologise.</p>
<p>As a third phase of the project, we have designed a redundant backend server, which allows us to store customer mail files on two independent disk arrays (potentially in two locations) with sub-1 minute level fail over, and we plan to test this in late May, before retrofitting it to our new storage setup in early June if successful.</p>
<p>At the end of May had the following short term work to complete, and <strong>as at 2nd June</strong>, this work is done:</ul>
<ul>
<li>We need to add servers and RAM to our VMWare cluster, to increase available computing power on the new mail cluster. <strong>Done</strong>.</li>
<li>Migrate the remaining 200 mailboxes from our Redhat GFS Cluster. <strong>Done</strong>.</li>
<li>Ensure all customers are using the new platform, and correct any old customer configurations. <strong>Done.</strong></li>
<li>Fixed an issue in the Linux Kernel, related to disk i/o timeouts under heavy load, which causes the file servers to crash. <strong>Done.</strong></li>
</ul>
<p>Finally, to take advantage of the new system customers should ensure they check their email from <strong>pop3.gradwell.net</strong> and use <strong>relay.gradwell.net</strong> as their outbound smart host.</p>
<p><strong>Outstanding Issues</strong></p>
<p>Out VMWare based solution is performing well, giving good speed and has resolved many of the issues customers were experiencing. However, a number of elements continue to need to be addressed Mid-Term.</p>
<ul>
<li>Implement the high availability solution for our storage servers, which we hope to complete by early July. We have a proof of concept in operation and are beta testing it (at 14th June).</li>
<li>Implement a multi-site VMware cluster, giving us multi-site redundancy, which will be complete for autumn 2008. We have ordered the redundant networking equipment required to do this (at 14th June) and expect it to be implemented by mid-August 2008.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.gradwell.com/2008/06/02/gradwell-mail-infrastructure-rebuild/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
