▄ ▄▄▄
▄▀▀ ▀ ▀▀▄
▐▌ ▐█
_ ▀█▄▄▄▄ ___ __________ _ ▄ __________ _ ▄ ______ _ ▄▄█▀ _
▀▀▀▀█████▄▄▄▄ ░ ▄▄▄▄▄█▄ ██▄▄▄ ▄▄█▌ ▄ ▄███▓░
▄▄████▄▄▄ ▀▀█████▓▄ ▄▄▄███▀▀▀▀██████▐██████▄ ▄██████▄██████▄ ░▓████▌
▐██████ ▀████▄█████▄ ▐█████▀████████▄███████▓▐████████▄ ▐████▓░
▐██████ ▐███▌█████▓░ ▄▄▄██████▌██████ ▀█▀ ██████▌██████ ▀██▄▐████▌
▐██████ ▄████░▓██████▀▀▀▀██████▌▓█████ ██████▌▓█████ ▀██████▓░
▄▄▄▐█████▓ ▄▄ ▄▓████▌▐██████ ▄▄▄ █████▓▐█████▓ ▄▄▄ ▒█████▐██████ ▄▄▄▐██████▌▄▄▄
██████▌▓▓▐█████▓░▐██████ ▓▓▓░▓█████▐██████▌▓▓▓ ▐████▓▐█████▒ ▓▓▓ █████▓░
██████▌▒ ▓██████▌░▓████▓░▒▒▒ ▐████▌░▓█████▌▒▒▒ ▐████▌ ██████▌ ▒▒ █████▌
░▓█████▌░ ▐██████▒ ░▓████▌░░░ ▐███▒ ░▓████▌░░░ ▐███▓░ ▒█████▌ ░░ ▓████▌
▀▀▀█▀▀████▄███████▌ ░▀███▌ ░ ▄██▀▀ ░▀███▌░ ▄██▀▀░ ▀▀▀█▀▀▀▀▀░ ▐████▓░
_ ________ ▀▀▀▀▓███▓░ _ ▀▀█▄ ▀ _sRT!CRo_ ▀▀█▄ ▀ ___________ _ ▄▄██▓▀▀░ _
░ ░▀██▌ ▀ ▀ ▄█▀ ░
░ ▐█ ░ ░ ▐▌ ░
░ ▀▄ ░ ░ ▀ ░
░ ░
░ ░ ░
░ PRESENTS
░ ░ ░
░
░ FineCrypt v2.1 *Keymaker.Only*
▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄
╒══════════════════╕ ╓─ ──── ─ ──══── ─ ────── ─ ────── ─ ──══── ─ ──── ─┐
┌─┤▌ RELEASE INFO ▐├─╜ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ └┐
█ ╘══════════════════╛ █
█ █
█ [ Program .......................................... FineCrypt v2.1 ] █
█ [ Type ........................................ Encryption software ] █
█ [ OS ...................................................... Win9xNT ] █
█ [ By .......................................... Crypto Systems Inc. ] █
█ [ Homepage ............................... http://www.finecrypt.com ] █
█ █
█ [ Cracked by ........................ Ivanopulo ] █
█ [ Release type .................. Keymaker.Only ] █
█ [ Release date ................... Apr 01, 2000 ] █
█ █
└┐ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ┌┘
│╒══════════════════╕ ╓─ ──── ─ ──══── ─ ────── ─ ────── ─ ──══── ─ ──── ─┤
┌┴┤▌ DESCRIPTION ▐├─╜ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ └┐
█ ╘══════════════════╛ █
█ █
█ Many well-known cryptographers have published practical advice on how █
█ to distinguish an enhanced cryptographic product from so-called snake █
█ oil. Some products meet these requirements, others do not. But all of █
█ them are the same in one respect: they are all black-boxes for the █
█ user. On one side (input) of this black-box the user enters so-called █
█ plaintext (data that can be read and understood without any special █
█ operations) and on the other side (output) the user receives █
█ ciphertext. All the things that happen inside the black-box remain █
█ unknown to the user. █
█ █
█ If you take a look at the ciphertext resulting from the work of any █
█ program that can be considered cryptographic, you will see the same █
█ gibberish. Knowing an algorithm such as CAST, IDEA, Blowfish, etc. █
█ used by a particular program helps you to determine the level of █
█ security that can be achieved using this black-box. But how can you █
█ find out for sure what algorithm is used if all of them produce █
█ similar (but not the same) gibberish? █
█ █
█ Many people today do not believe software developers when they claim █
█ that they use (and use correctly) a secure encryption algorithm in █
█ their product. Users do not trust such statements concerning the █
█ safety of their data (which is sometimes very valuable). Widely █
█ published source code of the program usually helps to understand the █
█ principles of its functioning. Even those people who are not capable █
█ of professionally reading and evaluating this source code by █
█ themselves may trust the opinion of many professionals who do not █
█ find any weak links in this code. Then why, as we mentioned above, █
█ cant we find cryptographic programs that are not black-boxes for most █
█ users? Here is the most interesting thing. You can only be guaranteed █
█ that the program functions adequately to its published source code if █
█ you compiled the source files and got executable files by yourself. █
█ Otherwise a complex method of reverse engineering must be applied. █
█ (This is a complex method because if you could understand with the █
█ help of reverse engineering how the program works, then the source █
█ code publishing would be pointless. Furthermore, after you check one █
█ copy of a program with the help of reverse engineering you cant be █
█ sure that another downloaded copy will function in the same way). Why █
█ would the installation files downloaded from a corporate Internet █
█ site differ (even small differences are significant) from their █
█ published source code? █
█ █
█ There are many possible reasons for this. We will give you just one █
█ of many examples. Imagine that a computer intruder or interested █
█ organization downloads the source code of a cryptographic program, █
█ changes it so that it starts to use 40-bit key instead of 128-bit key █
█ and builds changed source code into an executable program. Then they █
█ crack the corporate site, introduce their own installation set █
█ instead of the original set and then successfully decipher any █
█ messages that are encrypted by this changed program with the help of █
█ easy 40-bit key. The changes in the program may be so subtle that █
█ even professionals will have difficulty catching them. █
█ █
█ How then can you determine whether the encryption performed by a █
█ certain program is secure or not? By comparing the plaintext at the █
█ input and the ciphertext at the output with some patterns that are █
█ offered by the developers of software you can receive a guarantee █
█ that encryption performed by the program is adequate to the source █
█ code and that the key is of the stated length. Considering the █
█ mathematical complexity of transforming plaintext into ciphertext, █
█ which is performed during the encryption, it is practically █
█ impossible to find the method other than by implementing this █
█ algorithm to transform two plaintexts into two ciphertexts fully █
█ adequately to the authorized samples given by the authors of the █
█ algorithm. FineCrypt offers you a method of ensuring that your █
█ information is protected the way you want it to be. And you do not █
█ need to have programming or encryption experience in order to see █
█ this. █
█ █
└┐ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ┌┘
│╒══════════════════╕ ╓─ ──── ─ ──══── ─ ────── ─ ────── ─ ──══── ─ ──── ─┤
┌┴┤▌ INSTRUCTIONS ▐├─╜ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ └┐
█ ╘══════════════════╛ █
█ █
█ Run the keymaker and register the program. █
█ █
█ Enjoy =) █
█ █
█ PLEASE NOTE: Straight after you type your registration information in █
█ the program and press OK 'About' dialog will still show 'UNREGISTERED █
█ COPY' message.. Must be minor bug in the program's interface or smth █
█ like that... Don't worry, just press OK. It'll show 'Registered to: █
█ ' next time you open it. █
█ █
└┐ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ┌┘
│╒══════════════════╕ ╓─ ──── ─ ──══── ─ ────── ─ ────── ─ ──══── ─ ──── ─┤
┌┴┤▌ GREETINGS ▐├─╜ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ └┐
█ ╘══════════════════╛ █
█ █
█ Our greetings fly to all groups and crackers who work hard to keep █
█ the Scene alive. █
█ █
█ Personal greetings to: Dimedrol, russ97, egis. █
█ █
└┐ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ┌┘
│╒══════════════════╕ ╓─ ──── ─ ──══── ─ ────── ─ ────── ─ ──══── ─ ──── ─┤
┌┴┤▌ CONTACT ▐├─╜ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ └┐
█ ╘══════════════════╛ █
█ █
█ Visit our www site at [ http://www.damn.to ] █
█ Backup page [ http://damn.da.ru ] █
█ █
█ Email address for contacts [ [email protected] ] █
█ █
└┐ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ┌┘
└─ ────── ─ ──══── ─ ────── ┬ ────── ─ ────── ┬ ────── ─ ──══── ─ ────── ─┘
│▌ (c) 2000 DAMN ▐│
└ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ┘