#98082 - 2002-03-28 04:22 AM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear Richard,
Great update. It was already hard to catch temporary file, but now it only becomes harder to do it. Possible that Ruud can his current point of view about pipe to kix. greetings.
btw: this week we will also update our site with it.
|
Top
|
|
|
|
#98083 - 2002-07-25 06:42 PM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Anonymous
Anonymous
Unregistered
|
EEP!! I've just redone my scripts and am using KixCrypt to protect the account credentials that I use for SU.EXE from being visible to the users. I thought it was working fine, until now... Doing a search of my users personal drives, I have now found no less than two dozen of the temporary (randomly named) .kix files that were not deleted after login. These are being left right in the root of my users' personal drives. I'm worse off now that I was before. Now the sensitive password is not only visible to the user, but being presented to them right in their personal drives.
Can anyone offer suggestions?
|
Top
|
|
|
|
#98089 - 2002-12-19 12:18 AM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Get the small (15 Kb) executable kixcrypt.exe from here. Get the small (15 Kb) console-less executable wkixcrpt.exe from here.
18 December 2002 Version 2.14b released Actually, it was released a few days ago, but the board has been down It's amazing how much a part of my daily life monitoring the KiXtart BB has become! Changes
- A bug in memory allocation causing a failure on Windows XP has been solved. Note, I could not replicate the failure, but testing at the site where the failure occurred suggests it has been resolved. Let me know if it hasn't. Many thanks to ElegantSol for his help in resolving this.
- The first "cannot find self" error message is no longer displayed. It wasn't particularly useful and would appear on systems which don't expand the command line to include the command extension, such as most NT+ systems.
- In DEBUG mode non-ASCII characters present on the command line are reported, with their values.
- Well, you asked for it, now you've got it. Oe of the most popular requests has been for a method of setting the directory that the temporary file is created in. There is now a "-t path" option when you decrypt which will create the temporary file in "path"
Additional Info The API which retrieves the command line parameters cannot handle 8-bit characters. If you supply an 8-bit character the actual value I get is undetermined. This restriction has been in place in all version of KiXcrypt, but I have only recently received an email on the subject. In practice this means that you must stick to 7-bit ASCII characters on the command line. Note, non-printable characters such as the BEL (control-G) or the escape character are fine, so long as you work out a way of passing them on a command line. 7-bit ASCII characters are characters with a decimal value below 128. The only exception is NULL (Chr(0)), which is an end-of-string terminator. You may have trouble typing CR and LF characters, and the DOS end-of-file mark (control-Z) may cause some oddities as well.
|
Top
|
|
|
|
#98092 - 2002-12-18 04:04 PM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
masken
MM club member
Registered: 2000-11-27
Posts: 1222
Loc: Gothenburg, Sweden
|
|
Top
|
|
|
|
#98093 - 2003-01-17 02:51 PM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Major feature release - include support files in encrypted package.
Apologies for the long line.
Get the small (20 Kb) executable kixcrypt.exe from here. Get the small (20 Kb) console-less executable wkixcrpt.exe from here.
17 January 2003 Version 2.16b released Phew, less than a month and another feature release. This release adds the second most requested feature - multiple file inclusion. This means that you can now bundle the KiXtart interpreter, ini files, registry dumps, additional scripts or whatever you fancy with the main script. Changes
- Bug fix: A variable scope error meant that files created in a temporary directory using the "-t" feature would not be deleted in some cases.
- New feature: You may include any number of arbitrary files by using the "-f filename" option. You may repeat the "-f" option as many times as you like, up to a limit of 255 files.
- New feature: Three environment variables are created when the script is decrypted. These are detailed below.
Additional Info The "-f" option allows you to include arbitrary support files in the package. Note the following features and restrictions:
- Support files will be unpacked into the same directory as the primary script file.
- Path information is not kept - all unpacked files will be created in the same directory.
- Support files are encrypted in the crypted.exe
- Support files will be created with their original name. Only the primary script file will have a random name.
- The primary script file is always the last file to be unpacked and the first to be deleted, to reduce the time it is visible in the file system.
- Support files are not deleted until the primary file has finished executing, so may be visible in the file system for some time.
- If there is already a file present with the name of the support file being unpacked the process will abort and remove all files unpacked so far. There is no option to overwrite existing files.
It is possible for the process decrypting the file to create them in a directory specified by the "-t" option. This means that your own scripts may not know where to find the support files. To get around this, the following environment variables are provided: KIXCRYPTVER The version of KiXcrypt. KIXCRYPTDIR The temporary directory that KiXcrypt is unpacking the files in. KIXCRYPTFILE The full path name of the script being executed. Note: Some of these values are now also provided by KiXtart macros in recent releases. Example The following example creates an encrypted version of the file "update.kix". There are two support files, "control.ini" and "update.gif" which are packaged with it.
code:
kixcrypt.exe update.kix -f control.ini -f splash.gif
When the crypted.exe is run, it will unpack the three files into the current directory (or the directory defined by "-t"). The files "control.ini" and "splash.gif" will be created with their originbal names. The primary script file "update.kix" will be created with a random file name.
Here is a more complicated example:
code:
kixcrypt.exe update.kix -f control.ini -f spash.gif -f c:\winnt\kix32.exe "%%%%KIXCRYPTDIR%%%%\kix32.exe ^s"
This example will add the KiXtart executable to the file. The path will be lost, so the executable will be unpacked in the same directory as the primary script. To be sure that your are running your version of kix32.exe, the command is defined at the end of the line - the "^s" will be replaced with the primary scripts random file name. You must use the four "%%%%" characters to represent a single "%" in the final command line. If you now execute the encrypted file with the command:
code:
crypted.exe -t c:\temp
The four files will be unpacked into the c:\temp directory (assuming no file already exists with the same name). Assuming the primary script is created with the random file name "WSSHGSMO.kix" the command which will be executed is: quote: %KIXCRYPTDIR%\kix32.exe c:\temp\WSSHGSMO.kix
|
Top
|
|
|
|
#98096 - 2003-01-17 05:08 PM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Hmmm. Not a bad idea.
I should be able to cobble a simple GUI front-end together using JavaScript. It's just about time to leave for the weekend, so I'll have a butchers next week.
Not too sure about the help button though, takes all the fun out of trial and error
|
Top
|
|
|
|
Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 259 anonymous users online.
|
|
|