#98101 - 2003-01-20 09:44 AM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Patrick,
- "-t" option is for use with the encrypted program "crypted.exe", not with kixcrypt. If you do "crypted.exe /?" (or -h) you will see it documented - you won't see it documented in the kixcrypt message as it is not relevant in that mode.
- "-f" option - you are quite right, I missed it off the usage message. Will be fixed in the next release.
- "^s" is an alias for "%s" and is documented in this thread somewhere. I will be writing new documentation at some time, but the GUI interface sounds like a lot more fun As the "%s" format is deprecated because it can cause problems I will change the message.
- Version history - "kixcrypt -v" will give you a full version history. All my errors made public.
The console thing. This comes up a lot, and I really don't have the answer A crypted.exe created with "wkxcrypt" does not create a console when it it executed. Unfortunately, the "system()" call that I use to execute the unencrypted script does create a console. If anyone has an idea how to execute arbitrary DOS commands from a MinGW compiled exe without creating a console please give me a shout and let me know.
|
Top
|
|
|
|
#98102 - 2003-01-20 05:19 PM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
KiXcrypt GUI interface.
As a response to the huge number of request (Hi Shawn) I've knocked together a simple GUI interface to the KiXcrypt utility.
It is basically a KiXtart script using IE COM calls, and some JavaScript.
I'm not posting the script here as it is chock-a-block full of HTML code so it'll be a real problem to post to this forum.
This is beta quality - not all KiXcrypt options are supported, there are no instructions and garbage-in will get you garbage-out.
However it seems to work OK, so I'm looking for some feedback. I'd like to know of any problems, extra features it needs, and whether it is worth me spending any more time on it.
Instructions for use: 1) Download the script from here 2) Ensure that kixcrypt.exe is in an executable location, i.e. your PATH or the current directory 3) Run "kix32.exe kcgen.kix" 4) Fill in the blanks and then hit the "Execute" button. 5) Keep generating the crypted.exe until you are happy (or bored), then close the IE window when you are done.
A temporary file kcgen.html will be created in your %TEMP% directory and removed when your done.
Please let me know how you get on.
|
Top
|
|
|
|
#98103 - 2003-01-23 04:49 PM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
What, no takers?
Maybe a screenshot will whet your appetite:
|
Top
|
|
|
|
#98106 - 2003-01-24 05:04 AM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Tan Bandradi
Fresh Scripter
Registered: 2001-04-17
Posts: 31
|
Dear Richard,
Does the "-k" option on KiXcrypt version 2.16b also applicable to prevent support file deletion (file that added with "-f" option) including the primary script file deletion?
Because I would prefer to delete the support file from the script alternatively, the support file deletion by KiXcrypt sometime fail, and the unpacking process on KiXcrypt will be aborted at the next execution, and the final result is KiXtart script execution will fail.
What I did is to include file kix32.exe, kx16.dll, kx32.dll, and kx95.dll together with the primary script by using the "-f" option. This support file will be unpacked and the kix32.exe will be executed to run the primary script.
I did this because I don't want to put KiXtart files on netlogon share, the script replication on domain controllers sometime fail because the .dll file is in use.
Thank you in advance, Tan
|
Top
|
|
|
|
#98108 - 2003-01-24 10:21 AM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Tan,
The file deletion process is as follows: [1] For the primary file only (which is normally your KiXtart script) some extra KiXtart script is tacked onto your script. This extra code immediately attempts first to overwrite, then to delete itself. This works because the entire script is read into memory so the file can be removed. The purpose of this is to leave the unencrypted file around for as short a time as possbile. Once the overwrite/delete has completed control is passed to your own script.
[2] Once your script has finished running the calling program (crypted.exe) checks to see if your script is still present i.e. the delete failed. You will get an warning message that the file is still present, and crypted.exe will itself attempt to overwrite then delete the file.
[3] All support files are then deleted.
In summary, the support files are not deleted until the script has finished running, so you can delete them yourself, rename them, copy them or open/read them in your script.
The only exception to this is if your script "escapes" the controlling crypted.exe, in which case it will think the script has finished and delete the files while the script is running.
You could escape control by RUNning a new process and exiting the original script for instance, or by using the "START" command.
The "-k" option disables step [1] only. This is useful if your primary file is not a KiXtart script. You might have packaged an executable, an Excel spreadsheet or a DOS batch file in which case adding KiXtart script to the file would render it useless.
|
Top
|
|
|
|
#98119 - 2003-01-28 04:56 PM
Re: UTILITY: KiXcrypt 2.16b - KiXtart encryption
|
Jochen
KiX Supporter
Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
|
|
Top
|
|
|
|
Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 557 anonymous users online.
|
|
|