home *** CD-ROM | disk | FTP | other *** search
-
-
-
- /-/yper(rypt: Cryptography for Hackers/Phreakers & Others
- =========================================================
-
- Version 1.10, Released 03/19/92
-
- Written By Professor Falken
- Copyright (c) 1991,1992
-
-
- [ NO NEW DOCUMENTATION AS OF v1.10 RELEASE OF HYPERCRYPT ]
-
- /=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\=/=\
-
-
- INTRODUCTION:
- ------------
- HyperCrypt was written with the Hacker, Phreaker, Pirateer and Almost
- Average Joe in mind. Its purpose is to extend highly secure cryptographic
- systems to the end user of the program.
-
- I decided to write THIS program because I felt there was an inadequate
- supply of encryption utilities out there. Let me explain, the encryption
- utilities that were in the public domain (Fred Fish & Copyrighted)
- either employed insecure encryption algorithms or the key (password)
- length was much too short to make cracking it hard. Unlike those previous
- programs, and the hordes of other programs which follow in their footsteps,
- I am proud to release a highly secure, command-lined, low memory overhead,
- and portable cryptographic tool.
-
- The files you wish to encrypt can be really anything. A list of
- telephone numbers, friends names, passwords for various systems,
- technical notes, where you hid the dead body etc. You can really
- encrypt anything.
-
- DIFFERENT VERSIONS:
- -------------------
-
- There are three different versions of HyperCrypt included in this
- release. They are:
-
- hc1 - The 68000 Optimized Version
- hc2 - The 68030 Optimized Version
- hc3 - The 68040/68881 Optimized Version
-
- So if you have a '030 or '040 please use the CORRECT version,
- you should see an small increase in the speed of HyperCrypt.
-
-
- USING THE E (Encryption) and D (Decryption) SWITCHES:
- -----------------------------------------------------
-
-
- To encrypt a file with HyperCrypt specify which file will be the
- INCOMING file(Usually the one with all the secret shit in it). Then
- specify what the OUTGOING filename should be. For instance, I wish to
- ENCRYPT a file called TELEFONE.DOC, I will use "fatcuntwhore" as my
- password. I suppose I will output the ENCRYPTED text to a file called
- TELEFONE.ENC Here's how its done:
-
- CLI: hc telephone.doc telephone.enc fatcuntwhore E
-
- OK, so now you have this nice file called TELEPHONE.DOC which looks
- so messed up, if you didn't know better, you'd swear its the face of
- your neighbors crack-smoking child.
-
- Make sure you take a non-related file such as sys:c/ED and copy it
- over your original INCOMING file. Make sure you copy it to the same
- name, so that the original is totally written OVER, and there is NO
- way of UNDELETING your data. THEN ERASE your original file(It should
- now actually be ED).
-
- So, after an amount of time elapses you decide you need a telephone
- number out of that file. No problem. Enter:
-
- CLI: hc telephone.enc telephone.dec fatcuntwhore D
-
- Now, you can read TELEPHONE.DEC and get the phone number you need.
- But, if you noticed, I used a DIFFERENT filename for DECRYPTING the
- file. The reason for this is just in case I fucked up the KEY and
- it OVERWROTE my encrypted file with the incorrect decrypting KEY.
- So when I check out telephone.dec and see that it is FINE! I can then
- rename telephone.doc to something else, copy some bullshit file over
- its place, then erase it. See that way no one will be able to match
- your enciphered text with your deciphered text and figure out your key.
- See how easy it was?!
-
-
- PASSWORD LENGTH:
- ----------------
-
- In the past there has been a tendency among users of cryptographic
- systems to use a word or a name as a key. Today this procedure is
- VERY unsafe. There are a fewer than a million words in an unabridged,
- and fewer than a million names in the largest telephone directory.
- That number of potential keys could be tested in a few minutes on a
- powerful computer of today. Even the use of eight randomly chosen
- ASCII characters is unsafe. If a key is introduced directly, it should
- consist of 16 or MORE ASCII characters (IE- A-Z,a-z,0-9,and punctuation
- combinations) Sometimes making LONG passwords is about as much bother as
- it will be for someone trying to break it. Here are some ideas for
- making up these LONG keys:
- 1. Sentences from books.
- 2. Phrases from obscure songs.
- 3. TV/Radio Commercials.
- 4. A column from an old newspaper.
- 5. Make up a short story.
- 6. Make faces with the ASCII chars. :0 :) ;) etc.
-
- I'm sure you can think of other things to write about, like maybe
- your first screw, but that may too personal, incase someone breaks it.
-
- ALSO make sure you PROPERLY dispose of the ENCRYPTED filename, that
- you just decrypted. First copy a file over, then another, then to be
- safe, copy another, then rename the fucker, THEN erase the SOB.
-
- It would also be nice to have this program setup in your PATH.
- So that you can encipher stuff all over your harddrive! When the nice
- men in jackets come to borrow your computer don't let them have all
- your data that easily.
-
- CONCLUSION:
- -----------
-
- This documentation is A LOT longer than I intended it to be. Oh well,
- you should be able do discern how to run the thing from the previous
- text and the small example built into the program.
-
- I would now like to thank Infinite Perfection for releasing
- this product on their intercontinental distribution system. I really
- helps a program when it has access to a WIDE dispersal network. Again,
- thanks IP.
-
- Word to PARADISE!- Dudes you most haneously FUCKED UP the Killer
- Cracker release version. First you fucked up the name and called it
- Killer Hacker. Second of all you claim "BY PARADISE" which I highly
- doubt any of your codes could write such complex code. And Third of
- all, it was FUCKING .DMSed!!! DMSed to a disk with no working
- (IE-dir) shell. Dudes, if that is what U call a release, shit no
- wonder your not #2. Anyway, I still appreciate your fucked up job
- of distributing the product, but I think I'll stick to IP from now on.
- In fact, there will be a re-release of KC under IP.
-
- MANY MANY thanks go out to Alpha-Flight for their FUCKING
- execellent job of converting Killer Cracker over to German,
- MANY thanks to AFL for that. Now all the German hackers will be happy.
-
- Many thanks go out to my BETA-Testers, Wintermute(713), and
- Stryker(612). If it wasn't for BETAs there would be a BUGGY program.
-
- Anyhow, greets go out to: All X Legion of Doom members hanging out
- and around, P/H/A & Doctor Dissector (KC3.0 is the BEST!), Prometheus,
- Sir Hackalot, Ex-Phortune 500s UNITE!, Shawn-Da-Lay Productions -
- Wheres the NEW version of Telix Hacker?!!, Brew Associates Where RU?,
- L.E. Pirate(What happened to Dragonfire?!oh no)(What Cult of the Dead
- Cow?), The Rebel(716), 2600 Magazine(About time I get that damn
- subscription information-1.5 months later), Phrack Magazine, Mondo 2000
- Magazine (Wheres my subscription fuckers?), Twisted Sector, The Ranger,
- The Viper, Slavelord, ANARCHY!, and all the others who give me phree file
- points... Not that I am partial to people who give me free points or
- anything.(haha)
-
- And for EVERYONE who I left out- YOU TOO!
-
- Amiga programs released to date:
-
- 1. CNA Inquiry v1.x (1991)
- 2. TCK-Tear v1.x (1991)
- 3. Killer Cracker v2.x (1991)
- 4. HyperCrypt v1.x (1991)
-
-
- - Professor Falken
- = Ex-Legion of Doom!
- = Ex-Phortune 500
-
- HyperCrypt - Version 1.00
- Written by The Aptolcater & Professor Falken
- Copyright (c) 1991 Released by Infinite Perfection
-
-