Torque and passworded zips?

#21 XoClutch's code is in now and the way I see it the only way to crack it is brute force or retrieve the password from the memory (its compiled in the engine). So it isn't 100% secure, but it doesn't get any better i think. I mean, you'll always have to compile a password in the engine, so you won't stop a real hacker. It will keep everyone else out there tough, so its good enough security if the only thing you are trying to do is keep people from messing with your assets etc.
I do think this is better then a passworded zip. It requires 2 passwords, and like Xoclutch said, there are no wizard-style tools out there to try a brute force crack.
btw, we also changed the file extension from .zip to .erp (encrypted resource package), while something like this doesn't stop the avarage computer user its already enough to keep the kiddo's out heheh.

#22 Oh, and if the challenge is a brute force crack, I don't mind spending 20$. Without the engine i don't think anyone will be able to decrypt it.

#23 Fixed URL for Cryptainer:

www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=7276

If your objective is to make the scripts inaccessible, perhaps some kind of Perl-based obfuscator would be best. TGE script is very Perl-like so an obfuscator designed to strip Perl of comments and indentation and convert all symbols to meaningless short tokens would make it difficult to know what the script was intended to do.

OTOH, anyone remember the obfuscated C++ contest in the back of each issue of the now-defunct C++ Report? That was one of my favorite columns every month.

#24 That resource, is a bit confusing to get working... Altho i got it compiled, it didn't seem to do what i wanted. I could be wrong though

#25

Quote:If your objective is to make the scripts inaccessible, perhaps some kind of Perl-based obfuscator would be best. TGE script is very Perl-like so an obfuscator designed to strip Perl of comments and indentation and convert all symbols to meaningless short tokens would make it difficult to know what the script was intended to do.

Scripts are compiled into .dso files, so they can't be accessed anyway.

#26 Note that .dso's aren't currently endian-portable (ie. x86 won't work on Mac). A recent thread has a patch to address this, adding an endian-fixer for floats.

#27 They should be endian portable for 1.4.

#28 www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=7787

Tell me what you guys think!!!!

#29

Quote:
They should be endian portable for 1.4.

RC1 or 2?

#30 Any version that implements an endian safe read/write for F64's. RC2 for sure, not sure that it made it into RC1. The change is trivial if you need it for your own projects; see Ritter's thread on the topic.