To program an effective virus for Linux is fairly difficult. It's much easier to provide malware disguised as an add-on, however. The Amarok project now wants to protect against that.

Linux users are pretty easy going when it comes to Internet dangers, which can lead to trouble, as was recently revealed in an incident of malware disguised as a screensaver. It's easy to lean back and say, "well, it's your own fault that you downloaded a binary package without first looking at the source code." But the more Linux users there are, the higher the rate that programs are downloaded and installed without much forethought. Security tests may be available, but require a lot of work in view of the magnitude of uploads.

One of the first developers to address this problem is Mark Kretschmann, who recommended a solution for the KDE music player that other projects could also adopt. Even Amarok is an easy target for these attacks. The attacker needs just to disguise one as a "cool" add-on, which Kretschmann claims, for example, could completely wipe out your home directory.

He suggests, therefore, immediately using a version control system (VCS) for all scripts and add-ons. This might increase the entry barrier for prospective Amarok developers, but the detour through a VCS provides a better protection against what Kretschmann calls "crapware" scripts, because all programmers will then know that their code is being reviewed. The scripts in version control can then be downloaded via the Get Hot New Stuff (GHNS) framework in KDE, where additional security measures can be applied. Even if an author manages to inflict malware into the code, the suspect checking it in can still be traced.

Apart from guarding against malware, a mandatory VCS has the further benefit of removing "abandonware" (such as code that was forked and is no longer maintained) or giving it to someone else to maintain.