Jump to content



Photo

Tokenized Compilation insecure?


  • This topic is locked This topic is locked
2 replies to this topic

#1 Koshy John

Koshy John

    koshyjohn.com

  • Active Members
  • PipPipPipPipPipPip
  • 461 posts

Posted 18 June 2008 - 03:13 AM

I thought that once the tokenized compilation scheme was introduced our scripts would be slightly more secure. I was under the false impression that it would (at least) be harder for others to decompile scripts now. It's pretty annoying to find that within 2 minutes (searching, downloading and running), a script that took years to write (literally) could be fully decompiled into a recompilable form.

Is there any plan in the works for an even more secure system?
Visit: www.KoshyJohn.comMajor projects: neoSearch - DiskMax







#2 Valik

Valik

    Former developer.

  • Active Members
  • PipPipPipPipPipPip
  • 18,879 posts

Posted 18 June 2008 - 02:41 PM

Of course not. In fact, the next step is to add a way for people to easily view your script without putting any effort at all into it.

That is of course sarcasm. Really, did you need to create a topic on this subject for the 500th time? Locking yet another pointless topic on the same subject.

#3 Jon

Jon

    Up all night to get lucky

  • Administrators
  • 9,529 posts

Posted 18 June 2008 - 07:40 PM

I thought that once the tokenized compilation scheme was introduced our scripts would be slightly more secure. I was under the false impression that it would (at least) be harder for others to decompile scripts now. It's pretty annoying to find that within 2 minutes (searching, downloading and running), a script that took years to write (literally) could be fully decompiled into a recompilable form.

Is there any plan in the works for an even more secure system?

People need to understand that unless we make a compiled script ask for a password every time it is executed then someone can create a decompiler.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users