---------------------------------------------------------------------                                  TES Presents                 ----------------------------------------------                 - What To Look For In A Code Hacking Program -                 ----------------------------------------------                              written by Dissident     Phreaking's getting tricky these days, ain't it?     Ok, there are two groups of things a code hacker should have, thenecessities and the things that are good to have...  Here are the necessities:     Mutliple ports.  If you constantly try to hack from the same port (the800/950 or whatever number that the company you're hacking from is on) youare begging to be caught.  The program should have an option to handle atleast 5 different ports.  It should also be able to handle a different formatfor each one if necessary. (One could require nine digits, another only 4, another requiring a 9 before the place you're trying to call to, etc)     Multiple targets.  The program should be able to handle as manytarget numbers as it can ports.  If everytime you try a code you go to thesame number you are, again, begging to be caught.     The ability to hack codes RANDOMLY.  And when I say random, I mean goingas far as to have a different seed each time it generates a random code...If you hack sequentially I hope you get caught.     Not only should the codes it tries be random, but almost everything aboutthe program should be random.  It should pick a random port, with a randomtarget, and with a random code.  Believe it or not, some companies are startingto show some intelligence, and they're beginning to notice patterns. . .You can't predict chaos, remember that.     The ability to stop after a certain number of tries, or a certain numberof successful codes, or at a certain time.  If you let the hacker run for along time, you better have a LOT of ports and targets set up...  Hack forshort periods of time, or for a relatively small number of tries.  If youget impatient and desperate for codes, you will make mistakes.          And now, the nice things to have.     The ability to have a random delay between the tones it dials.  Humanscan't dial 11 digit numbers in .7 of a second, and the companies know that.Humans also cannot dial with a consistent gap between each tone.  If theprogram puts a random time between each tone, the system will have a betterchance of thinking you're a human.     The program SHOULD be able to encrypt all of the codes it hacks when itsaves them/prints them/etc.  That way, IF you get busted, you won't have somuch evidence against you.  When you get nailed, they go through everything,even if they are idiot schmucks.  If your list of codes contains all 'wrong'codes, they'll have less of a case against you.     It is also nice if the code hacker waits a random length of time betweenattempts, no matter how many ports it is trying.  If you're hacking randomports, with random targets, with a random delay between digits dialed, with arandom amount of time between all of your attempts, and with a randomlygenerated code, you're going to be hard as hell to catch.     And now some warnings. . .     I don't know if it is a COMMON practice, but some companies have set upbad accounts (codes, whatever) for the specific purpose of catching whoevertries to use it.  If it doesn't belong to a real person, only a hacker wouldget it.     Don't hack fast...  If at all possible, dial fairly slowly.  I've heardof places that watch for extremely fast dialers.     Don't phreak to the same place with the same code constantly.  I feelthat one is self explanatory.     If you're very cautious, you can always use someone else's line when youare searching for codes.  But be SURE you don't leave anything that can pointto you.     If you think there is a chance that you've been snagged, or at leastcaught the attention of the Gestapo, stop phreaking.  The less stuff theyhave against you, the less of a case they'll have against you.  Also, if youkeep phreaking, they'll sooner or later shove a printout in your face thatcontains every number dialed from your phone.  Don't bring everybody else downjust because you got careless.     Speaking of bringing everyone else down...  I don't know if the truth hasbeen out yet, so I'll bring it out.  There was a loser by the name of JeremyHall.  His common handles were "Quicksilver" and "Shells".  He thought he washot shit.  He set up many Alliance conferences, called up Voice Mailboxes almost everyday, etc.  He was about 13 years old, a little whiny brat.Well, there was also a damn good phracker by the handle of Amadeus.  Everwonder what happened to him?  Quicksilver turned him in to save his own ass.He also caused alot of Mailboxes to come down, and I think a few boards camedown because of his ignorance.Just thought I'd mention that for those who knew Amadeus or Narcsilver.(BTW-Narc:615-647-8019  724 York Road  Clarksville, TN 37042 Various programs with code-hacking functions written by members of TES- Commcracker and Coax - written by Cronus HAMR, HAMR 2.0,HAMR128 - written by Dissident CHOMPS under development - Cronus CHOMPS-Amiga also under development - Dissident All of the above except for HAMR 128 and CHOMPS Amiga were written/are beingdeveloped for Commodore 64s...  Commcracker/Coax/HAMR require 1660 modems,the rest will work with Hayes Compats.--------------------------------------------------------------------------