You cannot have a science without measurement. | |
| R. W. Hamming |
Writing a program that inserts code into another program file is one thing. Writing that program so that it can be injected itself is a very different art. Although this document shows a lot of code and technique, it is far from being a "Construction Kit For Dummies". You can't build a working virus just by copying whole lines from this text. Instead I'll try to show how things work. Translation of infecting code to a assembly is left as a (non-trivial) exercise to the reader.
An astonishing number of people think that viruses require secret black magic. Here you will find simple code that patches other executables. It is not hard to write a virus (once you have a good understanding of assembler, compiler, linker and operating system). It's just hard to let it make any impact.
Regular users can't overwrite system files (at least under serious operating systems). So you need root permissions. You can either trick the super user to run your virus. Or combine it with a root-exploit. But since all popular distributions come with checksum mechanisms, a single command can detect any modification. Unless you implement kernel-level stealth functionality…
I do believe that free software is superior, at least in regard to security. And I strongly oppose the argument that Linux viruses will flourish once it reaches a critical mass of popularity. On the contrary I question the credibility of people whose income relies on widespread use of ridiculously insecure operating systems.
This document is my way to fight the FUD. [1] Use the information presented here in any way you like. I bet that Linux will only grow stronger.
All sections titled "Output" are real product of source code and shell scripts included in this document. Most numbers and calculations are processed by a Perl script parsing these output files. The document itself is written in DocBook, [2] a SGML document type definition. [3] Conversion to HTML is the last step of a Makefile that builds and runs all examples.
I worked with an installation of "Red Hat Linux release 7.2 (Enigma)". [4] The freely downloadable CDs [5] contain all used tools: bash-2.05-8, bc-1.06-5, binutils-2.11.90.0.8-12, file-3.35-2, findutils-4.1.7-1, gcc-2.96-98, gcc-c++-2.96-98, gdb-5.1-1, glibc-2.2.4-24, make-3.79.1-8, nasm-0.98-8, perl-5.6.1-26.72.3, util-linux-2.11f-17
This document is not yet officially accepted by LDP. You might want to look at the discussion on LDP-discuss. [6] For the time being you will find the document at the sites listed in appendix Mirrors.
This document, The Linux Virus Writing HOWTO, is copyrighted (c) 2002 by Alexander Bartolich.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1, or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts.
All accompanying source code, build scripts and makefiles is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
All copyrights are held by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark.
Naming of particular products or brands should not be seen as endorsements.
No liability for the contents of this documents can be accepted. Use the concepts, examples and other content at your own risk. As this is a new edition of this document, there may be errors and inaccuracies, that may of course be damaging to your system. Proceed with caution, the author does not take any responsibility.
All software is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.
Who am I kidding? This is dangerous stuff! Stop reading immediately or risk lethal pollution of your systems!
You are strongly recommended to take a backup of your system before major installations and backups at regular intervals.
Everything in this document is either plain obvious or has been written by someone else long time ago. My meager contribution is nice formatting, reproducibility and the idea to take the subject to mainstream media. But I'm certainly not innovative.
Silvio Cesare <silvio@big.net.au> Founder of the trade. Keeper of the source. [7] Admire the release date.
John Reiser <jreiser@BitWagon.com> Found one bug and two superfluous bytes in In the language of evil. Proved that I can't code a straight 23 byte "Hello World".
paddingx Contributed technical details and implementation for Additional code segments and Doing it in C.
Rick Moen <rick@linuxmafia.com> Has a very inspiring site. [8] And I shamelessly quote him in the abstract.
A lot of people helped me shape language and ethical position of this document (sorted by perl(1), blame Larry): Charles Curley, Dave Wreski, David Merrill, Gary Lawrence Murphy, Greg Ferguson, Harald Wagener, Ian Turner, Marinho Paiva Duarte, Martin Wheeler, QuickFox of kuro5hin, Steve Sanfratello.
Feedback is most certainly welcome for this document. Please send your additions, comments, criticisms, flames and "contributions" to the following email address: <alexander.bartolich@gmx.at>
A few people sent me executables for that other operating system. I am very grateful for this kindness. But you should know that this document is about Linux only.
| [1] | |
| [2] | |
| [3] | |
| [4] | |
| [5] | |
| [6] | |
| [7] | |
| [8] |