#99042 - 2003-09-03 10:05 AM
Re: KiXcrypt version 3.03x - call for testers.
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
quote:
how can I know where is the original crypted.exe?
It's already there. You won't find mention of it in the main documentation, as it has only been introduced with this experimental version.
Have a look at the new features described in the first post in this thread, specifically the %KIXCRYPTEXE% environment variable. This too is experimental, so let me know what you find.
|
|
Top
|
|
|
|
#99043 - 2003-09-03 11:46 AM
Re: KiXcrypt version 3.03x - call for testers.
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Bad (but not unexpected) news on the compression front.
The easy way to get compression into the existing code is to do it in this order:
quote:
source->encrypt->compress
It just took a couple of hours to implement this.
Unfortunately, the output from the encryption algorithm is extremely random - good for encryption, not so good for compression. This means that the compression routines cannot identify a reasonable sized dictionary to work with, and so the compression rates are very small.
The solution is to change the processing to:
quote:
source->compress->encrypt
This will require an extensive re-write of the existing code, and some creative thinking.
|
|
Top
|
|
|
|
|
#99046 - 2003-09-09 11:29 AM
Re: KiXcrypt version 3.03x - call for testers.
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
quote:
how do I check my kixcrypt version?
There are a few ways. If you run "kixcrypt.exe" with no parameters it will display the version and useage info. If you supply the "-v" option it will give a long version history.
wkixcrpt.exe is more tricky, as there is no console output. The two are always kept at the same version - they are created with the same source code, the only difference is an extra flag supplied to the linker which disabled the console.
If you are paranoid however, there is an environment variable %KIXCRYPTVER% which holds the version number. Create a little script to display the version number in a MessageBox(), encrypt and run.
[ 09. September 2003, 11:29: Message edited by: Richard H. ]
|
|
Top
|
|
|
|
|
#99049 - 2003-09-18 10:26 AM
Re: KiXcrypt version 3.03x - call for testers.
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
I covered this in the last few paragraphs of reply http://www.kixtart.org/board/ultimatebb.php?ubb=get_topic;f=14;t=000468;p=1#000017
Basically:
- The creation of temporary directories is not supported.
- Overwriting existing files is not supported.
It may be supported in a future version.
When script finishes running, the files that the script created are removed.
The only files which will not be removed are:
1) Additional files your script has created when it run.
2) Files that KiXcrypt has no permission to remove, because they are still in use or permissions have changed during execution.
3) Files left because of an abort.
|
|
Top
|
|
|
|
Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 369 anonymous users online.
|
|
|
![[Wink]](images/icons/wink.gif){kind=icon}
![[Big Grin]](images/icons/grin.gif){kind=icon}
