Canonical, the commercial sponsor of the Ubuntu Linux, has said that compromises of most of its local community servers this week do not reflect on the distribution's security or enterprise-readiness.

The company said such criticisms were wide off the mark, since the affected servers were running old, unpatched versions of Ubuntu as well as a number of insecure web applications.

The compromises affected five of the eight Local Community (LoCo) hosting servers, which are sponsored by Canonical for the use of local-area Ubuntu developer communities but hosted outside the company.

Canonical was at pains to point out that the servers did not host downloadable software, but mainly news pages, blogs and localised documentation.

The problem came down to the fact that responsibility for the security of the machines didn't clearly belong to either Canonical or the communities using the servers. The systems were all located outside Canonical's own datacentre.

The problem first came to light on Monday evening, when Canonical received reports that one of the LoCo servers had been compromised, and an investigation found four more of the servers had been hacked.

"Since it was reported that they were actively attacking other machines... the decision was taken to shut the machines down," said James Troup, head of Canonical's system administration team, in a report on the breaches which was published on Ubuntu newslists.

The systems could have been breached in several ways, Troup said, since they were being accessed using FTP without SSL and were running more than a dozen web software packages, all of which were out-of-date and missing security patches.

What's more, the systems were running a version of Ubuntu Linux that is no longer receiving security updates from Canonical, meaning there was no way of fixing more recent security issues.

That's because more recent versions of the operating system failed to work with the servers' network hardware, Troup said.

"This probably allowed the attacker to gain root," Troup said.

The communities affected will have the choice - of moving their servers into the Canonical datacentre, where they'll be kept up-to-date but will have stricter limits on how they're used, or sticking with outsourced servers but taking on the full responsibility for administration.