Raising Hell with Unix, Komputer, More Hacking
[ Pobierz całość w formacie PDF ]
* Data Kult * ����������������� * Kryptic Night *Lord Logics �� Raising �� Bounty HunterShadow Walker �� Hell �� Nacht Habicht- S M C - �� with Unix �� - S M C -Realm of Infinity ��Kryptic Night�� The Viking's Den(503)629-0814 ����������������� (408)867-1224SMC Home - S M C - Western Dist.Production # 3����������������������������������������������������������������������������I - IntroductionThis file will describe several ways to cause mischief on a Unix system.Like the other SMC Productions, I will try to present the information at abeginners level. However, all levels of hackers should benefit in some wayfrom the information contained within. And now... on with our show...II - How To Fill a Hard DiskThere are several ways to cause havoc by filling up a systems harddisk. Filling up a hard disk will make it so that the system cannot createthe temporary files vital to it's efficient use. It will also cause otherproblems, such as a person trying to save a 10 page financial report, andfinding that there is no room for it. Also, if the HD is full, the systemwill not run properly. You will be bombarded by a continuous stream of'write failed, file system is full'. Over all, this is a very good way topiss people off.Step OneCreate the following file with the 'ed [filename]' utility under thebourne shell, or the 'edit [filename]' under the C shell. The filename canbe whatever you want, here I will call it 'hah1'. Only type in what iscontained within '[]'s, the other text is what the system will send toyou.$[ed hah1]*[a][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][echo Hahahahahahahahahahahahahahahahahahahahahah!!! >> -fucku!][nohup hah1 &][^C]*[w]754*[q]$[chmod +r+w+x hah1]$[nohup hah1 &]1234$This will create a file called '-fucku!'. Files beginning with a '-'are very difficult to delete, as when you try to do a 'rm -fucku!'<rm - remove file> It interprets the '-f' as an option, it tries thento force delete the file 'ucku!'. As you can imagine.... this wouldn'tquite work. The text after the echo can be anything you wish, I justused a sample text that is quite pointless and takes up space. The numbersrepresent the file size, and process number, they will be different onyour system.The file will add the text from the echo statement to the file '-fucku!'until it reaches the 'hah1 &' command, which will make it start over again.This is an endless loop. For as long as you are on-line, and their areprocesses left, the file will continue to add to the file. This is avery slow method, but it's easy if you are starting from scratch. Ifyou get a message such as 'cannot fork hah1: process terminated' that meansthat the loop is taking up so much memory that the system can no longercontinue with that job. Don't worry, it will settle back to normal after allthe processes are eventually killed, if it does, continue to run the filein the background until you have a '-fucku!' file that is about 100-200klong, this will allow us to progress to our next step.The command 'nohup hah1 &' tells unix to continue to run the 'hah1'in the background, even after you hangup. This means you can run theprogram, hang up, and call back. This function will only work underthe bourne shell. If you have a prompt of '$', then you are using thebourne shell. This function will become exceedingly useful when westart with the next step.The command 'chmod +r+w+x hah1' will make the file readable, writable, andexecutable by you. This string may or may not be necessary on the system youare using. If you get a message such as 'hah1: Permission Denied' than youwill need to use the chmod command. And now onto the next step...Step TwoWe will now explore the ever powerful 'cat' command. The 'cat' commandis the equivalent of the MS-DOS 'type' command. We will use a functionof the unix system called redirection that will allow us to 'cat' filesinto each other. This will cause the source file to be copied to the endof the destination file, I'm sure you're beginning to see the mischiefyou can cause with this.To begin with, create a file called '-fucku2' the same way you createdthe '-fucku!' file. Try to run the 'hah1' program until the new 'fucku2'file is around 100-200k also. This isn't absolutely necessary, but it'shelpful and saves some time.Next, create the following file with the editor <'ed' or 'edit'>.I will call it 'hah2', but you may call it whatever you wish.$[ed hah2]*[a][cat -fucku! >> -fucku2][cat -fucku2 >> -fucku!][nohup hah2 &][^C]*[w]61*[q]$[chmod +r+w+x hah2]$[nohup hah2 &]7049$What we've just done is create a very short, and very nasty, programthat can fill 20 megs in under 5 minutes. The file when run will add thecontents of '-fucku!' to the end of '-fucku2', and do the reverse. Thismeans that when you have two files of 100k to begin with, you will getthe following results after every completed loop...-fucku! .. -fucku2 .. -fucku! .. -fucku2100k >> 200k >> 300k >> 500k700k >> 1200k >> 1900k >> 3100kAs you can see, the file grows VERY quickly. Set it up in the morningbefore school, come back and the HD should be completely full. You maywish to also run multiple write processes, just to confuse the system.If you do, rename the files to something appropriate, but maintain thebase content. If you do it in several directories, the sysop will haveto do some serious cleaning to get rid of it.Step ThreeSit back and laugh. If you wait awhile, in approximately 30 minutes,the average 40 meg hard drive will be full. I've tested this method onseveral systems, even an ancient VAX, and the results were more or lessthe same. The sysop, or any other user, will be able to write anythingonto the system until this problem is resolved. Many programs needto create temporary files to even operate. These programs are nowcompletely unusable, except for the few that save to memory. To deletethe files, the sysop will have to do one of several things, all of whichare very unpleasant. And now for the next lesson...III - MischiefThis section will describe a couple of ways of perpetrating mischief on aunix system. These ideas are for the most part harmless, but can definitelypiss people off. The idea of a continuous subdir was molded from onepresented by Shooting Shark.Idea #1This method will create an endless amount of directories under athe current directory. Create multiple files with different name anddirectories to really annoy the 'sop. Type the following to accomplish this.$[ed sub1]*[a][mkdir -FuCkU!1][chdir -FuCkU!1][/xxx/xxx/sub1 &][^C]*[w]69*[q]$[chmod +r+w+x sub1]$[nohup sub1 &]7099$This program will create a directory called '-FuCkU!1', change to thatdirectory, then create another one under the first one, and so forth. Itis an endless loop, and will continue virtually forever. The third lineof the program contains a string '/xxx/xxx/sub1 &'. You will need to fillin the x's with your current directory. To find out your current directorytype 'pwd' this will print a string telling which directory you are in.Fill in the x's with this data. The rest of the program you should be ableto figure out by now. Try it, you'll like it.Idea #2So, you've seen someone on the system that you really don't like? Or doyou just want to piss someone off? This methods for you. This method willdescribe a way to send out data to another user, or terminal. Here is whatyou will want to type to create a file to anger the other user.$[ed beep]*[a][echo ^G ^G ^G ^G Wheee!!! ^G ^G ^G >> /dev/xxxx][nohup beep &][^C]*[w]25*[q]$[chmod +r+w+x beep]$[nohup beep &]8002$Fill in the '/dev/xxxx' with the terminal you want to annoy. To find outthe terminal of the person you want to fuck over, type 'who' it will printout something like this....$[who]guest ttyd0 Nov 30 19:06root console Nov 30 19:20Bendover ttyd5 Nov 30 18:45$The first column is the name of the user, the second column tells uswhat terminal they are logged on as, and the third states at what timethey logged on. The second column is what we need right now. Fill in thex's with the terminal that you wish. If you wanted to bother the root, youwould type '/dev/console', to bother guest type '/dev/ttyd0'. To bothermore than one terminal, just add another line after the first 'echo'statement with a different terminal identifier. With the 'nohup' command,the computer will send a continuous outpouring of beeps until he logs offor reboots the system. Try it on the terminal you are logged on under tosee exactly what it does.���������������������������������������������������������������������������IV - ConclusionThese projects should be enough to get you started on your road to UnixHell. With a li...
[ Pobierz całość w formacie PDF ]