|
|
|||||||
[Moderator's note: As this thread has drifted off topic, I have moved it to the general discussions forum and posted a new one in suggestions - Les] Now that KiX can pre-tokenize/encrypt/shrink the scripts, I think it should also be able to embed the script into a single EXE. I envision a lean EXE with the tokenizer, debug, keyword lists, etc. stripped out to make the resultant EXE as small as possible. There are lots of good reasons to make the EXE as small as possible, but mainly because bandwidth is a terrible thing to waste. I first made this suggestion on SL's beta forum Thoughts: 4.50 - tokenizer (external app?) but since it is slightly off topic there, and since it did not generate the interest there that I had hoped for, started a separate thread here. There are already a couple of ways (KiXScripts Editor and KiXCrypt) to put everything into a single EXE, but they mostly rely on temporary files. I believe also, that there is a tempfileless version of KiXCrypt in the works. A single EXE would simplify distribution of applets, ease versioning, and eliminate the number of round trips on searching for the external .KX file. It would also ease the deployment of GPO based scripts which don't take well to external pathing. The implementation of MakeEXE should be such that it could be scripted on the command line or by API so that KiXScripts Editor could choose to leverage this approach over their existing one. On the topic of security, I recognize that this would still be 'security by ignorance' and that nobody should misconstrue this as "Secure". To that end, I point you to Ruud's comments within the discussion Thoughts: 4.50 - INCLUDE (his first reply)where he says "In general, you should never, ever, put truly sensitive information in any shape or form within the users security context. Whether or not passwords in scripts are truly sensitive depends on your specific situation." |
||||||||
|
|
|||||||
I agree...I would love a built in solution to make scripts executables. |
||||||||
|
|
|||||||
This is a great idea. Also, this would be cool to undo the encryption/compression too. Of course, a "back door" would be a potential security risk... Kent |
||||||||
|
|
|||||||
Dear, The MakeEXE idea is a good one, but it isn't necessary to have a backdoor to recreate the original source. Every programmer is saving his sources after compilating them. greetings. btw: the tokenizing thing is a good result, which makes it possible to make your sources more secure as ever. kixtart doesn't required anymore normal source as input. |
||||||||
|
|
|||||||
These sounds like some very good improvements...Anyway to get a copy of this alpha version of 4.5? |
||||||||
|
|
|||||||
Dear, What is your email address? greetings. |
||||||||
|
|
|||||||
sptomey at hotmail dot com |
||||||||
|
|
|||||||
see your mail. greetings. |
||||||||
|
|
|||||||
Got it...Thanks. |
||||||||
|
|
|||||||
Dear, We have send you the kixtart 4.50 build 140 edition. Currently a newer release has been released. See Scriptlogic We don't have this latest build. Specific issues aren't a problem in our scripts. Such structures we weren't/aren't using. greetings. |
||||||||
|
|
|||||||
LOL Quote: We probably would never have found that one since we have such a hate for GOTOs. |
||||||||
|
|
|||||||
Might be time to deprecate GOTO ;-) Then nobody is tempted to use it. |
||||||||
|
|
|||||||
OOPS! I tried copying (keeping the original) this thread from the suggestions forum. I guess with UBB.Threads this is no longer possible. If you would like to contribute (on topic) to the original suggestion, I encourage you to visit MakeEXE suggestion |
||||||||
|
|
|||||||
Hello Could you please send the 4.5 version to me? I would like to test the new tokenizing features for our terminal server login script. Thank you! citrix@online.ms I will write feedback to the Scriptlogic Beta Forum! Regards Danny |
||||||||
|
|
|||||||
KiXtart 4.50 is in a private beta test and not publicly available. |