Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 112

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 112

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 112
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3368: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:112)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3370: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:112)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3371: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:112)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3372: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:112)
OrbWorks Community Forum • View topic - How hacker friendly is PocketC?
Page 1 of 1

PostPosted: Thu Jan 12, 2006 4:30 pm
by Aqua32
I went ahead and poked around in a prc file created with PocketC Architect just to see what I could find...

I noticed that I could find strings (which I would expect to) and these strings could easily be encrypted so they cannot be found directly but then I found all of my function names & event handler names also. These should be obfuscated during the prc creation!

Im not a cracker but I do know that the more information you give them, the easier it is to figure out how your app is working... This leads to my second question..

What else might be easily decyphered by a hacker/cracker? And what steps can be taken on my/your part to prevent exploitation of my work?

Thanks much

PostPosted: Thu Jan 12, 2006 8:08 pm
by exit_head
nothing, if someone wants to crack your app theres not much you can do, there gunna do it.Try to make your registrations system use func names that arnt obviouse.

PostPosted: Thu Jan 12, 2006 9:39 pm
by Aqua32
Obfuscation sure would be nice though.

And, yes.. If someone really wants to crack your app, they will.. But would you rather break into my house or a National bank ;-)