Which font you are using is no problem at all, because during the save action it will be converted to an useful one for notepad.
For example use select:
- font type: Arial (so you see the effects of a proportional font)
- font size: 8
Example of a font "Arial" with size "5":
code:
? only encrypted code is located in the common folder (f.e. NETLOGON). code which is very hard to modify. during decryption you can check of code has been
changed or becomes damaged.
? a kixtart script for decryption is very slow. by testing a short script it takes too must time and it is comsuming a great lot of CPU time. a short script
for me is about 250 lines.
by using another program language we get an enormous speed up. a script of 10.000 lines can be decrypted within 2 à 5 sec before starting
running kix32.exe procedure.
? do not use only XOR encryption. we think about many elements:
stripping Kixstart script first.
f.e. delete empty lines, remove comment statements, remove print statements when you are only using WRITE statements, change nice variable names to meaningless
variable names (f.e. $x1, $x2, ..., $x999), combining separate lines to one line. compress kixtart script. calculate CRC value of script. encrypt script by XOR
and/or other encryption techniques with a dynamic password usage.
a dynamic password means: each time you are running the encryption/compression procedure the password will be different, which means the encrypt output file
contains NEVER the same contents. make it possible to run the procedure over and over, so cracking because harder and harder.
Result of a script of 300.000 bytes is 40.000 bytes after using of compression and encryption techniques. Encryption cost about 10 à 20 seconds.
Decryption cost about 2 à 5 seconds. The processor speeds influences these results.
Example of a font "Arial" with size "8":
code:
? only encrypted code is located in the common folder (f.e. NETLOGON). code
which is very hard to modify. during decryption you can check of code has
been changed or becomes damaged.
? a kixtart script for decryption is very slow. by testing a short script it
takes too must time and it is comsuming a great lot of CPU time. a short
script for me is about 250 lines.
by using another program language we get an enormous speed up. a script of
10.000 lines can be decrypted within 2 à 5 sec before starting
running kix32.exe procedure.
? do not use only XOR encryption. we think about many elements:stripping Kixstart script first.
f.e. delete empty lines, remove comment statements, remove print statements when
you are only using WRITE statements, change nice variable names to meaningless
variable names (f.e. $x1, $x2, ..., $x999), combining separate lines to one
line. compress kixtart script. calculate CRC value of script. encrypt script by
XOR and/or other encryption techniques with a dynamic password usage.
a dynamic password means: each time you are running the encryption/compression
procedure the password will be different, which means the encrypt output file
contains NEVER the same contents. make it possible to run the procedure over and
over, so cracking because harder and harder.
Result of a script of 300.000 bytes is 40.000 bytes after using of compression
and encryption techniques. Encryption cost about 10 à 20 seconds.
Decryption cost about 2 à 5 seconds. The processor speeds influences these
results.
Greetings.
[This message has been edited by MCA (edited 20 June 2000).]
