code:

---

wkixcrypt tst.vbs -m "" -k -c "cscript.exe %s //b //nologo"

---

Running it still gives me a short console window...

Can this be prevented???

quote:

---

The encryption is a very simple XOR routine so hopefully I will still be able to travel outside the UK without fear of arrest :-o

---

quote:

---

ok, actually if his info:

quote:
--------------------------------------------------------------------------------
The encryption is a very simple XOR routine so hopefully I will still be able to travel outside the UK without fear of arrest :-o

--------------------------------------------------------------------------------

is correct, the crypter kix is 100% more affective than kixcrypt.

---

• I'm no security guru.
• It has to be two-way, i.e. unencryptable. More secure (one-way) encryption is fine for passwords but makes a script hard to execute.
• It's purpose is to deter users from browsing for passwords or security exploits which may be present in your scripts. It should not under any circumstances be used to secure nuclear warhead activation codes.

• The seed is either a password supplied when encrypting the file, or where no password is supplied then a random password of random length is generated. The only difference between the two methods is that a random password is embedded into the encrypted file so that it can be automatically unencrypted, and a user supplied password is not - it has to be supplied as a parameter to unencrypt the file.
  The seed is used both as a start point for the encryption algorithm and also to control it's process. A long password with a good selection of characters will make the encryption less predictable.
• All 256 possible byte values are accepted from the source file and used in the encrypted file. This means that any type of file including binary (Word, Excel, EXE) may be encrypted.
• The "XOR" encryption character is taken from a number of "one-time-pads". This means that each character which is encrypted from the source file has a unique character to encrypt.
• The one-time-pad used is selected by algorithm, and the pads are switched frequently.
• The character position in the one time pad is also based on an algorithm, they are not used sequentially, so even knowledge of the values of the one-time-pads would not allow you to decrypt the file.
• There are a further 3 additional methods used to peturb the encryption to make it harder to break. Some, all or none of these may be combined on each character during the encryption process and include:
  Rotate higher and lower nibbles (4 bits).
  Switch odd and even bits.
  Skip a number of iterations of the algorithm (self modifying algorithm).
  The decision on whether to use any of these "salts" is of course based on the algorithm.

Hopefully that will reassure anyone who was worried that the encryption technique might be too simple