KiXforms Forum Index KiXforms
The Forum for the KiXforms Community
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 Quick Links 
Site News
Downloads
Documentation
Donations
Script Archive
Tracking Systems

Pre-tokenizing and KiXforms

 
Post new topic   Reply to topic    KiXforms Forum Index -> Discussion
View previous topic :: View next topic  
Author Message
benny69
KiXforms Advocate
KiXforms Advocate


Joined: 30 Oct 2003
Posts: 567
Location: Lincoln, Ne

PostPosted: Sun Jun 05, 2005 8:50 pm    Post subject: Pre-tokenizing and KiXforms Reply with quote

I just downloaded KiXtart 2010 (4.50) and I am tiring to understand the format that our scripts should take in reference to KiXtart and KiXforms.

The way I have interpreted what I have been reading is that;

Pre-tokenizing a script encrypts, compresses (will process faster) and contains a signature.

Am I suppose to create a signature and add it, or just by the fact of tokenizing does it add a signature?

A statement out of KiXtart 2010 documentation, "The level of security provided by tokenizing a script qualifies as ‘obsfucation’. " what does ‘obsfucation’ mean?

Does all of this mean that I should be separating functions from the main script and calling the separate Pre-tokenized scripts as I need them?

I have been putting child (for the lack of a better word) forms in functions and calling the functions when I want to show that form. Should I be separating the forms into separate scripts? How should I be doing this?

I use ASE and like compiling my scripts in to self contained exe's, I add Icon.dll's, .ico's , bmp's, wkix32, KiXforms.dll and anything else I need. Should I be doing it differently?

As I create scripts I have been throwing everything into one directory, should I be breaking things up into different directories, like a forms dir, images dir, dll dir or what?

_________________
Wait don't order yet,... get KiXforms Designer .NET 2.0 (Beta)
KiXforms Designer .NET 2.0 (Beta)
Back to top
View user's profile Send private message Send e-mail
Les
KiXforms Aficionado
KiXforms Aficionado


Joined: 24 Dec 2003
Posts: 317

PostPosted: Sun Jun 05, 2005 9:58 pm    Post subject: Reply with quote

There is no user action to add any signature.
You would continue to do the same as you did in previous versions.
Obfuscation is the practice of making it difficult but not impossible to reverse-engineer the script. It is not true encryption.
ASE is not a compiler, but rather it is a packager. You probably would not want to pretokenize scripts if you are going to package them with ASE. You will want to wait for a future release of ASE that does the tokenizing. That said, you can tokenize sub components if you like.
What wwould be the point of breaking up pieces into subdirs?

_________________
The Repro Man
Stealing for a living!
Back to top
View user's profile Send private message
benny69
KiXforms Advocate
KiXforms Advocate


Joined: 30 Oct 2003
Posts: 567
Location: Lincoln, Ne

PostPosted: Sun Jun 05, 2005 10:04 pm    Post subject: Reply with quote

I think I was talking to Jochen a while back and I think he was breaking thing up into different directories maybe that was for organizational purposes I don't know.
_________________
Wait don't order yet,... get KiXforms Designer .NET 2.0 (Beta)
KiXforms Designer .NET 2.0 (Beta)
Back to top
View user's profile Send private message Send e-mail
Lonkero
KiXforms Devotee
KiXforms Devotee


Joined: 13 Mar 2003
Posts: 1022
Location: Espoo, Finland

PostPosted: Wed Jun 08, 2005 2:35 am    Post subject: Reply with quote

where did you download 4.50 from?
I didn't know it was published yet...

_________________
Hammer
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
Lonkero
KiXforms Devotee
KiXforms Devotee


Joined: 13 Mar 2003
Posts: 1022
Location: Espoo, Finland

PostPosted: Wed Jun 08, 2005 2:40 am    Post subject: Reply with quote

btw, what you can test with 4.50 RC-1 (which I think you have) the include combined with tokenizing.

so, instead of using call and stuff to keep up with your sub scripts, use "include" to include them in the main project script during tokenizing.

then, after that, all you need is that tokenized mainscripts.
so neat.

_________________
Hammer
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
benny69
KiXforms Advocate
KiXforms Advocate


Joined: 30 Oct 2003
Posts: 567
Location: Lincoln, Ne

PostPosted: Wed Jun 08, 2005 3:10 am    Post subject: Reply with quote

Lonkero,
You are correct I have the RC-1 (I should have been more specific). Your ‘include’ suggestion sounds like a great idea, after reading the ‘Remarks’ @ kixscripts.com it sounds like you would use 'include' at the beginning of your scripts, but I'm not sure if I am understanding it correctly, could you give me a simple example?

Thanks for the great input.

_________________
Wait don't order yet,... get KiXforms Designer .NET 2.0 (Beta)
KiXforms Designer .NET 2.0 (Beta)
Back to top
View user's profile Send private message Send e-mail
Lonkero
KiXforms Devotee
KiXforms Devotee


Joined: 13 Mar 2003
Posts: 1022
Location: Espoo, Finland

PostPosted: Wed Jun 08, 2005 4:33 am    Post subject: Reply with quote

well...
include is kinda like the one found in the program languages.
basically, the included script is included (same happens with call) before execution or interpretation of the script.
whereas call does call the script during execution when call line is met.

include is the way if you have bloated script, say, if you use lots of udf's
you can leave them out of your main script and use include to include them in "just in time" before kixtart executes the script.

now, what the real benefit is, that when used with tokenization, the tokenized script will hold all the included files too.
that is, the whole script system you had build, is ready to be published as a single tokenized file.

with called scripts, you would go on sharing each and everyone of them.
and you would need to tokenize them separately too.

so it comes to the obsfuscation (or what the word is)...
with include, you can work in your private little developing environment just like before but when you decide to publish a new version, just tokenize the main script (similar to that compile button in visual studio) and voila, your package is ready.

this way, you never need to convert anything on your own system nor hazzle with dependencies.
and once files is tokenized, it's fixed and can't be broken by missing udf Wink

hope I got this little clarified. I mean, I just realized that my english is not good enough for proper text that could nicely put the words in perfect order.

_________________
Hammer
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
Display posts from previous:   
Post new topic   Reply to topic    KiXforms Forum Index -> Discussion All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group