Linux.Darlloz worm ei ole Linux-mato vaan...

...PHP-mato. Tämä tiedoksi niille tolloille jotka tulevat tänne lähipäivinä väittämään että maailmalla on nyt löydettä ensimmäinen laitteista toiseen leviävä vaarallinen "Linux-haitake".

The original article (and others, similar) are IMHO irresponsible for a couple of reasons, not limited to:
1) The vulnerability (if it may even be called that) is NOT a gnu/linux vulnerability, its a PHP vulnerability.
2) The vulnerability affects a very limited subset of server types and DOES NOT affect most users on the net, nor most users who will read the article.
3) The vulnerability is NOT in the wild, is more hypothetical than real, and is not likely to be a problem across the boards. (most new routers, even home routers, are not going to be affected by this PHP vulnerability.
4) This article (and others, similar) are written to affect users with fear, uncertainty, anddoubt. It is time for FUD writing to come to a complete halt.
5) This vulnerability (if it may even be called that) is NOT a linux vulnerability... it is a server vulnerability in PHP... (it has absolutely nothing to do with linux (the kernel). This vulnerability is based in PHP, is hypothetical, and is a vulnerability on any server platform with the PHP extensions to the web server on that platform... this is not a gnu/linux , nor linux, vulnerability.

I will also add, that the vulnerability is supposed to work because of "well known" userid and password "path(s)" on the linux system... how silly! Almost every distribution handles the "path(s)" as well the userid and passwords for security, and safety (no worm is going to be able to read it). Also almost every distribution (including embedded systems) handle this issue "differently," meaning that wide-spread propagation of such a "vulnerability" is not realistic.

The original article is mostly just Symantec noise.

The original article (and others, similar) are IMHO irresponsible for a couple of reasons, not limited to:
1) The vulnerability (if it may even be called that) is NOT a gnu/linux vulnerability, its a PHP vulnerability.
2) The vulnerability affects a very limited subset of server types and DOES NOT affect most users on the net, nor most users who will read the article.
3) The vulnerability is NOT in the wild, is more hypothetical than real, and is not likely to be a problem across the boards. (most new routers, even home routers, are not going to be affected by this PHP vulnerability.
4) This article (and others, similar) are written to affect users with fear, uncertainty, anddoubt. It is time for FUD writing to come to a complete halt.
5) This vulnerability (if it may even be called that) is NOT a linux vulnerability... it is a server vulnerability in PHP... (it has absolutely nothing to do with linux (the kernel). This vulnerability is based in PHP, is hypothetical, and is a vulnerability on any server platform with the PHP extensions to the web server on that platform... this is not a gnu/linux , nor linux, vulnerability.

I will also add, that the vulnerability is supposed to work because of "well known" userid and password "path(s)" on the linux system... how silly! Almost every distribution handles the "path(s)" as well the userid and passwords for security, and safety (no worm is going to be able to read it). Also almost every distribution (including embedded systems) handle this issue "differently," meaning that wide-spread propagation of such a "vulnerability" is not realistic.

http://www.itworld.com/open-source/384754/linux-worm-wriggles-its-way-routers-cameras-and-other-devices