[QUOTE=DravenX] Ok i have been playing around with the plugin and it's a good idea but still has some security holes.The tmp file can still be accessed when the game is running.[/QUOTE]
Yes, you're right. But the idea is not to prevent the user from viewing the content. (because, in practice, this is impossible ), but to prevent any changes in the content that will be loaded by the game.
Imagine that you're using the Plugin to load your cutscene images. The user will not be able to hack and change the graphics and will not be able to edit or see the the cutscene images that he has not "archived" yet. But, when he do archive, he can (obviously) see them in the game window, save them using print-screen or in the tmp folder when they are on the screen. No problem with that. =D
[QUOTE=DravenX]The next Security flaw is the password ,If i am desperate enough i can get your password very easily by examining the exe with another app.Create an exe game with this plugin and i will show you your password no matter how long or short it is.[/QUOTE]
There is an old (or classic?) technique to get around this.
Imagine that your password is "xBacon2016". In the password field of the action: do not simply write "xBacon2016", but "xB"+"acon"+str(20)+str(1)+str(6).
Now try to find the password in the executable. ;)
And don't forget. "zip" files do not necessarily need the extension. zip. Nothing prevents your files from having ".pak", ".cab", ".dat" or (my favorite) ".dll" extension. =)
[QUOTE=amfest]I personally haven't messed with it yet but does it create the tmp folder in the game dir? [/QUOTE] Yes, in the game dir.
I'm thinking about a "compress file with password action". So you could create save games in .ini files(I know u guys do it all the time) and protect then from hacking. =)