Home opinion-and-analysis Open Sauce Linux kernel project servers compromised

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

A number of servers at the Linux kernel project have been breached, according to an advisory at the kernel.org website.


Entry was gained via a machine that goes by the name of Hera.

The breach was discovered on August 28 and, while the kernel team believes the source code repositories were not affected, investigations are underway to check and also to bolster security across the project infrastructure.

Update, September 1, 1.35pm AEST: The British technology news site, The Register, reports that the intrusion went undetected for 17 days. This is based on an email it obtained which was sent to developers by John Hawley, the chief sysadmin of kernel.org.

The breach is believed to have occurred via a compromised user credential; how the attacker or attackers used that to gain superuser status is not yet known.

The attacker(s) had modified ssh files (openssh, openssh-server and openssh-clients) and these were running. In addition, a trojan startup file had been added to the startup scripts on Hera.

The kernel team has logged user interactions as well as some exploit code.

The trojan was initially discovered due to error messages apparently coming from a package, xnest, that was not installed; if similar behaviour was observed elsewhere developers were advised to investigate. However the presence of such messages did not make it clear that the machine was compromised, susceptible or not.

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect