氨槽鄄卑辈圹鄄膊膊膊膊膊膊膊膊膊膊膊膊膊膊膊膊槽圹脖氨槽鄄卑 氨槽鄄卑辈圹鄄脖北北北北北北北北北北北北北北北辈槽圹脖氨槽鄄卑 氨槽鄄辈圹鄄脖卑鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍氨辈槽圹脖槽鄄卑 氨槽鄄圹鄄脖卑 鞍北膊圹鄄圹脖 氨槽圹鄄脖卑 S - D U N G E R 9.9+ 鞍北膊圹圹脖 氨槽鄄脖卑 The Final N-Coder 鞍北膊圹脖 氨槽鄄脖卑 Julius "?" Thijssen 鞍北膊圹脖 氨槽鄄脖卑 Hens "maniac" Zimmerman 鞍北膊圹脖 氨槽鄄脖卑 the men with a plan 鞍北膊圹脖 氨槽鄄脖卑 鞍北膊圹脖 氨膊鄄脖卑鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍氨辈槽膊卑 氨辈槽膊北北北北北北北北北北北北北膊鄄脖卑 氨辈膊膊膊膊膊膊膊膊膊膊膊膊膊膊膊脖卑 鞍北北北北北北北北北北北北北北北鞍 SINCE YOU ARE NOW OWNER OF THIS EXCLUSIVENESS, WE STRESSFULLY URGE YOU TO READ (AND PRINT) AS MUCH AS POSSIBLE OF THE FOLLOWING. - THE S-DUNGER EN-/DE-CODES FILES IN A 100% UNBREAKABLE WAY! WE G U A R A N T E E THAT IT IS NOT POSSIBLE (FOR HUMANS) TO CRACK A FILE THAT HAS BEEN SCRAMBLED WITH SDU.EXE as long as you follow the instructions given in this file. - We've had questions about a program with a similar name, and we can only say that OUR first S-D.EXE was already there in 1985 and we didn't know about any other at that time. We always thought we were first with the name, or at least with a scrambling level of this order. Due to this name-conflict we've decided to change the name of the executable into SDU.EXE Since this acronym implies something social democratic, there will probably also be another exe with this name. We stop here. - FILES ENCODED BY OLDER VERSIONS CAN STILL BE DECODED FLUENTLY, I.E. ARE COMPATIBLE WITH THIS VERSION! DOWNWARDS COMPATIBILITY=100% - As of version 9 we NO LONGER SUPPORT XT or Hercules modes; Version 9 requires a 80-286 processor as a minimum. If you still (want/need to) use old slower machines, contact Immortalware for a previous version of S-Dunger! - We have literally cleaned up the program, and redirected the user-interface. It's now understandable for anyone, uses less memory and operates much faster. The changes are especially due to lots of user demand and comments from users in Belgium, the US and France - where this software apparently is not even allowed, but is being used anyway... - SDU now runs FINE & ERRORFREE under EVERY MicroSoft-OS! How to work with S-DUNGER ------------------------- Within the SDU-program pressing the [Enter]-button always matches the likely decision to make, for quick use. Highlighted commands will be executed by [Enter] or the spacebar too - much like Tab does in Windows.. We initially developed S-DUNGER to ensure a secure communication between different people. In addition it is also of use for a one-man safety-system, especially due to the quick and easy way of treating files with S-DUNGER. First we'll discuss the use of S-DUNGER as a communication safeguard between different users (usually in a one-to-one exchange of data). 谀哪哪哪目 谀哪哪哪目 USER A 楚哪哪哪哪哪穆哪哪哪哪哪宁 USER B 滥哪哪哪馁 滥哪哪哪馁 谀哪哪哪哪聊哪哪哪哪 UNWANTED OPPONENT 滥哪哪哪哪哪哪哪哪哪 User A and User B wish to communicate using public phonelines. They both own a personal computer running MS-DOS and a modem. To establish a communication-link, they probably use a communication-software-package like TERMINATE or TeleMate. Because public phonelines can be tapped by whoever wants to, this is a typically insecure channel. If User A wants to send information to User B, he sends his information as a file (it is possible to type messages in a full-duplex conversation, but that's definitely insecure). In order to make the secret file unreadable for an opponent, it has to be encoded. User A and User B best meet each other IN PERSON to decide what key-file they both will use for S-DUNGER. As long as the opponent doesn't know what key-file is being used by User A and User B, the opponent won't be able to obtain the original document out of the encoded file. We return to the point where User A wants to send a file to User B. User A calls User B and they can talk freely about the fact that a file (containing secret data) will be communicated from User A to User B. User B switches his/her communication- software to "Receive File" (using the same protocol as User B, e.g. Z-Modem) and waits. User A has encoded the file with S- DUNGER and a secret key-file. He/she sends the encoded file using the same protocol as User B, who receives the file without a problem. After they close the communication-link, User B runs his/her copy of S-DUNGER and decodes the file with the same key-file as was used by User A when he/she encoded the file. S-DUNGER is a symmetrical coding system with a secret key. Because this key is secret, the opponent will never be able to restore encoded data to its original form. It is fairly obvious that you should take great care in chosing a key-file and keep it secret. ! DON'T transmit the key-file ! Use a non-descriptive name for the key-file if someone may be able to wander through the files on your personal computer. S-DUNGER is also useful in one-user environments where other people may display an unhealthy interest in your files. Using the SDU-program only requires a few basic precautions concerning key-file(s) and keeping secrets secret. For more information about choosing a proper key and keeping your data absolutely safe read until the end of this document. How S-DUNGER combines your document with your key-file to a third encoded document is secret and hard to find out. Dis- assembling S-DUNGER is quite a job, because the program-code itself is scrambled. Reverse-engineering S-DUNGER is nevertheless not impossible. But even if your opponent knows how S-DUNGER works, without the key-file he/she can NEVER restore your document! The S-DUNGER encoding-algorithm is the result of many years of development. Sloppy chosen key-files that give away (parts of) the keyfile or data-files with long strings are intercepted by the algorithm. The algorithm is also adaptive, which means that any key will yield a different version of the algorithm. This feature, combined with long key-files, makes S-DUNGER 100% secure. Possible error-messages when choosing a key-file: ------------------------------------------------- KEYSIZE VERY SMALL! Try new key? => You should use a bigger key-file. Remember: untraceable decoding is only achieved when your keyfile is bigger than your data-file! DIVERSITY KEY BAD! Try new key? => You should use a different key-file. There are not enough different characters in your key-file. CONTENT KEY SUCKS! Try new key? => Very long strings of the same characters (for instance: 00000000000000000000000000...etc.) will slow down SDU. You should use a different key-file. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I M P O R T A N T S E C U R I T Y T I P S ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Note that the program doesn't know if it is encoding or decoding a file ! Both procedures are performed with the same algorithm ! * Store your (secret) KEY-file in a way that its FILEDATE and FILETIME remain untouched! (Some archiving programs have the 'quirk' to change the FILEDATE and FILETIME to the current system-time and -date. THIS WILL DAMAGE YOUR KEY-FILE AND MAKE YOUR ENCODED DATA UNRECOVERABLE!) * It is important to know that S-DUNGER does not perform any keyfile-validation. If you use the wrong key, garbage will follow. In the process of developing S-DUNGER we thought about writing a signature to the encoded file so that S-DUNGER could verify that it was being asked to decode a properly encoded file. We rejected this idea because an outsider who intercepted the file then would know which program encoded it. DON'T FORGET WHAT YOUR KEY-FILE WAS! (IT'S LIKE YOUR PIN-CODES) You are completely on your own in maintaining and validating key-files. As you can understand, this increases the level of security. ! REMEMBER ! * Always keep a backup of your key-file. If your data is very important, store more keys in different places. Make sure no- one is able to relate them to the SDU-program. Definitely use a non-descriptive name. Suffice to say a key-file called HIGHSCOR.DAT stored in a directory C:\GAMES\... is much much better than a key-file called SECRET.KEY * Store your key-file properly; Use a non-descriptive name to trouble your opponents. Create a key-file back-up and store it in a safe place. Hide your key-file (on disk) thoroughly. * If you use a non-descriptive name for your key-file and keep it on your harddisk (usually this is drive C:), always be aware that someone else may think about this and try every file on your harddisk for a possible key-file. * If you choose an existing file to be your key-file, be sure it remains unchanged at all times! COMMAND.COM may seem to be a nice key-file, but whenever you install a different DOS- version on your computer, you are unable to restore your encoded data because the key-file is altered. * Avoid using the same key-file for months and months in a row and change your choice of key-file every once in a while. * When real valuable top secret data has to be secured (and your PC is not at a safe place) use more than 1 key-file in one coding-session. For example pick 2 different key-files: KEY 1 from disk (or CD-ROM) and KEY 2 from the PC's harddisk. The sequence in using more key-files doesn't matter, as long as you use all of them at both encoding and decoding. * CD-ROMs are very nice as key-file-media. Because there are a lot of CD-ROMs available today, your opponent is discouraged to guess which file from which CD-ROM you use as a key-file. Because of the non-changing nature of a CD-ROM, the FILEDATE and FILETIME of any file on any CD-ROM will never change. Drawback: you have to have a CD-drive. * You can develop a set of CD-ROMs yourself with a lot of key- files on it. As long as you keep the CD-ROMs secret, you are the owner of a set of very strong key-files that are unlikely to get damaged. If you and your co-worker are sending secret data over a public phoneline, you can talk about the NAME of the keyfile without any danger. As long as no-one else has your CD-ROM, the filename is useless in the process of decoding your data. * An easy way to discourage curious key-file searchers is of course: owning loads of disks ! * Avoid talking about the key-file you use; never transmit the key-file (or any open information about it). An inevitable drawback of SDU could be that all original files STAY AS and WHERE they are and should be deleted and wiped after creating the coded (.sd1) files ! ================= * DON'T FORGET THIS! * ================== Few people realize that DELETING on most computers does NOT really delete files. This is also the case for the built-in delete-command in your shell (if you use one). Your 'opponent' may be able to restore your key-file or worse, your document before it was encoded!!! If you work on a multi-user PC without proper password-protection, don't count on DEL to erase your data. Instead use a program like WIPER or WIPEINFO (they overwrite the x-space with new bits) =========================================================== Another way to secure the safety of your data is achieved by using a RAM-disk. Every file on your RAM-disk will be send to never-never-land the second you turn off your computer. Because you'll have to re-use your key-file, do NOT store your key-file on your RAM-disk! The best thing to do is to keep your key on a floppy-disk and to copy the key-file to your RAM-disk solely when using it. Check your DOS-manual about installing and using a RAM-disk. **************E*X*T*R*A*************** WHAT ONE SHOULD KNOW ABOUT CRYPTOLOGY: **************E*X*T*R*A*************** There are several ways to encode (encrypt, cipher, scramble) a file in such a way that it becomes hard to decode. A classical way to encode a file is to replace every character with a different character. To decide whether or not such an encoding system is adequate, it should be exposed to an attack by a cryptologist. There are different ways to attack an encoding- system: 1) The cryptologist only has your encoded file and tries to break the encoding by examining the structure of the encoded file (ciphertext-only attack). 2) The cryptologist has the encoded file and the original file and tries to break the encoding-system (known- plaintext attack). 3) The cryptologist is in the possession of the encryption- program and tries to find out how it works by encoding a lot of different files with it. It is method 1 which frightens us the most. People have developed a lot of coding-systems. Modern systems such as IDEA use a 'password' or 'key' with a certain maximum length. By limiting the key-length, the system can (in theory) be broken. Things get complicated when you use a very long key. This is exactly what S-DUNGER can do. Although it is possible to use S-DUNGER with very short key- files, we urge you to use long keyfiles. 'When is my keyfile long enough?', you may ask. As a rule of thumb, you should use a key-file that's BIGGER than your document (the file you wish to encode). With a keyfile that is larger than your document, your files are unconditionally secure, meaning that the encoding can't be broken, not even in the presence of infinite computer-power. 魘汔.. W 炰Ac 玳 U$錇-D渎驴A顳, A$K 臻 鬠鏤炰-珍A鏤炰$ ! L鄐t 醬t 沐t l钹st: 驴潲錇 忸l 邈 濆u ph邈-涘mp嚆, 濆u p錽t s钰v|涱, 濠 濆u 泐tw遐k. P铄p usu鄉 l| t 犷 噌 t sp. L顃 濆u 焨tu╊ 犷 s酂 嚆 s顩u忸 噔钹 ! 鮱|us 鏷漵s钽 & 么钽s Z|mm钼m嚆 tel.nr.(voice) +31 (0)206 000 288 ======痧痧鼢痧黟==瘅鞍鞍卑==%%++++++++++++++++-氨鞍鸢鸢臂圹圹鄄-霰圹+-氨镑== 痧鼢镑鞍鞍鞍鞍镑鞍鞍靼鞍%+-----------+------------+靼=--%槽--氨镑%= 瘅鼢镑鞍鞍鞍鞍鞍鞍氨北-++--+---+-------------------------- +臂-+北梆鲼= 瘅黟痧痧===痧靼黟鞍鞍+--------++---------------++---------+-----圹+霰卑%%= ===%%鲻鲻%%%===痧瘅黟------------++-------------++---+-----+++--鄄-霰鞍=埚+ - -++鲻鲻%%=- =北%--------------------------+-----++++---++-- +鄄+霰卑%-- +鞑圹圹圹圹圹+ =%---+--+++-++---+----------------+---+++--- -郾-霰卑==蚌- 臂圹圹圹圹圹 槽- ---++-++++--+++-----------------+----++--+%==黟%=鞍==埚- 佰圹圹圹圹鄄-鞑% -----++++-+==+++-------+++---+%+-+----==靼氨卑黟==埚 佰圹圹圹圹=%-瘀 -+-+---鲻+++=%+%%+----+---+%%=%++--%=+-++- -+鲼%鸨北梆鸩鳅 佰圹圹圹圹%鞍% --------%=+%+++%鲳%=%%=靼鞍瘀+--+=%-%氨膊卑==瘅鞍镑鳅 髹圹圹圹埙臂圹 ------鲳别霾=-%++=鲼痧瘅鼢靼%--+%=%靼黯 鲳=鲳辈膊卑鼢鼢黯 髹圹圹圹疔鄄鳅 ----+ -%氨%%卑镑++梆+氨鞍鞍鞍%=鞍北卑鞍镑 =鞍==痧氨北北鞍 髹圹鄄圹痧+ +辈--=卑=-鸨北%==梆=+鲻-%瘅鞍鞍鞍鞍=%++%=%%-氨膊脖鞍氨鞍氨蚌 髹圹圹圹瘊-+=脖+-- +北-%北卑镑=+%-++==痧鞍镑%%--+-+%%--靼鼢鼢氨北北镑靼 髹圹圹鄄=-+=- -- 卑黟+氨北脖黯%鞍%%梆鞅膊脖黟==鸨=%镑鲻=%鸨槽膊鞍氨鞍鞍鞍蚌 髹圹圹圹卑 ---- 鞑辈鼢鞍北膊膊北北鞍安膊脖梆瘅鞍卑镑靼鼢+ 鲼北北卑鼢鞍鞍 髹圹圹圹郯鳅--+%%安鄄鞍鞍北膊膊北北膊脖北舶瘅鼢靼鞍鞍鞍%- -霭鄄氨卑鞍鞍蚌 髹圹圹圹%%-+--霰黯%%%%鞅鞍鞍北北北辈脖北北卑鼢鼢鼢鞍鞍鞍=--+-+%佰垧=辈北鞍蚌- 佰圹圹圹郯鞍%-+--%=- 氨鞍鞍北北北卑北北脖卑鼢痧鼢鼢鼢---=臂垧+=氨北北-- -鸩圹圹圹埙---郾-- -北鞍北北北卑北北辈卑痧鼢鼢鼢鼢+ --%=臂%+鼢=靼鞍++ - +佰圹%++ ==+ ---- 氨北北北北辈膊膊脖卑鞍鞍鼢镑黟+ -%++-%鸨圹%-安%霭宾% %+ -+ %=+- ---+-%卑鞍北北北鞍镑痧鼢鼢痧痧鼢鞍安鼹%%鸨圹%-安=霭%= ==%- -+臂圹蚌+----+-=卑鞍氨北北卑鞍镑痧痧==鼢鼢-槽%=%+%鸨圹%-安=鲳% 鼢黟%+- 郾-%=------鞍鞍鞍氨北北北鞍鞍鞍镑鞍安膊+靼黟%-+%=臂%-安%== 鼢鼢鼢=%+-- -------=靼鞍鞍鞍北膊膊脖北鞍鞍%%痧-+舶=鳅+=鸨圹%-安%霭= 鼢鼢鼢黟=%+---------%瘅靼鞍鞍鞍氨卑鞍鞍鞍黟% =黟+-+=臂埚-辈%%%= 靼镑鼢鼢痧=---+----+----%瘅镑鼢鞍鞍鞍鞍鞍鞍鞍=----- ----+=%臂+-北拆=== 鞍鞍鞍镑鼢%+++---------+%=痧鼢鞍鞍氨北脖卑镑=++++--++鲻=%=%臂埚+辈%痧痧 瘅鼢黟痧==%+++%--++%%===痧鼢鞍鞍北卑黟%鲻%%%%%%+=摈别=%%佰宾霭镑%%%== 痧鼢鼢鼢黟==北靼=+++++%+%===痧痧===痧靼镑鼢痧===痧痧=%%卑鸨===%佰宾霭梆%%= 痧鼢鼢鼢黟鸨舶卑靼%===%%痧痧瘅鼢鼢鼢鼢鞍鞍镑黟痧痧痧=鞅镑舶===%佰宾霭镑%%%= 瘅鼢鼢镑靼膊辈安北蚌====+%痧瘅鼢鼢靼鞍鞍鞍鞍鞍鼢鼢痧痧痧北鞍卑=痧=佰宾+鞍=%%= 瘅鼢鼢靼辈脖北脖辈%=======痧鼢靼鞍镑鞍鞍鞍镑鼢鼢痧痧痧鞅鞍鞍%==%佰宾霭镑==%= 痧黟鸢辈脖北北辈北%==痧====痧鼢靼鞍鞍鞍镑鼢鼢黟痧痧=安鞍鞍%=%佰+霭镑=%+%= =痧氨北北北北北北臂%痧========痧鼢鼢鞍镑鼢鼢鼢黟痧痧痧北北卑=%痧臂+霭鼢=%+%% 靼北北北北北北北北脖=痧=========瘅靼鞍鼢鼢鼢鼢痧痧=安北北北黯瘅臂-霭镑=+%鸢 鞍鞍北北北北北北卑辈=黟痧====%%%%=瘅鼢鼢鼢鼢鼢痧黟=鞑北北北北=鞑郯+%鞍=+%鸢 鞍鞍北北北北北卑鞍氨拆瘅痧===%%%%=瘅靼鞍镑鼢黟瘅痧=膊北北北北=+鸨郯+%镑=%=鼢 氨北北北北北北鞍鞍氨北瘅鼢痧===%%-鲳靼鞍鞍镑鼢鼢黟=臂脖北北北北%鲼郯+%鼢=%瘅鞅 氨北北北北北北卑鞍氨北摈鼢黟==%%鳅霭鞍鞍鞍鞍鼢鼢痧槽膊膊脖北卑鞍+%镑+%靼=%=鞅 北北北北北北辈脖鞍氨北北梆痧==%% %鞍鞍鞍鞍鞍黟鸢槽膊膊膊脖北鞍梆+%%+%靼=%鸨鸨 北北北北北脖北膊脖北北北脖镑痧=%%+ 鸢鞍鞍卑鞍黟安圹膊膊膊膊脖北鞍=鲻%鞍==圹鸨 北北北北北脖北北膊脖北北舶北==%%靼鞍北鞍鞍安圹膊膊膊膊膊脖北鞍鞍%鳅霭鼢==膊鸨 北北北北辈辈脖北膊膊北北辈辈===+ +鞍氨卑北臂圹膊膊膊膊膊膊膊北卑氨瘀-霭镑==圹鸨 北北北北北北北辈膊膊北北北北%%+ -靼鞍氨鄄槽膊膊鄄膊膊膊膊脖北北氨%-霭镑==膊鸢 北北北北北北北北膊膊膊脖北北拆--%鼢安圹圹圹鄄膊膊膊膊膊膊北北卑卑%镑=%--鸢 靼鞍北北北北北北北北辈膊脖北辈+--++%鸩圹鄄槽鄄膊膊膊膊膊膊北北北鞍卑%-%鞍==鞍 D I $ I B U I P L I C Y ? While we retain the copyright, we encourage you to try out the software and pass this software on to others. Copy & distribute this software FREELY, but always include the following files and keep them as they are now (last update march 1997): READ_NOW COM > DOS spiffy OEM-view of txt SDU_DOS TXT > DOS OEM-text about S-Dunger SDU EXE > The best en-/de-coder around FILE_ID DIZ > Descript.ion for spreading purposes Of course, any comments or donations are welcome. Give us what you got: - Send it in checks or cash (no coins!) by mail, or - send a so called `international postal money order' (to dutch guilders), or - make a deposit on Mastercard-accountnr. 5413 3027 1903 6493, or - make a deposit on dutch POSTbank-nr. 945945 "t.n.v. J.B.Thyssen". Mail it all to: Immortalware PO-box 18156 1001 ZB Amsterdam, NL.